The use of compiler variables to customize setup at build time and have setups for different products is really a nice feature to have, when only very few things change between them, having a unique setup project.
However, how such approach doesn't break the Patch requirements when the elements that I need to have different are: Product Name, Product Code, Product Version and files/features and such differentiation breaks the Patch Requirements?
Break of Patch Requirements
-
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
As long as the compiler variable values are the same in the patch reference setups and the patch being built, you should not run into any issues.
Michael Nesmith
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
-
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
Yes, of course!
Michael Nesmith
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
-
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
Use whatever names you like, and enter in those variables using the form #NAME# into the respective hard coded fields. Then just use whatever values you like for those newly created compiler variables (use the Project Options dialog to define them, and you can assign/override default values there, or use the command line build tool).
Michael Nesmith
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
Who is online
Users browsing this forum: No registered users and 42 guests