Special Patch for web deployed setup

Ton_B · Post by **Ton_B** » Fri Aug 21, 2009 2:13 am

Hello,

I want to create a patch for our web deployed setup. But can't seem to get it to work.

This is the situation:

On a company server (for example: \\\\Server-01\\Files\\Setup) ther is our setup executable, so no internet connection is necessary.
We have done this, because this allows us to create 7Zip files for additonal install packages such as .NET

Now we want to create a Patch because we have only changed, added or removed one file.
I've read the IA Help and the White paper for cretating patches, but can't seem to get it to work and I'm a little confused.

This is the problem:

Once created the inital setup, I've created the patch "project" as explained in the White paper.
So far so good.

But when I run the patch it askes for the original location of the extracted setup files.
Reading the White paper i got a little confused, because it says that you only have to point out that location if you are deploying using a single file setup and not a web deployed setup?

But ok, I think i can live with that, but I really don't want to point out the location, because the setup must be run in silent mode.
I don't want any user interaction !

So I figured, Can I programmaticly set the folder.
I Probbably can, But what happens if the location in the users %temp% folder is removed?

This is really a common situation by our customers.
Most of the system administrators have a script to clean the users temp folder from time to time.
So I really cannot point to that location.

Asking the system administrator to exclude the folders with mia* when cleaning the temp folder is no option.

Any ideas ?

Thanks in advance

Ton Blokhuizen

MichaelNesmith · Post by **MichaelNesmith** » Fri Aug 21, 2009 5:35 pm

You should never get a prompt for sources when running with a web build - unless, some external program is nuking the cached source folder. Did you try on a clean VM first?

MichaelNesmith · Post by **MichaelNesmith** » Fri Aug 21, 2009 5:39 pm

PS: You can pass the source folder on the command line to the patch setup as described in the help file:

Specifying Original Setup Sources for Patching

To make sure the setup program does not prompt for the location of the original setup sources during a patch operation, you may use the patch source command line parameter.

<setup> /p=<original>\\dataIn the above example, setup.exe denotes the main setup executable, and original setup sources is the full path to the folder containing the original setup sources. Be sure to specify the data subfolder inside the original setup source folder (the data subfolder exists in all InstallAware setups built in uncompressed mode). For more information, see Patch Source Resolution.

Ton_B · Post by **Ton_B** » Mon Aug 24, 2009 1:52 am

No, I did not test it on a clean machine, I've tested it on my development machine.
I shall try it on a clean machine.

You are talking about, passing the setup location trough a command line.
I'm still wondering if this is the %temp% location or can I pass the location of the main setup folder (from wich you start the initial setup).

Ton_B · Post by **Ton_B** » Thu Sep 03, 2009 4:10 am

I've tested it on several clean machines, but they all promt for the original setup....

And although the exe is almost 10 times smaller than the original, it seems to take as much time to complete as the original.
Stange because I only added one small textfile to the patch.

What am i doing wrong ?