New Version/Revision - automated
Posted: Thu Sep 05, 2024 3:41 am
Hi,
We have a setup that is created automatically by calling miabuild.exe with the appropriate parameters. Works great.
Now there is a new requirement and there should be an additional setup creation method: also script-driven, but a new version should be generated with a version number provided by the script.
For it to be a new version, the setup needs a new revision guid.
Both pieces of information are stored in the .mpr file and can be edited by the script.
At this point my problem is: I see the corresponding information when I look at the file, but there is no identifier like in an .ini file, the line number does not seem to remain constant when changes are made to the setup.
Is it safe to replace old with new version number and old with new revision guid or is there a unique and safe way to do thiss? Using the InstallAware UI is not an option here.
Is there a file format description available?
Kind regards
Anja
We have a setup that is created automatically by calling miabuild.exe with the appropriate parameters. Works great.
Now there is a new requirement and there should be an additional setup creation method: also script-driven, but a new version should be generated with a version number provided by the script.
For it to be a new version, the setup needs a new revision guid.
Both pieces of information are stored in the .mpr file and can be edited by the script.
At this point my problem is: I see the corresponding information when I look at the file, but there is no identifier like in an .ini file, the line number does not seem to remain constant when changes are made to the setup.
Is it safe to replace old with new version number and old with new revision guid or is there a unique and safe way to do thiss? Using the InstallAware UI is not an option here.
Is there a file format description available?
Kind regards
Anja