For anyone that has been using the Beta 2 and the new final release (Visual Studio 2005 Professional Edition) version 8.0.50727.42 (RTM.050727–4200) using the Microsoft .NET Framework Version 2.0.50727, I am afraid that I may have some bad news for you and for the team that released this version at Microsoft.

The symptoms of the bug that my IDE was experiencing when I was using the Beta 2 version was exactly the same as what Scott Hanselman said here. This would now be the third complete manual uninstall and reinstall of the new final release (Visual Studio 2005 Professional Edition) version 8.0.50727.42 (RTM.050727–4200) using the Microsoft .NET Framework Version 2.0.50727, and the usual started happening again:

The certain keyboard keys became non-functional such as the enter key. arrow keys, ctrl, alt, backspace, and shift keys ?!?!

NONE of the .NET Framework tool modules would load, or “the referenced assembly could not be loaded” ?!?!

The answer is some what trivial with ONLY 20/20 hind site vision after the source of the problem was identified. Your user setting file for Visual Studio 2005 some how corrupted itself during the installation or IDE loading process, and you must have the environment reset your user data file “again, which we all know should have been tracked and eliminated in the Beta 2 version.”

Quite certainly, the last time I checked we are all still human, including Microsoft, and we make mistakes. Even so, while the product was in Beta 2 version, I believe that knowledge of this problem existed way before the RTM date of the final release and SHOULD HAVE been taken care of. In stead we see this sort of thing propagating to the next version which sort of, kind of, just so happened to be a final release. I can already see the maintenance cost going though the roof…

Any who . . . to fix this nasty bug, close Visual Studio 2005, go to the root install folder for your version of Visual Studio 2005 and enter the following commands:

cd C:\<>\Microsoft Visual Studio 8\Common7\IDE\

devenv.exe /ResetUserData

or if provides yet another unexpected nicety use:

devenv.exe /?

command to uncover exactly what switch option will reset the user settings file and YOUR DONE!

To be quite honest, without reading a post like this to get the solution, you will probably think that your development environment is totally and utterly useless.

Hope this helps, now get back to work!

Comment Section

Comments are closed.

The opinions expressed in this public online diary are my own personal opinions, thoughts, and feelings and do not represent anyone else's view including family members, my employer, and friends in anyway, unless of course you believe in GOD and constantly need JESUS through Mother Mary with His power to save, heal, and instill forever peace like I constantly need him.

Matthew James k:

Matthew James k

Template theme by Medialoot