When you try to generate type library information by using the Microsoft.VisualStudio.Shell.Interop.dll assembly in Microsoft Visual Studio 2008, you may encounter one of the following symptoms.
When you use the Regasm.exe utility to generate and to register a type library, you may receive the following error message:
RegAsm: error RA000 : Type library exporter encountered an error while processing "Microsoft.VisualStudio.Shell.Interop.SVsSolutionObject, Microsoft.VisualStudio.Shell.Interop". Error: Type 'SVsSolutionObject' and type 'SVsSolution' both have the same UUID.
When you use the TlbExp.exe utility to generate a type library, you may receive the following error message:
TlbExp : error TX0000 : Type library exporter encountered an error while processing 'Microsoft.VisualStudio.Shell.Interop.SVsSolutionObject, Microsoft.VisualStudio.Shell.Interop'. Error: Type 'SVsSolutionObject' and type 'SVsSolution' both have the same UUID.
A Visual Studio 2008 package implements a property collection that is exposed by the EnvDTE.DTE.Properties property. If the collection is a member of an object that uses a type from the Microsoft.VisualStudio.Shell.Interop.dll assembly, the common language runtime (CLR) will not construct the necessary in-memory type library for the assembly. For example, the following Visual Studio macro that references the EnvDTE.DTE.Properties property will fail, and then you will receive an error message.
Dim proj As Project = DTE.Solution.Projects.Item(1) Dim props As Properties = proj.ConfigurationManager.ActiveConfiguration.Properties
This problem occurs because the ImportedFromTypelib attribute is removed from the Microsoft.VisualStudio.Shell.Interop.dll assembly in Visual Studio 2008. The ImportedFromTypelib attribute is removed because this assembly does not have an associated type library. Therefore, the ImportedFromTypelib attribute causes failures when the CLR tries to find an associated type library.
Because the ImportedFromTypelib attribute was removed in Visual Studio 2008, the CLR cannot construct the necessary in-memory type library for the Microsoft.VisualStudio.Shell.Interop.dll assembly. This failure is caused by duplicate type GUIDs.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site:
Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
You must have Visual Studio 2008 installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This hotfix marks all the duplicated GUIDs by setting the value of the ComVisible property to false so that the type library generator will ignore the duplicated GUIDs.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates