Visual Studio Common IDE Package error

[Darren]

I installed 2005 Beta 2 Team System today (4/17). I believe it was released
on MSDN Subscriber downloads on 4/14. I followed the uninstall procedure as
documented in subscriber downloads. Uninstall worked perfectly....seemingly,
no errors. I rebooted and installed beta2. When the IDE starts I get 6 or
so of these error messages

---------------------------
Package Load Failure
---------------------------
Package 'Visual Studio Common IDE Package' has failed to load properly (
GUID =

{6E87CFAD-6C05-4ADF-9CD7-3B7943875B7C} ). Please contact package vendor for
assistance. Application

restart is recommended, due to possible environment corruption. Would you
like to disable loading this

package in the future? You may use 'devenv /resetskippkgs' to re-enable
package loading.
---------------------------
Yes No
---------------------------

Followed by this error message
---------------------------
Package Load Failure
---------------------------
Package
'Microsoft.VisualStudio.QualityTools.TestCaseManagement.QualityToolsPackage,

Microsoft.VisualStudio.QualityTools.TestCaseManagement, Version=8.0.0.0,
Culture=neutral,

PublicKeyToken=b03f5f7f11d50a3a' has failed to load properly ( GUID =

{A9405AE6-9AC6-4F0E-A03F-7AFE45F6FCB7} ). Please contact package vendor for
assistance. Application

restart is recommended, due to possible environment corruption. Would you
like to disable loading this

package in the future? You may use 'devenv /resetskippkgs' to re-enable
package loading.
---------------------------
Yes No
---------------------------

Is there any fix or work-around for these errors?

Thanks,
Darren

[Belsterling@discussions.microsoft.com Mark Belsterling]

Darren,

I had the same problem. Thomas Krause found a solution to a similar
problem. I uninstalled all of the duplicate Microsoft.VisualStudio.* in the
assembly directory (the duplicate Microsoft.Visual itself had to be removed
last because of depenencies) and our problem was resolved. Just make sure
you open the property and click the version tab to get the version number.
Uninstall the earlier version.

Thomas wrote:

There are also a few other assemblies which exist twice. Maybe uninstalling
them can also solve other problems.

Thomas Krause

"Thomas Krause" <nospam.forum.thoma...@abc.de> wrotes:
> Here is the solution for all the problems:
>
> After looking closer at the error:
> Method not found: 'Int32
> Microsoft.VisualStudio.Shell.Interop.IVsErrorItem.GetCategory(UInt32
> ByRef)'.,
>
> I tried to copy out the assembly from the GAC and inspected it with the
> object browser. Everything looked normal and I actually found the Method
> with this signature, but after looking again in the GAC I saw that there
> were 2 versions of the Microsoft.VisualStudio.Shell.Interop.8.0 assembly.
> The only difference was that one of them had architecture MSIL and the
other
> had no architecture given. I inspected both assemblies and found that one
of
> them had another signature for this method:
> public int
>
GetCategory([System.Runtime.InteropServices.ComAliasNameAttribute("Microsoft
> .VisualStudio.Shell.Interop.VSERRORCATEGORY")] out
> Microsoft.VisualStudio.Shell.Interop.VSERRORCATEGORY[ ] pCategory)
>
> instead of the expected:
> public int
>
GetCategory([System.Runtime.InteropServices.ComAliasNameAttribute("Microsoft
> .VisualStudio.Shell.Interop.VSERRORCATEGORY")] out uint pCategory)
>
> So I copied both assemblies out of the cache and looked into the property
> page of the MSIL-dll to find out the 'real' dll-version: Verion:
> 8.0.40607.16 (beta1.040607-1600). The other assembly had the right:
> 8.0.50110.28 (pd7.050110-2800).
>
> After a simple manual uninstall from the GAC all 3 errors disappeared.
Even
> a fourth error (Help not installed), that I did not mention disappeared.
>
> Now I'm really proud of me, thanks for listening ;-)
>
> So just go to C:\Windows\assembly and right click on
> Microsoft.VisualStudio.Shell.Interop.8.0 (the one where MSIL is in the
> Processor Architecture Column) then choose uninstall and everything should
> work!
>
> Of course I'm not responsible for any negative results from this action.
>
> Thomas Krause

[fdn...@gmail.com]

Perfect! That fixed everything. I would've never thought to look in
the assemblies directory. Thank you very much!

Darren