MachineKiller, that is my post and that had to do with using a custom provider for the SQLDataProvider with my current version 4.4.1. Not on the upgrade.
I am seeing the SAME exact error as Hoopie, every time I try and upgrade my dev system. Thank god I have version control so I am not ruining things.
And leupold, while I appreciate your exact "checklist" post for a reference...But reposting it every time someone comes up with this error after they upgrade (there are like 10 threads in here with the same error), it gives no solution since I have done it about 20 times and everything the same result.
From what I have gathered (mind I am trying to go from 4.4.1 to 4.6.2)...(try to debug your converted 4.6.2 site with the VS project of the DNN framework(it won't compile) the core team has modified the windows authentication system and removed the name space "DotNetNuke.Security.Authentication" which is referenced in all of my custom skin controls for logging in. Also the legacy core login control. They have moved the actual signin control to the new "Authentication" folder under the admin directory. So you will have to go in and remove any code you have referencing that class/namespace.
They also made some methods in the ModuleController static, where they were not static before. So errors are being thrown there.
It looks like the new auth system was added to 4.5.5. So if users started on 4.5.5 and then upgraded to 4.6.2 the upgrade it probably worked ok. But anyone lower then 4.5.5 then you have to make some updates to code and files to get things to run.
I could be wrong, though on the versions.
So if you are trying to upgrade to 4.6.2, I would recommend holding off until one of the core guys chime in with a solution...I will post my findings back also if I get mine up.
tty