leupold wrote roberthking wrote
What you're saying is that the source for the modules hasn't changed from 3 to 4? The v3 source still works as-is for v4? |
Correct, they are still running on ASP 1.1, even when invoked from an ASP 2.0 portal. Anyhow, they will only need to be ported to ASP 2.0, if specific features of the new .Net framework features are to be used or you want to edit them using Visoua Studio 2005 (and above).
Having been away from DNN since 2.x, this really confuses me for some reason.
a) DNN4 is designed for the Net2.0 f/w, yet the modules in 4.0 haven't been ported. They CAN be, but it's the responsibility of the developer to do it himself.
b) One can develop modules against the 1.1 f/w and use them in 4.0, but would then need a more complex dev & runtime setup
c) One can stick with 3.2 and get all the functionality of 4.0
Am I getting this right?
If so, the only reasons to go to 4.0 are:
a) to take advantage of the 2.0 f/w for some module development
b) if the roadmap shows that 4.0 is getting all the attention and 3.2 will die quickly.
Am I still getting this right?