Just wondering if new/upgrade of modules made for DNN will be made for DNN 3.1 (.NET 1.1) anymore. For instance the Beta module for Forums is out and according to its release version 4.x states it will be for DNN 4.x ... will there be 3.x version too? Will DNN totally shift its progress to .NET 2.0?

I know its a bit too much to ask, but at the moment upgrading to .Net 2.0 is just not feasible and almost not affordable.

Has anyone faced something similar ... what were your experinces?

Ta

Ta,

please accept, that DNN 3 is already in sunrise period. If it becomes necessary, there might be security fixes in the future, but in general, developement of the core framework has shifted to DNN4 only. There will be a few more module releases - the UDT team is working on a final feature upgrade 3.4.0 and will afterwards move to DNN 4 as well, so in the mid term you should think of migration to DNN 4, which is not that difficult as most DNN3 modules can be used in DNN4 without issues.

Hi Carlos,

By not affordable i meant it in our internal setup and not with installing and upgrading to .Net 2. We are using/planning to use DNN with an already built site where community features will be handled by DNN and content managed by another CMS system. As the pages will be juggled between DNN & the CMS we might be using some user controls built for the CMS in DNN, so having a development enviroment on the same .Net version helps. We also have to make a few changes in the source for DNN to make it work with our members system and other important requirments for the site so development tools used to code these changes need somewhat to be for a similar versioin.

We can upgrade the CMS to .Net 2 also .. but it just seems to esculate onwards. (we have VS 2005 ordered and plan to move to .Net 2 but not just yet as its not on the to-do list yet)

My managers just asked me to get a new community features up and me explaining a ripple effect like this just wont go down well.

Thanks for your help previoiusly