Sebastian Leupold wrote
Sorry, but I strongly disagree. DNN 3.0 is rather old, premature and out of date (still using .Net 1.1). In contrast to an oldtimer car, which usually has its charme, there have been so many features added, enhancements entered and issues (including security affecting ones) fixed during the past years, that there is definately no recommendation for an ancient version of this framework - and many newer and elaborated modules currectly require DNN 4.x as underlying plattform. DNN 4 has come to an end, next release (after final 4.8.3) will be DNN 5.0.0 with new features and an easy upgrade path, do you really want to miss it? Upgrade from V 3.0 will be much more difficult, though the core team tries its best to make it possible.
If your host doesn't provide latest DNN, look for another one. period.
Version 4 and indeed Version 5 will have many additions over version 3 however it depends on just what you want to do with DNN - it is a web site framework and some of the additions will be a benefit to some and not to others - the average web iste does not always need the extras - one should look at the frameswork not by the criteria that v2 and v3 are old hat but that v4 and v5 have added benefits and when compared to v2/v3 some extra overheads that may not be needed just to be able to say that you have the latest version - the criteria in moving from one version of the framework to another is that one has a use for the additions.
To compare the framework to an oldtimer car is not a suitable comparsion - I actually run a 280E merc that is over 30 years old - however I have the comfort,safety and fuel economy with low running costs then I would have with a current version merc - the 30year old merc actually gets me drom point a to point b in the same time as the latest version merc and in fact does it cheaper.
However DNN is a tool that will generate a web site and of course web sites are all different with differeing needs unlike a car that is basically no matter what the version a thing that moves you from point a to point b - true if you want to pull the birds then a $300,000 car might just do that better then a $20,000 car but lets face it if you have the right personality you should be able to pull the birds on any value car.
DNN framework has that personality - you can pull customers into a web site based on dnn1,dnn2,dnn3,dnn4,dnn5 - at the moment dnn1,2,3 do that with less problems and when dnn4 is fully stable hopefully after the final of dnn4 then the same will apply. Support is a major cost to any consultant or hosting provider.
It is true generally that any provider should be able to support any current version of DNN - if you are on shared hosting then you should be able to set the asp.net version for the site via your control panel but just because the drop down shows asp.net3 does not mean that it should be used - you need to work out what you want your site to do - know your requirements and then match the software to meet it at the lowest support cost - dnn can be updated you can update dnn2 to 4 when the need arises if indeed it does.
What I stated about version chasing is simply do not chase version numbers for the sake of chasing version numbers - change version when and if the need arises for the extra benefits that the newer version provide.
If you need to retool your development tools to match the newer versions then again a decision process related to cost verus benefit must be applied. If you are in the USA then that retooling cost is lower then say those in Australia and other places.
Its a decision process - should I retool or update versions and why - its not just a statement that version 2/3 are like old time cars.