This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Enable Minor Upgrade Does the setup have to be named Setup.exe?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 09, 2012
03:15 PM
Enable Minor Upgrade Does the setup have to be named Setup.exe?
My setup is called myapplicationname_setup.exe
I want to update my applications exe files since we made some Minor changes to the code.
IS 2012 - from the Help it says
OK, I know code is unambiguous, but how about that statement in RED. Do I really have to call my setup "setup.exe", or is it OK to name as I have done .i.e myapplicationname_setup.exe?:confused:
Is it really looking for setup.exe or just looking for a setup naming match?
I want to update my applications exe files since we made some Minor changes to the code.
IS 2012 - from the Help it says
How Do You Get a Minor Upgrade to Work?:
If the latest version of your installation has the same product code as the previous version of your installation, you can apply a minor upgrade to update your product. By simply building a release that includes Setup.exe, your latest installation will be minor upgrade enabled. Setup.exe can detect when a previous version of your product exists on the target machine. When it detects this, it runs the rest of your installation in minor upgrade mode.
OK, I know code is unambiguous, but how about that statement in RED. Do I really have to call my setup "setup.exe", or is it OK to name as I have done .i.e myapplicationname_setup.exe?:confused:
Is it really looking for setup.exe or just looking for a setup naming match?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 10, 2012
08:08 AM
Any replacement name for setup.exe is fine (of course if it doesn't end in .exe you'd have other problems) - the contents, and in particular the MSI GUIDs are important. We just have to refer to it as something, and "the file commonly known as setup.exe" is ... cumbersome. 🙂
Note that Windows Installer minor upgrades do require the name of the .msi file to match, however, so be sure to keep that file's name consistent across your builds.
Note that Windows Installer minor upgrades do require the name of the .msi file to match, however, so be sure to keep that file's name consistent across your builds.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 10, 2012
08:23 AM
Thanks a lot for the info. I am just beginning to learn how to update my applications. BTW - I had one problem where one of my executables i was trying to update was not updating and discovered that when I made the exe from my application development interface (VB6) I had forgotten to set the versioning properties to auto increment, so even though I was making code changes, the executable never got overwritten on install because the versions were the same.:eek: