(Re)Registering a newer DLL

[ssearles]

I've got an existing installer that I'm trying to upgrade. Part of that upgrade is the replacement and reregistering a DLL with a newer version. Now the previous installer had successfully registered the older version without a problem, and the newer installer for a brand new installation works fine with the new DLL.

The issue is when I try to upgrade an older installation, with the reinstall of the new MSI... I'm trying to find a bullet proof way to make sure the old DLL is replaced and reregistered without user interaction.


Has anyone run into this before or have a preferred/proven method I can use?


Thank in advance,

[Cosmin]

Hi,

If the old installation registered the DLL, it should also unregister it when uninstalled. To uninstall the old version when running your installer you can try one of the approaches explained here. If the uninstall of the old version doesn't unregister the DLL, you can try using a custom action in the new package to unregister it.

Regards,
Cosmin

[ssearles]

Ok, so if my older installer did it via a Custom Action (basically to run the regsvr32 command), but my new installer actually has the new DLL directly embedded, I should use a Custom Action again to unreg it, but the AI to register the new one?


Just wanted to make sure I'm understand you

[GabrielBarbu]

Hello,

Ok, so if my older installer did it via a Custom Action (basically to run the regsvr32 command), but my new installer actually has the new DLL directly embedded, I should use a Custom Action again to unreg it, but the AI to register the new one?

Yes, this is correct.

Regards,
Gabriel

[clintc]

Please ignore