My websites all run on the Dot Net Nuke platform. And DNN released version 5 on Christmas. Lots of big news in the community, one might think that angels themselves had come down with trumpets to announce the joy that was DNN 5.0.

Except, it didn't work.

When I tried to upgrade the first time, the install died because third-party software I was using had some major problems with the release. So, I reset my platform, removed that particular piece of software and tried again.

The install finished, but now I couldn't log in because one of the other pieces of software I use didn't work with 5.0.

Now, you could say that the vendors have had time to fix this since the beta was released.

But I prefer to say that DNN broke one of the major software tenets, one I've broken often enough, "Don't break existing code with new release!"

The developer who's software broke the install said,

I'm going to have to put a notice on our site ..

Even trying to upgrade a DNN supplied module fails - returns "invalid file extension - " ..

The only way to install a module is to delete the module first, then install .. which means on an upgrade - you lose where that module was on your site.

We have (abstracted api layer) done and are testing it now - there was a TON of cough .. *wonderful* API changes - I would hate to be a normal DNN developer with alot of module code.

Which means I'm going to have to make a clean 4.x DNN install with just my modules and then run an upgrade and see if it works. I am not doing anything fancy so I am suspecting most of my code will work but still...