http://support.microsoft.com/kb/307367
For a COM module, you have the options of *COM*, *COMRelativePath*, and * COMSelfReg*. Any one of those three options will register the COM module during the installation. Note the following details about each choice: 1. *COM*: The module will be registered as a COM object by the Windows Installer engine. The deployment project will update the Class table, ProgID table, and other tables in the Registry Tables group of the corresponding .msi file. This is the recommended way to register a COM module. 2. *COMRelativePath*: The module will be registered as an isolated COM object by the Windows Installer engine. Note that this module will be used only by the application that the module is installed with. 3. *COMSelfReg*: The installer calls the *DllRegisterServer* function of that module at the time that you install the module and the * DllUnregisterServer* function at the time that you uninstall the module. The deployment project will update the SelfReg table of the corresponding .msi file. It is not recommended that the installation package use self-registration. Instead, the installation package should register modules by authoring one or more of the other tables provided by the installer for this purpose (that is, select the *COM* or *COMRelativePath* options). Many of the benefits of having a central installer service are lost with self-registration, because self-registration routines tend to hide critical configuration information. http://amiraryani.wordpress.com/2009/08/07/visual-studio-setup-deployment-project/ http://msdn.microsoft.com/en-us/library/w4dsy50b(v=VS.80).aspx you properly already read all this, but just incase i sent it On Wed, Jan 19, 2011 at 1:51 PM, Greg Keogh <[email protected]> wrote: > Hi Noobie, I'm using a Custom Action now to set special folder > permissions and a few other smaller tweaks during install. I just wasn't > sure if one of the standard vsdrfXXX values would do what I want with a EXE > COM server (they're poorly documented). Worst of all I have no idea how to > set the custom permissions on a 32-bit COM server, although it's probably a > fragile registry change which I would have to ensure works correctly on > different Windows. > > > > I've been meaning to study Wix, but time defeats me. I didn't know there > was a VS2010 extension, so that's good news worth looking at. > > > > Greg >
