I'm tasked with making one of our driver sets capable of being added to a clients MSI installation.
The bulk of the work for "our install" is actually performed by a call to a DLL via a custom action. We have already completed most of the work to prove we can launch our install dll. As a stand-alone installation or as part of a merge-module this would be a sufficient solution.
The problem is that we release new versions of this driver set with additional features, bug fixes etc every couple months, as does our client with their parent installation.
I've discovered that if I change something in the merge module it won't merge.
Our driver files and install DLL are included in the binary table. the custom action dll extracts the files and installs them itself.
the only solution i can see so far is to delete the files from the binary table before performing the merge. I can't trust them to do this themselves.. lol
Whats the best way I can just give them a "new version" they can update their MSI project with?
Edited by deskey, 05 August 2004 - 18:41.
