As some of you might know, upgrading a source installation of DNN has always been a bit tricky, especially if you have the in a sourcecontrol system like SourceGear, SourceSafe or simliar and/or have made any modifications to the core (which I find i almost impossible to avoid in a serious development project). The main problem is that you don't really know which files have changed and which hasn't, but also that solution and project files might have changed also and that the web.config file has been altered.

As far as I have been able to figure out, there are 2 possibilities. Either you can extract the new version on top of the current installation (which should not be confused with a production installation, we are talking development here) or you could delete all DNN files and kind of do a fresh start and just add your own files. Now, the first method is quite easy to exectue, but you will risk having files laying around that perhaps are from older releases of DNN, and might not even exist in the latest version, which could be a security- and maintenanceproblem. The second solution is perhaps safer, but if you are running a big project like we are with 30 projects in the solution plus the DNN ones, that isn't really something you want to do for just any maintenanerelease of DNN.

Is there some recommended approach on how to do this, ie some kind of best practice? I find that today, we kind of only upgrade at most 2-3 times a year, because it is so much work and feels quite risky without a proper process.

/pJ

Another thing, is there a way to see what files have changed between release 2 different releases of DNN Core? Other than using WinDiff or similar of course. That's another hurdle to pass over to get this to work. Must say I am really suprised by the low number of responses here, either I am missing something that everyone knows about or we are the only ones running a large scale devleopment project on DNN, which seems highly unlikely.