Patching Vs Versioning - Advanced Installer Community
89jase
Posts: 6
Joined: Wed May 28, 2014 7:19 am

Patching Vs Versioning

Hi all

I've been experimenting with a few ways to install weekly patches and cannot find a consistent result, hoping I could get something cleared up.

So my business release patches weekly as an MSI pushed through SCCM.
At the moment these are just Normal MSI's with a new ID generated each time (new project) and are is NO version.

I want to include version in attempts to automate this, but need to understand about file over-writes and removing other files. As follows is an example.

myApp v1.1
has files a.txt, b.txt and c.txt in the Project / MSI

myApp v1.2
has files c.txt(updated) and d.txt in the Project / MSI

when I install myApp 1.2 the result I want is
a.txt, b.txt, c.txt(updated) and d.

Due to file size limitations I cannot include all files for each build. Is this the right approach to take, or will this example remove files a.txt and b.txt when v1.2 is installed? If files a.txt and b.txt are removed, what's the best approach to take?

Thanks all, I'm just having trouble getting a consistent outcome so understanding the logic would be a great help!
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Patching Vs Versioning

Hi,

In your example, if you create a major upgrade (new version) which contains only the "c.txt" (updated) and "d.txt" files, then the "a.txt" and "b.txt" will be removed and only the files contained by the new version will be installed on the machine.

However, if you create a patch, it will contain only the "c.txt" (updated) and "d.txt" files, but after the installation all the files will be kept on the machine.

To create a patch you can follow steps described in the Authoring a Windows Installer patch tutorial.

Let us know if this helped, otherwise give us more details about your scenario.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
89jase
Posts: 6
Joined: Wed May 28, 2014 7:19 am

Re: Patching Vs Versioning

Thanks for your reply and clearing that up.

One small follow up question, I'm doing all this through command line, how would I indicate to do the patch?

From the UI when I increment the version it and click save I'll get the prompt asking if I want a Patch or Major Update

When I set the version through command line I do-not get the prompt. Is there any additional param to pass it knows to make a patch? What's the default behavior? Patch or Major Update?
Below is a Generated parameter file I pass into the command line of Advanced Installer. (This file is generated through a python script)

Code: Select all

;aic
SetVersion 8.11
DelFolder APPDIR\a
DelFolder APPDIR\b
DelFolder APPDIR\c
DelFolder APPDIR\d
AddFolder APPDIR\ C:\AutoMSI\TempBuildFiles\a
AddFolder APPDIR\ C:\AutoMSI\TempBuildFiles\b
AddFolder APPDIR\ C:\AutoMSI\TempBuildFiles\c
AddFolder APPDIR\ C:\AutoMSI\TempBuildFiles\d
SetPackageName "myApp v8.11.msi" -buildname DefaultBuild
Save
Rebuild
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Patching Vs Versioning

Hi,

If you set a higher version from command line the "Major Upgrade" option will be used by default. However, if you want to make a patch, you can send the -noprodcode parameter.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
89jase
Posts: 6
Joined: Wed May 28, 2014 7:19 am

Re: Patching Vs Versioning

Excellent, Thanks a bunch!
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Patching Vs Versioning

You're welcome. Glad to help.

Just let us know anytime you have a question.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”