"Minor" Upgrades - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

tgillitzer
Posts: 36
Joined: Tue Dec 13, 2011 12:12 am

"Minor" Upgrades

Having two issues with "Minor" Upgrades (or patches as AI seems to call them).

I am changing the product version and then selecting "Patch" on the dialog for Major Upgrade vs Patch. This is, as I understand it, is defined as a Minor Upgrade. I'm not making patch projects at this time.


1) My installer is using an EXE bootstrapper. I have selected the option to "Install MSI as Minor Upgrade (if applicable)" and to "Do not delete extracted MSI and CAB files".
I make 1.0.0.0 of my installer and install it. Success.
I make 1.0.1.0 of my installer, select Patch. Install it, I get the following error: A network error occured while attempting to read from the file: C:\Users\Administrator\AppData\Roaming\company\msi name\1.0.1.0\install\ScriptPro Health Messaging Services 1.0.0.0.msi.

The 1.0.0.0 MSI obviously wouldn't exist in the NEW msi version directory. It exists in its directory. This seems like a bug in AI.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: "Minor" Upgrades

Hello,

In order to create and deploy a patch installation package you should follow our "Patch Authoring" tutorial. Also, when creating patches you should make sure they don't break the patch rules.

If you have any questions let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
tgillitzer
Posts: 36
Joined: Tue Dec 13, 2011 12:12 am

Re: "Minor" Upgrades

Daniel, I am familiar with the patch process that creates separate .MSP files. I am not using this process.

My understanding is that I should be able to use the MSI to patch an existing installation as long as I follow the rules around Major vs Minor upgrades. Can you please explain why my process, which appears to be using all standard AI/MSI capabilities isn't an acceptable way to do what I am trying to do?

My process is working minus the issue where the new MSI is trying to access the MSI in the new directory. If I manually copy the original MSI into the new MSI directory it works fine.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: "Minor" Upgrades

Hello,

This may happen if the embedded MSI of your upgrade version of your installation package has a different name than the embedded MSI of your previous version. So, can you use the same name in the "MSI name" field, from "Media -> Configuration" tab, for both of your projects versions and see if the behavior still persist? If so, can you please send us both .AIPs (project files) to support at advancedinstaller dot com so we can investigate them?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
tgillitzer
Posts: 36
Joined: Tue Dec 13, 2011 12:12 am

Re: "Minor" Upgrades

I see, my MSI Name is "[|ProductName] [|ProductVersion]"

I was able to work around it by changing the extract path on that same page from
[AppDataFolder][|Manufacturer]\[|ProductName] [|ProductVersion]\install
to
[AppDataFolder][|Manufacturer]\[|ProductName]\install

Thanks
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: "Minor" Upgrades

You're welcome. I'm glad you got this working.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”