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
- :
- Patch Design - Multiple Previous Setups - Missing file
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
‎Sep 16, 2009
07:49 AM
Patch Design - Multiple Previous Setups - Missing file
Hello,
My first post here so a bit of introduction - I'm Marcin from Poland 🙂
Straight to the problem:
- Create an InstallScript MSI project - Product Version: 4.7.701.0
- Create a single feature called "DefaultFeature" with a single component "FirstFile" that has a single key file "1.txt"
- Build the project and move the output to folder "Build701"
- Update Product Version to: 4.7.702.0
- Add a new component to "DefaultFeature" called "SecondFile" containing single key file "2.txt"
- Add Minor Upgrade Item pointing to .msi from "Build701" folder
- Build the project and move the output to "Build702" folder
- Update Product Version to: 4.7.703.0
- Add a new component to "DefaultFeature" called "ThirdFile" containing a single key file "3.txt
- Build the project and move output to "Build703" folder
- Add a new patch configuration
- Point latest setup path to "Build703" .msi file
- Add two previous setups - first one pointing to "Build701" .msi and second one referencing "Build702" .msi file.
- Build the patch
- Install "Build701"
- Run Update.exe to update "Build701" -> "Build703"
- Patching completes successfully but file 2.txt is not being created <- that's the problem.
I'm thinking it's my lack of understanding. Can anyone help, please?
Cheers!
Marcin.
My first post here so a bit of introduction - I'm Marcin from Poland 🙂
Straight to the problem:
- Create an InstallScript MSI project - Product Version: 4.7.701.0
- Create a single feature called "DefaultFeature" with a single component "FirstFile" that has a single key file "1.txt"
- Build the project and move the output to folder "Build701"
- Update Product Version to: 4.7.702.0
- Add a new component to "DefaultFeature" called "SecondFile" containing single key file "2.txt"
- Add Minor Upgrade Item pointing to .msi from "Build701" folder
- Build the project and move the output to "Build702" folder
- Update Product Version to: 4.7.703.0
- Add a new component to "DefaultFeature" called "ThirdFile" containing a single key file "3.txt
- Build the project and move output to "Build703" folder
- Add a new patch configuration
- Point latest setup path to "Build703" .msi file
- Add two previous setups - first one pointing to "Build701" .msi and second one referencing "Build702" .msi file.
- Build the patch
- Install "Build701"
- Run Update.exe to update "Build701" -> "Build703"
- Patching completes successfully but file 2.txt is not being created <- that's the problem.
I'm thinking it's my lack of understanding. Can anyone help, please?
Cheers!
Marcin.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 16, 2009
08:32 AM
Just solved the problem by manually fixing ISTargetImage table (Order column - it should be "2" for "Build702" and "1" for "Build701")
What's intersting - the Order value generated by IS is wrong for my patch no matter if I add "Build701" or "Build702" as a first Previous Setup.
Marcin.
What's intersting - the Order value generated by IS is wrong for my patch no matter if I add "Build701" or "Build702" as a first Previous Setup.
Marcin.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 07, 2009
10:12 AM
Thank you for answering your question. This solved our problem. The problem seems inconsistent within our product line. The sequence is "incorrect" in all of are products but the problem only showed up in one of them. When this happened, our missing patch files in question changed between our GA release and Patch 1 but DID NOT change between Patch 1 and Patch 2. Not sure if this is what triggers the problem when applying Patch 2 only. We were using InstallShield 2008 on our MSI project.