mat_bruges
Posts: 33
Joined: Tue Mar 11, 2008 12:28 am

COM Registration does not refresh new version

Hi,

It took me a while to figure out why my application worked OK on my own machine, but failed on the client's machine.. but I finally figured it out:

I have a .NET Assembly that exposes a COM object. In the file properties of my assembly I specify "Auto Register file" and "Register .NET Assembly for COM Interop".

This works OK the first time you do it. It creates the required registry keys etc..

But when I did a new build (with modified version number) and I rebuilt the setup package, the registry keys for COM (CLSID\<ID>\InProcServer32\<version number>) were not updated. So when the new build was deployed on another machine, the COM object could not be loaded.

The workaround seems to be to open the assembly properties, uncheck the "Auto Register File" checbox, close the dialog, re-open the assembly properties, check the "Auto Register File" checkbox, close the dialog.

Since I have 4 merge modules I have to do this 4 times with every build. It also means I can not perform an automated build using the command line, I have to do it manually every time.

Can you please fix this?

Thanks

Mat
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: COM Registration does not refresh new version

Hi,

Currently this is not supported by Advanced Installer. However, we have this improvement on our TODO list and it will be available in a future version of Advanced Installer.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”