I just installed the VS 2005 final on a machine that has had no beta software installed on it (just the prior version of VS 2003 - which i removed before installing 2005) and when i started it i get errors about "Package Load Failure" or the "visual studio common ide package". I've found some post about this proble in beta 2 and they seem related to not uninstalling the previous beta correctly... but i am installing this brand new... why would i be getting this error.

Package Load Failure - VS 2005 Final Release
wuebbel
Also, does the IDE work and just have an error or are you blocked
Finally, you certainly can repair VS to see if that helps. We have done a lot in VS 2005 to make repair work a lot better than previous releases. One draw back is that we repair everything we can, which may lead to reboots during repair. For this release we decided that a full complete repair with reboots is better than a weaker repair function.
Thanks.
Bret
VS/.NET setup team
Bradrover
hagan3
http://astebner.sts.winisp.net/Tools/ttool.zip
RobDob
I then did a repair install which didnt help at all either.
In the end I had to go through the GAC manually and found 3 dlls that had the 8.0.40xxx version number. Once I deleted those it worked fine with no errors.
I still have no idea how i got those versions on my machine... i was careful never to install the beta so i wouldnt have these issues.
Now I am dealing with why VS freezes every time i try and open a .config file...
*sigh*
karch146802
Lazer
just seemed odd.
dham
THANK YOU!
MikeBe
Jeeva S
I'm having a similar problem.
Any ideas.When I start VS2005 I get 5 Package Load Failures.
Visual Studio Common IDE Package - GUID {6E87CFAD-6C05-4ADF-9CD7-3B7943875B7C}
If I open a WinForms app and double click on the form I get
Could not load type 'Microsoft.VisualStudi.Shell.Interop.IVsRunningDocumentTable2' from assembly 'Microsoft.VisualStuiod.Shell.Interop.8.0, Version 8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f11d50a3a. This is in the GAC.
I have tired a repair and it made no difference.
The only thing I might have done out of the ‘ordinary’ was install SQL 2005 first.
Dion
DBA_374
Dion
drehnstrom
Carlos Vara
I guess I've got nothing to loose trying the uninstall option and then reinstalling again.