vidur
Posts: 43
Joined: Thu Jul 31, 2014 4:21 am

Patching Files that werent installed

Hi,

I have a Scenario where on an older version of my software (say 4.1.2.1) i was skipping to install a file on a Windows 8 OS .

But now in my newer Version (say 4.1.3.0) I need that file there on windows 8. So to achieve this I removed the condition to not install on windows 8.

This works fine on a fresh installation, however when i create a patch the file does not get patched (or installed)

Is there anyway i can force this file to be installed on a patch.

Thanks
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Patching Files that werent installed

Hello,

First off please keep in mind that the fourth version number is completely ignored by Windows Installer.

Are you creating a patch as described in the Authoring a Windows Installer patch tutorial? Creating a patch implies a very delicate setting process which keeping the patch rules. Most likely one of the rules is broken for that file's component.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
vidur
Posts: 43
Joined: Thu Jul 31, 2014 4:21 am

Re: Patching Files that werent installed

Hi,

I have followed the patch rules as instructed at http://www.advancedinstaller.com/user-g ... tches.html .

Maybe i wasn't clear on my scenario.

1.) In the old version of my software(4.0.0.0) i have a file say "Application.exe"(version 1.0.0) . In the condition of the component I set it to "FALSE" (which means do not install)

2.) In my new version of my software (4.0.1.0) i have the same file "Application.exe"(version 2.0.0) . I have removed the "FALSE" condition from the component (which means i want it to install).

Now when i create a patch using these to versions, and run the patch. Will "Application.exe" be installed or not?

*from my experience it will not be installed. Is there a way i can work around this?

Thanks
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Patching Files that werent installed

Hello,

Thank you for the detailed explanation. I tested this and indeed the consecutive projects cannot be compatible because of the component condition.

In this case the only solution is indeed as you noticed to roll out a major upgrade, not a patch.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”