This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
A new Flexera Community experience is coming on November 25th, click here for more information.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Flexera Community
- :
- AdminStudio
- :
- AdminStudio Forum
- :
- Re: best path to "update" an MSI?
Subscribe
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
best path to "update" an MSI?
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok, I have deployed a repackaged app, it works perfectly. Now i have an update for this app. I have repackaged the entire app again with the update, and also just the differences (hopefully).
my question is, which is the best method of doing this? I want to update the msi on the machine as it has several 200mb+ databases in the app, and none of these is updated.
Should i create the difference msi with the same product code and run there? should i create the whole package with the same product code?
should i create a patch package (for gods sake tell me i dont have to do that manually as it appears) and apply that to the original msi?
I cant really find any good informations on this, all i find is "patch package is beyond the scope of this book" nice one bob baker...
I have the following books as well as online help etc:
Admin guide to repackaging and deployement (baker dickau)
Getting started with installshield and installer setups (baker)
official installshield for windows installer developers guide (baker)
Can anyone point me to a step by step or at least some useful info?
my question is, which is the best method of doing this? I want to update the msi on the machine as it has several 200mb+ databases in the app, and none of these is updated.
Should i create the difference msi with the same product code and run there? should i create the whole package with the same product code?
should i create a patch package (for gods sake tell me i dont have to do that manually as it appears) and apply that to the original msi?
I cant really find any good informations on this, all i find is "patch package is beyond the scope of this book" nice one bob baker...
I have the following books as well as online help etc:
Admin guide to repackaging and deployement (baker dickau)
Getting started with installshield and installer setups (baker)
official installshield for windows installer developers guide (baker)
Can anyone point me to a step by step or at least some useful info?
‎Feb 13, 2003 02:50 AM
(2) Replies
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
right i have just spent a few minutes in the developer forum and the general feeling there is upgrades(major/minor) are the best way to go.
However, according to everything i have read i must alter the package manually for all the files? there are a little over 700 altered files and registry settings??? Can i repackage the whole new thing, give it the same name as before, a different product code and give it the product code of the previous application as upgrade info? I think this is how it should be done (unless i completely misunderstood)
man this is confusing stuff today...
However, according to everything i have read i must alter the package manually for all the files? there are a little over 700 altered files and registry settings??? Can i repackage the whole new thing, give it the same name as before, a different product code and give it the product code of the previous application as upgrade info? I think this is how it should be done (unless i completely misunderstood)
man this is confusing stuff today...
‎Feb 13, 2003 03:06 AM
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
To me, it sounds like you need to apply a Minor upgrade through patching.
Repackage from scratch
maintain the same productcode
up the ProductVersion property
Use ConflictSolver to make sure that your component codes match from the old version to the new one (very important for minor upgrades)
you should then be able to make a patch which represents the differences in the packages
looeee
Repackage from scratch
maintain the same productcode
up the ProductVersion property
Use ConflictSolver to make sure that your component codes match from the old version to the new one (very important for minor upgrades)
you should then be able to make a patch which represents the differences in the packages
looeee
‎Feb 17, 2003 09:37 AM
Related Content
- Unable to publish applications to Intune with an error message "The Win32LobApp must have a valid value for the SetupFilePath property in AdminStudio Forum
- Unable to perform Online Activation even after having an internet connection on the machine where AdminStudio is installed in AdminStudio Knowledge Base
- How and Where to Change the Default Download Folder Path for Package Feed Module in AdminStudio Knowledge Base
- PSADT 'Wrap on import' output directory using variables in path in AdminStudio Forum
- Updating PowerShell App Deploy Toolkit - Bug? in AdminStudio Forum
