I have an instance of DNN v4.05.03 out there that is perhaps my most important site ever.  I am about to upgrade it to v4.06.02.  Within it, we have many custom modules (using SubSonic for DAL), and a handful of custom providers (Membership Provider, Membership Data Provider, Profile Provider, UrlRewrite Provider, and Sql Data Provider).

I am looking at all of the possible points of breakage and incompatibility beginning today.  I will obviously be first testing everything on a non-production version of the web site.  And to be precise, it will first occur on a development test-bed, then a deployed non-production server, and finally on the production web site.

Aside from the normal things such as back-up the files and the database, does anyone have any suggestions or comments on this upgrade path?  I want to be as informed as possible on any potential upgrade glitches that I might run into before I hit them (if possible).

Also, before anyone mentions it, I will not be upgrading to v4.07.00 until a stabilization release has been made available.  However, that looks to be version 4.08.00 from what I can tell on Gemini.

That's comforting.  Thanks Mike!  Also, we luckily do not use Object Qualifiers.  Personally, I dislike and discourage the use of them at all costs.

Will,
Any chance of listing them out specifically? Better yet, it would be great to know what dll's are obsolete given a particular version of DNN. Any way to squeeze out a better use of system resources is always appreciated.

FWIW, I had a very strange (and similar) event happen when upgrading a site from v3 to v4. A rogue dll kept the v4 upgrade from launching successfully. It was from back in the days of "experimenting with a module", being disappointed, then deinstalling. Trouble is, the dll stayed in the bin. Then when it was upgraded to DNN v4, that same dll was crashing the site. The only way to figure it out (without trying to guess at some fairly old file dates) was to remove/deinstall one-by-one and use the process of elimination.

Eric