diffrence between regsvr32 and vsdrfComSelfreg

  • Thread starter Thread starter Lars Roland
  • Start date Start date
L

Lars Roland

Hi:

I have an msi package that contains my outlook addin. On some versions
of windows this package works and everything is fine, but on others the
dll that contains my addin does not seam to work. If i run regsvr32 on
these machines then it works again - In the setup file I have market the
file with the register option: vsdrfComSelfreg

So to sum it up - is there a difference between regsvr32 and
vsdrfCOMSELFREG ??? - and can this diference perhaps be caused by
different versions of the microsoft install service ????.

I know that this is perhaps not the right place for these questions - but
if someone has the answar or can guide me to a place where I should ask
them, then I will be happy.




Regards. Lars Roland
 
Hello Lars

Try using "vsdrfCOM" option
When you select this and build the MSI file, the registration entries are extracted at build time and stored in the MSI file. When the MSI file gets installed, the DLL is copied to the system and the required registry entries are created from the data in the MSI file, such as the CLSID, ProgId and type library information. The end result is the same as if the DLL self-registered, except that the DLL code was not actually called at install time. This can be particularly important if your DLL is linked to another DLL that hasn’t yet been installed and therefore would result in the DLL failing to load if it was called during the install.

Hope this helps you..
Ninad
 
Back
Top