Output filenames for patch installers

[Fig]

Q: When building an web install project that includes a patch reference (e.g. patches an existing install) should the name of the output .exe remain unchanged?

Example for application XYZ.
XYZ v1.0.0 Product Version=1.0.0 Output file=XYZ10.EXE
XYZ v1.0.1 Product Version=1.0.1 Output file=XYZ10.EXE ?
XYZ v1.0.2 Product Version=1.0.2 Output file=XYZ10.EXE ??


The installer for v1.0.1 would use the v1.0.0 base project but:
- include a patch reference to XYZ10.EXE (from v1.0.0)
- change the Product Version number to 1.0.1
- Revision Code would change automatically as part of the build.

The installer for v1.0.2 would:
- include a patch reference to XYZ10.EXE (from v1.0.0)
- include a patch reference to XYZ10.EXE (from v1.0.1).
- change the Product Version number to 1.0.2
- Revision Code would change automatically as part of the build.



Q: From my example above, Would the XYZ10.EXE from v1.0.2:
- patch an EXISTING user's XYZ app from v1.0.0 to v1.0.2 ?
AND
- patch an EXISTING user's XYZ app from v1.0.1 to v1.0.2 ?
AND
- perform an INITIAL install of XYZ on a new user's machine?


I appreciate your time. I think I'm getting a handle on the patch but need a little help understanding the output filename.

[Didier44]

have yiou got ansvers about your questions ?
I have the same interrogations about name of output files : I use InstallAware express 7 R2 and if I set the same name for the patch than this used in the original setup project it seems that patch run well; but if i use an othe name for the output file name of my patch it fails !!!!!!

Thanks to sya me if you have solved this problem

[mills]

I always rename the patch filename after it's generated.

If you have a version say 1.2 and you have patch references to 1.0 and 1.1, then the 1.2 patch will be able to patch 1.0 and 1.1 to 1.2.

In the above case, I would name that setup_patch_1_0_and_1_1_to_1_2.exe

(if you have many past versions being patched, you may be able to come up with a more elegant naming solution).

I'm usually testing a single patch instance effects with a basic setup, so I have a setup called "My Setup.exe" and I usually have a patch that is generated as "My Setup.exe" which I rename to "My Setup patch.exe".

I think the point is that I don't worry about what the patch name is generated as. I expect it to match my setup and to rename it something reasonable myself.

Does that clarify things at all?

[Didier44]

Thank you Mills for your answer ;
it confirms what i thought
By