Mike,
I had started to hack my way down that route. Since there were no releases in a blank template (or
in this case IsProjBlankTpl.ism because it seems to be used be default) I added them with the same default names that the repackage wizard compiles with.
The problems & questions ran into were:
*) I figured out that I have to use a "Basic MSI Project" to be able to change the SetupLauncher setting to "No".
*) I could not change the compression setting without running the build wizard which then also compiles at the end. This seemed to give me some type of duplicate table error during the repackager's compile.
*) I am unsure whether running the compile at the end of the release wizard (required to change compression setting) causes any literal (non-template) values to be embedded in any of the ISM settings, etc.
*) Is matching the configuration and release name to the ones used in a default repackager compile the way to ensure that the appropriate release settings are performed automatically? Or will repackager use the only release if there is only one in the ISM?
Thanks for any additional help,
D.