Hi,
I migrated a VS 2003 add-in to VS 2005. The VS 2003 add-in
is a COM interface which must continue to be deployed as
a COM server. I have added the project output to the deployment
package and I set the Register property to vsdrpCOM.
If I look at the VS2005 MSI package generated with a viewer,
I find the the CLSID registry setting aren't in the package
This is because in VS2005, the Add-in's registration approach is different
from VS2003. In VS2003, you were required to register add-in assemblies
with Windows as COM components by using the Assembly Registration Tool
(regasm.exe) or via the setup package.
But these steps have changed in VS2005. You no longer need to register the
.NET assemblies with Windows by using regasm. Instead, you simply place the
assembly .DLL file into a specific directory (described later in this
topic) along with an XML file that has an .Addin file extension. This XML
file describes the information that Visual Studio requires to display the
add-in in the Add-In Manager.
So in VS2005 the XML registration method is simpler than the COM
registration method. This is the preferred method for using a Visual Studio
.NET 2003 managed add-in with Visual Studio 2005, and the VS2005 IDE will
not generate the VS2003 styled CLSID registry entry in the VS2005 Add-in's
setup package. Please refer to the following MSDN docs for the details:
Add-In Registration
http://msdn2.microsoft.com/en-us/library/19dax6cz
How to: Upgrade Visual Studio .NET 2003 Add-ins to Visual Studio 2005 by
Using XML Registration (Managed)
http://msdn2.microsoft.com/en-us/library/ms165632
Thanks!
Best regards,
Gary Chang
Microsoft Community Support
--------------------
Get Secure! ˇ§C
www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn
This posting is provided "AS IS" with no warranties, and confers no rights.
