OEM-stamped software - installation and updates

Hello,
What is the best way for you to deliver new versions of your OEM-stamped software?

Currently, I’m manually modifying the ProductGuid inside the OemInstallerWizard XML file. This approach works well in terms of installation and software functionality, but it causes each installation to appear as a separate entry in the list of installed applications.

There is also the option of creating a custom installer that includes the modified and system files, as Paavo described. However, I’ve found this method to be unreliable.

For now, I plan to stick with the first approach, but I would appreciate any advice on how to avoid leftover entries in the installed applications—or any entirely new method you might recommend.

Thanks and regards, Miro

Miro,

I update My OEM application by creating a separate installer that patches the existing installed app.

Build you OEM app first, and from your target directory gather the files that you need to patch.

In my case i only need the main signed arx file and a resource dll.

copy “C:\Develop\Install\OEM-2022\Target\x64\\PF\Root\.arx” > nul
copy “C:\Develop\Install\OEM-2022\Target\x64\\PF\Root\scree.dll” > nul
Plus any other files that have changed /updated/needed

I then add these files to a self extracting zip file (7-ZIP) which will update the installed app.

Cheers

Rick