If you only have one InstallShield 'Releases' configuration, then you might not have this problem as it will incidentally be the 'Default Configuration' every time. It is also worth noting that if you rely on a combination (or have multiple) Visual Studio build configurations that expect to be paired with different InstallShield 'Releases' configurations then you may have to hand-edit the InstallShield project files or Visual Studio solution files in order to build the different 'Releases' of the installer depending on how your continuous integration is set up. This particular setting is also not something that can be set if you decide to use the InstallShield 2022 R1 Application GUI either since that setting is in the. It is also worth noting that if your InstallShield project has multiple "Release" configurations that you cannot change the InstallShield "Default Configuration" of the release from within Visual Studio 2022. This includes not even updating the version number of the MSI nor adding/removing of files through Visual Studio 2022. I can confirm that while this version does allow you to build existing InstallShield projects within Visual Studio 2022, you cannot edit the installer project in anyway. The organization I work for recently purchased an InstallShield 2022 R1 license (Premiere) for over $7,000. ![]() ![]() ![]() ![]() Support for creating new projects wouldn't be supported in 2022 R1. InstallShield 2022 R1 will include support for upgrading and building existing InstallShield projects in Visual Studio 2022, via UI and MSBuild.
0 Comments
Leave a Reply. |