That is a common problem when beta versions of Visual Studio
aren't fully uninstalled before the release version is installed, or when
Visual Studio's components are uninstalled in the wrong order.
Solution
FDBK21319#2: Remove Registry Entries that cause the problem
Thanks to Chris Adams:
http://www.eggheadcafe.com/forums/F...D=20592&INTID=6
To fix, check the following 3 regkeys :
HKEY_CLASSES_ROOT\CLSID\{7D23CCC6-A390-406E-AB67-2F8B7558F6F6}\InprocServer*32
HKEY_CLASSES_ROOT\CLSID\{FD5CD8B1-6FE0-44F3-BBFB-65E3655B096E} \InprocServer32
HKEY_CLASSES_ROOT\CLSID\{FEDB2179-2335-48F0-AA28-5CDA35A2B36D}\InprocServer*32
Under (expand) InProcServer32, look for the presence of a non-2.0.0.0 (example 2.0.36.0)
and remove it. It has a reference that causes this to break.
WARNING : don't fool with the registry if you are not proficient doing that.
Option B
You can work around the problem, if editing the registry doesn't fix it, by using
Denis Bauer's ASP.NET Version Switcher to switch ASP.NET versions.
http://www.denisbauer.com/NETTools/...onSwitcher.aspx
While it doesn't edit ASP.NET configuration files, at least it allows you
to pick the version of the framework will be used for specific websites.
Here's instructions on how to manually uninstall beta versions of Visual Studio 2005
http://msdn.microsoft.com/vstudio/s...ll/default.aspx
Or, you might want to use the VS 2005 beta cleanup tool.
http://go.microsoft.com/fwlink/?LinkId=47598
Source: http://www.thescripts.com/forum/thread559064.html
No comments:
Post a Comment
You don't necessarily need to register to comment here.