Hi Everyone,
I have a question about patching and how IA works out what files to patch. I believe that it works out what to patch based on a binary diff of the files - correct? If so, is there any way to do it based on Assembly versions rather than diffs? The reason is that we do clean builds for all release/patches and have the Assembly versions set by the build - i.e. AssemblyVersion is 1.0.*. Now, this means that whenever a build is done, the DLL may not change but the version number has! Also, even if I don't change the version number (fix it to 1.0.0.0, for example), the fact that the DLL gets compiled means that the date in the file is different which means that, again, the patch program picks it up as having changed!
So, any suggestions or best practices would be most appreciated.
Thanks,
Andy.
Patching questions and how to Version files in VS
Re: Patching questions and how to Version files in VS
I have the same "problem", maybe somebody has an idea.
Re: Patching questions and how to Version files in VS
The current behavior a restriction imposed by the MSI Patch APIs.
We are looking into ways to work around this to provide the features you are seeking.
We are looking into ways to work around this to provide the features you are seeking.
Andy Mills
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.

