What does the installer need a CLSID for? Are you talking about the
ProductCode and UpgradeCode GUID's?

Those are generated when you create/add the setup program if you're using
the VS installer. You leave the UpgradeCode alone to preserve COM
compatibility for updates and you change the ProductCode for each version
change. That tells Windows Installer that it's the same program but a new
version.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Ojas" wrote in message
...
I am working on an installer for a VSTO 2005 SE plug-in for Outlook
2007.

The installer needs a CLSID for the plug-in. The plug-in is written
using C# and .NET 2.0.

For the plug-in CLSID I place in the Windows registry, do I use the
plug-in's assembly's GUID? Or, do I just create a new GUID and use
that one consistently? Or, what?