Re: [WiX-users] Does the msi-filename matter?
Dear Blair,
Thank you. I will do it this way then.
I only changed the approach a little bit:
1.) One main file (and lots of fragments etc.)
2.) For each version an environment variable needs to be set, e.g.
set VER=personal
set VER=corporate
set VER=demo
3.) Inside the main file I have e.g.:
?if $(env.VER) = corporate ?
?define UpgradeCode = 02C47FE9-0563-43d1-98D8-A23CBEBE18EA ?
?define LicenseRtf = license1.rtf ?
?elseif $(env.VER) = personal ?
?define UpgradeCode = CABA35A0-E3C6-4826-907E-461B04FC7E73 ?
?define LicenseRtf = license2.rtf ?
?elseif $(env.VER) = demo ?
?define UpgradeCode = FD80DD30-1E75-4f07-9105-654D855500D8 ?
?define LicenseRtf = license2.rtf ?
? endif ?
and so on. Then I just run
candle ...
...
set VER=personal
light ... -out personal.msi
set VER=corporate
light ... -out corporate.msi
set VER=demo
light ... -out demo.msi
The build environment is not the problem. I just have a build.cmd batch
file at the moment which executes all calls...
Regards,
Luke
Am 26.07.2010 21:07, schrieb Blair:
I worked a product where we took a set of WXS files and built them multiple
times varying a small number of inputs (such as compiler defines and/or
environment variables) and then linked each set of WIXOUTs into MSIs, as you
mention. I don't see a problem with that.
Not every build environment easily supports that approach, so you need to do
what works for your build system.
-Original Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent: Monday, July 26, 2010 3:56 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Does the msi-filename matter?
Dear Bob,
Am 25.07.2010 15:45, schrieb Bob Arnson:
On 7/25/2010 8:10 AM, Lukas Haase wrote:
However, there is also need to replace Product/@Id and
Product/@UpgradeCode ...
Use preprocessor variables and/or localization variables.
Thank you for your reply. This is what I already did with
-dLicense=License1.rtf.
But is this approach a good idea in general? I.e. this is my Main.wxs file:
?xml version='1.0' encoding='UTF-8'?
Wix xmlns='http://schemas.microsoft.com/wix/2006/wi'
Product Id='*' UpgradeCode='$(var.UpCode)' ...
[...]
WixVariable Id=WixUILicenseRtf Value=$(var.License) /
[...]
and call the compiler on the same file a few times to produce the
different MSIs? I.e.
candle Main.wxs -dLicense=License1.rtf
-dUpCode=13FE0C72-F630-4e66-AB2D-042F8B9556A5 -out Edition1.wixobj
candle Main.wxs -dLicense=License2.rtf
-dUpCode={A8E97AD2-3B6A-442f-8425-901459DD0B28 -out Edition2.wixobj
light ... Edition1.wixobj -out Edition1.msi
light ... Edition2.wixobj -out Edition2.msi
Another approach I could think of: Create a separate wxs file for every
project and use the Include-directive of the preprocessor to include
specific parts ...
Regards,
Luke
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does the msi-filename matter?
Dear Bob,
Am 25.07.2010 15:45, schrieb Bob Arnson:
On 7/25/2010 8:10 AM, Lukas Haase wrote:
However, there is also need to replace Product/@Id and
Product/@UpgradeCode ...
Use preprocessor variables and/or localization variables.
Thank you for your reply. This is what I already did with
-dLicense=License1.rtf.
But is this approach a good idea in general? I.e. this is my Main.wxs file:
?xml version='1.0' encoding='UTF-8'?
Wix xmlns='http://schemas.microsoft.com/wix/2006/wi'
Product Id='*' UpgradeCode='$(var.UpCode)' ...
[...]
WixVariable Id=WixUILicenseRtf Value=$(var.License) /
[...]
and call the compiler on the same file a few times to produce the
different MSIs? I.e.
candle Main.wxs -dLicense=License1.rtf
-dUpCode=13FE0C72-F630-4e66-AB2D-042F8B9556A5 -out Edition1.wixobj
candle Main.wxs -dLicense=License2.rtf
-dUpCode={A8E97AD2-3B6A-442f-8425-901459DD0B28 -out Edition2.wixobj
light ... Edition1.wixobj -out Edition1.msi
light ... Edition2.wixobj -out Edition2.msi
Another approach I could think of: Create a separate wxs file for every
project and use the Include-directive of the preprocessor to include
specific parts ...
Regards,
Luke
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does the msi-filename matter?
I worked a product where we took a set of WXS files and built them multiple
times varying a small number of inputs (such as compiler defines and/or
environment variables) and then linked each set of WIXOUTs into MSIs, as you
mention. I don't see a problem with that.
Not every build environment easily supports that approach, so you need to do
what works for your build system.
-Original Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent: Monday, July 26, 2010 3:56 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Does the msi-filename matter?
Dear Bob,
Am 25.07.2010 15:45, schrieb Bob Arnson:
On 7/25/2010 8:10 AM, Lukas Haase wrote:
However, there is also need to replace Product/@Id and
Product/@UpgradeCode ...
Use preprocessor variables and/or localization variables.
Thank you for your reply. This is what I already did with
-dLicense=License1.rtf.
But is this approach a good idea in general? I.e. this is my Main.wxs file:
?xml version='1.0' encoding='UTF-8'?
Wix xmlns='http://schemas.microsoft.com/wix/2006/wi'
Product Id='*' UpgradeCode='$(var.UpCode)' ...
[...]
WixVariable Id=WixUILicenseRtf Value=$(var.License) /
[...]
and call the compiler on the same file a few times to produce the
different MSIs? I.e.
candle Main.wxs -dLicense=License1.rtf
-dUpCode=13FE0C72-F630-4e66-AB2D-042F8B9556A5 -out Edition1.wixobj
candle Main.wxs -dLicense=License2.rtf
-dUpCode={A8E97AD2-3B6A-442f-8425-901459DD0B28 -out Edition2.wixobj
light ... Edition1.wixobj -out Edition1.msi
light ... Edition2.wixobj -out Edition2.msi
Another approach I could think of: Create a separate wxs file for every
project and use the Include-directive of the preprocessor to include
specific parts ...
Regards,
Luke
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does the msi-filename matter?
Dear Rob, Thank you for your reply. Am 23.07.2010 08:01, schrieb Rob Mensching: 1. You can have multiple .wxs files to create a single or set of MSI files. I recommend breaking your product down into useful chunks and putting them in Fragments then grouping the Fragments in logical files. Managing a product in a single .wxs file can be very challenging.smile/ I have already splitted my project into different files. However, the difference between my product is not only different files but also for example the WixUILicenseRtf WiX variable. I thought it is helpful to have a single Main.wxs file and compile the different flavours from that. The difference is handled with variables, for example: WixVariable Id=WixUILicenseRtf Value=$(var.License) / and then: candle Main.wxs -dLicense=License1.rtf -out Edition1.wixobj candle Main.wxs -dLicense=License2.rtf -out Edition2.wixobj light ... Edition1.wixobj -out Edition1.msi light ... Edition2.wixobj -out Edition2.msi However, there is also need to replace Product/@Id and Product/@UpgradeCode ... Is this a good idea? If not why? As said before, the different editions are more or less the same so I would like to prevent creating a separate wxs file for each edition because 99% of the contents would be the same. Even if I would only use fragments in different files, there is much information in the Main.wxs which would be redundant, e.g. Package, Condition, CustomAction, ... Regards, Luke 2. I think Burn would work very well for your scenario below. That doesn't help you since Burn isn't available yet and won't really be stable until early next year. They way things could work in Burn, is you could break 1 - 4 into 4 separate MSI package but make one Bundle. Then you can release ever increasing versions of the Bundle with various major or minor or small updates to the contained packages.Burn is smart enough to update only the MSIs that are newer... Basically, I think your scenario is best served by a multi-MSI design. The problem with multi-MSI design is you need a chainer to manage the install/unistall/update process. On Thu, Jul 22, 2010 at 12:37 PM, Lukas Haaselukasha...@gmx.at wrote: Thank you everybody for the discussion! The result is clear to me: I won't use minor- and small updates. One question concerning Best practice left for the deployment. In fact my application consists of: - Viewer (EXE, DLL, CHM) - Database (dat-file (80MB), bunch of PDFs) - License1.RTF, License2.RTF Now I ship my program in various flavours: 1.) Corporate edition with License1.RTF 2.) Private edition: Everything the same except License2.RTF 3.) (private) Network edition: Same as (2) except the name 4.) Demo version: Modified Database (30MB instead of 80MB) And finally each (1)-(3) get updates every few months. At first I thought with WiX it would be possible to just create one installer for all of those. But according to the discussions so far, am I right to just generate separate projects (wxs files) for each of the cases above? And according to the updates: Each of the (1), (2), (3), (4) shares the same UpgradeCode, doesn't it? Regards, Luke Am 22.07.2010 05:28, schrieb Christopher Painter: I wrote thatI had read several blog posts over the years and cited one of them as Vagmi and couldn't recall who the others were. I didn't say any of them were from you. In fact, I recall you writing a post about why WiX uses Major Upgrades and I referred to that as vindication; evidence that we have shared beliefs. BTW, I could ask you the same question considering your still unapologetic personal attack on me several years ago. I still believe that if we ever met in real life we'd hit it really well. I for one sure wish you could spend some time in Austin seeing the work I've done combining WiX with InstallShield. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Rob Menschingr...@robmensching.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 10:10:42 PM Subject: Re: [WiX-users] Does the msi-filename matter? I think you have me confused with someone else. I've always had the stance: If you can use a Major Upgrade do so. Life is too short to deal with the difficulties otherwise. What else have you told people I believe?smile/ On Wed, Jul 21, 2010 at 7:53 PM, Christopher Painter chr...@deploymentengineering.com wrote: Rob- I seem to recall several blog articles years ago talking about how major upgrades are ugly. One was from an active blogger at the time ( Vagmi ) but I don't remember the others. http://geekswithblogs.net/Vagmi.Mudumbai/archive/2006/06/11/81426.aspx Blair- My MSI mojo is good, but what development throws over the wall to me
Re: [WiX-users] Does the msi-filename matter?
On 7/25/2010 8:10 AM, Lukas Haase wrote: However, there is also need to replace Product/@Id and Product/@UpgradeCode ... Use preprocessor variables and/or localization variables. -- sig://boB http://joyofsetup.com/ -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does the msi-filename matter?
Couple things: 1. You can have multiple .wxs files to create a single or set of MSI files. I recommend breaking your product down into useful chunks and putting them in Fragments then grouping the Fragments in logical files. Managing a product in a single .wxs file can be very challenging. smile/ 2. I think Burn would work very well for your scenario below. That doesn't help you since Burn isn't available yet and won't really be stable until early next year. They way things could work in Burn, is you could break 1 - 4 into 4 separate MSI package but make one Bundle. Then you can release ever increasing versions of the Bundle with various major or minor or small updates to the contained packages.Burn is smart enough to update only the MSIs that are newer... Basically, I think your scenario is best served by a multi-MSI design. The problem with multi-MSI design is you need a chainer to manage the install/unistall/update process. On Thu, Jul 22, 2010 at 12:37 PM, Lukas Haase lukasha...@gmx.at wrote: Thank you everybody for the discussion! The result is clear to me: I won't use minor- and small updates. One question concerning Best practice left for the deployment. In fact my application consists of: - Viewer (EXE, DLL, CHM) - Database (dat-file (80MB), bunch of PDFs) - License1.RTF, License2.RTF Now I ship my program in various flavours: 1.) Corporate edition with License1.RTF 2.) Private edition: Everything the same except License2.RTF 3.) (private) Network edition: Same as (2) except the name 4.) Demo version: Modified Database (30MB instead of 80MB) And finally each (1)-(3) get updates every few months. At first I thought with WiX it would be possible to just create one installer for all of those. But according to the discussions so far, am I right to just generate separate projects (wxs files) for each of the cases above? And according to the updates: Each of the (1), (2), (3), (4) shares the same UpgradeCode, doesn't it? Regards, Luke Am 22.07.2010 05:28, schrieb Christopher Painter: I wrote thatI had read several blog posts over the years and cited one of them as Vagmi and couldn't recall who the others were. I didn't say any of them were from you. In fact, I recall you writing a post about why WiX uses Major Upgrades and I referred to that as vindication; evidence that we have shared beliefs. BTW, I could ask you the same question considering your still unapologetic personal attack on me several years ago. I still believe that if we ever met in real life we'd hit it really well. I for one sure wish you could spend some time in Austin seeing the work I've done combining WiX with InstallShield. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Rob Menschingr...@robmensching.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 10:10:42 PM Subject: Re: [WiX-users] Does the msi-filename matter? I think you have me confused with someone else. I've always had the stance: If you can use a Major Upgrade do so. Life is too short to deal with the difficulties otherwise. What else have you told people I believe?smile/ On Wed, Jul 21, 2010 at 7:53 PM, Christopher Painter chr...@deploymentengineering.com wrote: Rob- I seem to recall several blog articles years ago talking about how major upgrades are ugly. One was from an active blogger at the time ( Vagmi ) but I don't remember the others. http://geekswithblogs.net/Vagmi.Mudumbai/archive/2006/06/11/81426.aspx Blair- My MSI mojo is good, but what development throws over the wall to me frequently will not end well with anything other then a major upgrade with respect to msi servicing patterns and rules. I'm sure you've seen that also. Chris - Original Message From: Rob Menschingr...@robmensching.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 9:33:40 PM Subject: Re: [WiX-users] Does the msi-filename matter? Uhh, I personally always recommend Major Upgrades over all the other options. IMHO, the other options (minor updates and small updates) add pain that is rarely worth it (i.e. you have to be really big with lots of customers to bother with .msp's). I'd be curious to see who actually recommends anything but Major Upgrades for the general case. On Wed, Jul 21, 2010 at 4:07 PM, Christopher Painter chr...@deploymentengineering.com wrote: Same here. I've heard people post for years about how Major Upgrades are a pain and you better follow the component rules to a letter if you want minor upgrades, small updates and patching to work. I've choosen to only support Major
Re: [WiX-users] Does the msi-filename matter?
Thank you everybody for the discussion! The result is clear to me: I won't use minor- and small updates. One question concerning Best practice left for the deployment. In fact my application consists of: - Viewer (EXE, DLL, CHM) - Database (dat-file (80MB), bunch of PDFs) - License1.RTF, License2.RTF Now I ship my program in various flavours: 1.) Corporate edition with License1.RTF 2.) Private edition: Everything the same except License2.RTF 3.) (private) Network edition: Same as (2) except the name 4.) Demo version: Modified Database (30MB instead of 80MB) And finally each (1)-(3) get updates every few months. At first I thought with WiX it would be possible to just create one installer for all of those. But according to the discussions so far, am I right to just generate separate projects (wxs files) for each of the cases above? And according to the updates: Each of the (1), (2), (3), (4) shares the same UpgradeCode, doesn't it? Regards, Luke Am 22.07.2010 05:28, schrieb Christopher Painter: I wrote thatI had read several blog posts over the years and cited one of them as Vagmi and couldn't recall who the others were. I didn't say any of them were from you. In fact, I recall you writing a post about why WiX uses Major Upgrades and I referred to that as vindication; evidence that we have shared beliefs. BTW, I could ask you the same question considering your still unapologetic personal attack on me several years ago. I still believe that if we ever met in real life we'd hit it really well. I for one sure wish you could spend some time in Austin seeing the work I've done combining WiX with InstallShield. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Rob Menschingr...@robmensching.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 10:10:42 PM Subject: Re: [WiX-users] Does the msi-filename matter? I think you have me confused with someone else. I've always had the stance: If you can use a Major Upgrade do so. Life is too short to deal with the difficulties otherwise. What else have you told people I believe?smile/ On Wed, Jul 21, 2010 at 7:53 PM, Christopher Painter chr...@deploymentengineering.com wrote: Rob- I seem to recall several blog articles years ago talking about how major upgrades are ugly. One was from an active blogger at the time ( Vagmi ) but I don't remember the others. http://geekswithblogs.net/Vagmi.Mudumbai/archive/2006/06/11/81426.aspx Blair- My MSI mojo is good, but what development throws over the wall to me frequently will not end well with anything other then a major upgrade with respect to msi servicing patterns and rules. I'm sure you've seen that also. Chris - Original Message From: Rob Menschingr...@robmensching.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 9:33:40 PM Subject: Re: [WiX-users] Does the msi-filename matter? Uhh, I personally always recommend Major Upgrades over all the other options. IMHO, the other options (minor updates and small updates) add pain that is rarely worth it (i.e. you have to be really big with lots of customers to bother with .msp's). I'd be curious to see who actually recommends anything but Major Upgrades for the general case. On Wed, Jul 21, 2010 at 4:07 PM, Christopher Painter chr...@deploymentengineering.com wrote: Same here. I've heard people post for years about how Major Upgrades are a pain and you better follow the component rules to a letter if you want minor upgrades, small updates and patching to work. I've choosen to only support Major Upgrades and it's a bit of a vindication to now see the likes of Rob talk about why WiX's own installer only does Major Upgrades. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Neil Sleightholmn...@x2systems.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 5:58:54 PM Subject: Re: [WiX-users] Does the msi-filename matter? But a key point is that this is only a possible** problem for minor upgrades. If you do major upgrades you can ignore it. **I say possible because I have never seen an issue but I mainly stick to major upgrade because they are less hassle. Neil -Original Message- From: Blair [mailto:os...@live.com] Sent: 21 July 2010 23:12 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Does the msi-filename matter? That could help reduce the chance of that problem, but depending on which file the user changes (the initial
Re: [WiX-users] Does the msi-filename matter?
If this is a blocking issue that is preventing everyone from using an MSI feature, then this sounds like a BUG in the MSI design that should be reported to Microsoft with high priority and fixed in the next version of Windows Installer. -Original Message- From: Lukas Haase [mailto:lukasha...@gmx.at] Sent: Thursday, July 22, 2010 1:37 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Does the msi-filename matter? Thank you everybody for the discussion! The result is clear to me: I won't use minor- and small updates. One question concerning Best practice left for the deployment. In fact my application consists of: - Viewer (EXE, DLL, CHM) - Database (dat-file (80MB), bunch of PDFs) - License1.RTF, License2.RTF Now I ship my program in various flavours: 1.) Corporate edition with License1.RTF 2.) Private edition: Everything the same except License2.RTF 3.) (private) Network edition: Same as (2) except the name 4.) Demo version: Modified Database (30MB instead of 80MB) And finally each (1)-(3) get updates every few months. At first I thought with WiX it would be possible to just create one installer for all of those. But according to the discussions so far, am I right to just generate separate projects (wxs files) for each of the cases above? And according to the updates: Each of the (1), (2), (3), (4) shares the same UpgradeCode, doesn't it? Regards, Luke Am 22.07.2010 05:28, schrieb Christopher Painter: I wrote thatI had read several blog posts over the years and cited one of them as Vagmi and couldn't recall who the others were. I didn't say any of them were from you. In fact, I recall you writing a post about why WiX uses Major Upgrades and I referred to that as vindication; evidence that we have shared beliefs. BTW, I could ask you the same question considering your still unapologetic personal attack on me several years ago. I still believe that if we ever met in real life we'd hit it really well. I for one sure wish you could spend some time in Austin seeing the work I've done combining WiX with InstallShield. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Rob Menschingr...@robmensching.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 10:10:42 PM Subject: Re: [WiX-users] Does the msi-filename matter? I think you have me confused with someone else. I've always had the stance: If you can use a Major Upgrade do so. Life is too short to deal with the difficulties otherwise. What else have you told people I believe?smile/ On Wed, Jul 21, 2010 at 7:53 PM, Christopher Painter chr...@deploymentengineering.com wrote: Rob- I seem to recall several blog articles years ago talking about how major upgrades are ugly. One was from an active blogger at the time ( Vagmi ) but I don't remember the others. http://geekswithblogs.net/Vagmi.Mudumbai/archive/2006/06/11/81426.asp x Blair- My MSI mojo is good, but what development throws over the wall to me frequently will not end well with anything other then a major upgrade with respect to msi servicing patterns and rules. I'm sure you've seen that also. Chris - Original Message From: Rob Menschingr...@robmensching.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 9:33:40 PM Subject: Re: [WiX-users] Does the msi-filename matter? Uhh, I personally always recommend Major Upgrades over all the other options. IMHO, the other options (minor updates and small updates) add pain that is rarely worth it (i.e. you have to be really big with lots of customers to bother with .msp's). I'd be curious to see who actually recommends anything but Major Upgrades for the general case. On Wed, Jul 21, 2010 at 4:07 PM, Christopher Painter chr...@deploymentengineering.com wrote: Same here. I've heard people post for years about how Major Upgrades are a pain and you better follow the component rules to a letter if you want minor upgrades, small updates and patching to work. I've choosen to only support Major Upgrades and it's a bit of a vindication to now see the likes of Rob talk about why WiX's own installer only does Major Upgrades. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Neil Sleightholmn...@x2systems.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 5:58:54 PM Subject: Re: [WiX-users] Does the msi-filename matter? But a key point is that this is only a possible** problem for minor upgrades. If you do major upgrades
Re: [WiX-users] Does the msi-filename matter?
It is true that changing the MSI file name forces a major upgrade. If you are concerned that your user will interfere with your servicing strategy by renaming the MSI, you can use the OriginalDatabase property in a LaunchCondition to abort the install if they have renamed the MSI. I would suggest something like [OriginalDatabase] \MYSUPPORTEDFILENAME.msi http://msdn.microsoft.com/en-us/library/aa370562(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Lukas Haase lukasha...@gmx.at To: wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 4:42:20 PM Subject: [WiX-users] Does the msi-filename matter? Hi, Does the filename of the msi file matter in any way? I really DO NOT hope so! Because I have no influence if the user renames the file before installing?! [1] says: There are cases when the Windows Installer forces you to use a major upgrade [...] You have to when you change the name of the .msi file for any reason. [...] Regards, Luke [1] http://www.tramontana.co.hu/wix/lesson4.php#4.1 -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does the msi-filename matter?
That could help reduce the chance of that problem, but depending on which file the user changes (the initial or the update) you may not get a chance to warn the user to not rename the MSI. In most of the failure cases I have seen due to not finding the MSI file at the indicated directory caused by looking for a different name than expected (usually due to attempting a minor upgrade using an MSI downloaded using IE) Windows Installer never even starts parsing any sequence table. This is part of the reason huge numbers of software producers distributing over the internet use self-extract-and-launch-style wrappers (zip-exe style) for their MSI distribution. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, July 21, 2010 2:51 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Does the msi-filename matter? It is true that changing the MSI file name forces a major upgrade. If you are concerned that your user will interfere with your servicing strategy by renaming the MSI, you can use the OriginalDatabase property in a LaunchCondition to abort the install if they have renamed the MSI. I would suggest something like [OriginalDatabase] \MYSUPPORTEDFILENAME.msi http://msdn.microsoft.com/en-us/library/aa370562(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Lukas Haase lukasha...@gmx.at To: wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 4:42:20 PM Subject: [WiX-users] Does the msi-filename matter? Hi, Does the filename of the msi file matter in any way? I really DO NOT hope so! Because I have no influence if the user renames the file before installing?! [1] says: There are cases when the Windows Installer forces you to use a major upgrade [...] You have to when you change the name of the .msi file for any reason. [...] Regards, Luke [1] http://www.tramontana.co.hu/wix/lesson4.php#4.1 -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does the msi-filename matter?
Dear Blair, Dear Christopher, Thank you for your reply. Am 22.07.2010 00:11, schrieb Blair: [...] This is part of the reason huge numbers of software producers distributing over the internet use self-extract-and-launch-style wrappers (zip-exe style) for their MSI distribution. Do you have a recommendation for such a tool? [...] It is true that changing the MSI file name forces a major upgrade. Isn't this really dumb? I am kind of disappointed of MSI... Everything gets a GUID in order to be REALLY sure that everything just depends on an ID and not on a name etc. And then...that?! [...] I would suggest something like [OriginalDatabase] \MYSUPPORTEDFILENAME.msi http://msdn.microsoft.com/en-us/library/aa370562(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx Is this what you mean? Condition Message=You must not rename the msi file! OriginalDatabase ~ \MYSUPPORTEDFILENAME.msi /Condition Regards, Luke Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Lukas Haaselukasha...@gmx.at To: wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 4:42:20 PM Subject: [WiX-users] Does the msi-filename matter? Hi, Does the filename of the msi file matter in any way? I really DO NOT hope so! Because I have no influence if the user renames the file before installing?! [1] says: There are cases when the Windows Installer forces you to use a major upgrade [...] You have to when you change the name of the .msi file for any reason. [...] Regards, Luke [1] http://www.tramontana.co.hu/wix/lesson4.php#4.1 -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does the msi-filename matter?
But a key point is that this is only a possible** problem for minor upgrades. If you do major upgrades you can ignore it. **I say possible because I have never seen an issue but I mainly stick to major upgrade because they are less hassle. Neil -Original Message- From: Blair [mailto:os...@live.com] Sent: 21 July 2010 23:12 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Does the msi-filename matter? That could help reduce the chance of that problem, but depending on which file the user changes (the initial or the update) you may not get a chance to warn the user to not rename the MSI. In most of the failure cases I have seen due to not finding the MSI file at the indicated directory caused by looking for a different name than expected (usually due to attempting a minor upgrade using an MSI downloaded using IE) Windows Installer never even starts parsing any sequence table. This is part of the reason huge numbers of software producers distributing over the internet use self-extract-and-launch-style wrappers (zip-exe style) for their MSI distribution. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, July 21, 2010 2:51 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Does the msi-filename matter? It is true that changing the MSI file name forces a major upgrade. If you are concerned that your user will interfere with your servicing strategy by renaming the MSI, you can use the OriginalDatabase property in a LaunchCondition to abort the install if they have renamed the MSI. I would suggest something like [OriginalDatabase] \MYSUPPORTEDFILENAME.msi http://msdn.microsoft.com/en-us/library/aa370562(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Lukas Haase lukasha...@gmx.at To: wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 4:42:20 PM Subject: [WiX-users] Does the msi-filename matter? Hi, Does the filename of the msi file matter in any way? I really DO NOT hope so! Because I have no influence if the user renames the file before installing?! [1] says: There are cases when the Windows Installer forces you to use a major upgrade [...] You have to when you change the name of the .msi file for any reason. [...] Regards, Luke [1] http://www.tramontana.co.hu/wix/lesson4.php#4.1 -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does the msi-filename matter?
InstallShield grin/ Seriously, I'm warming up to WiX but I still only use it for my merge module development ( hundreds of them ). I still consume them with InstallShield Product Configurations to support dozens of products with upwards to 15,000 files each and dozens of third party packages to be bootstrapped before my MSI. One day ( year ) WiX will have Burn and I'll reevaluate that strategy. Regards, Chris Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Lukas Haase lukasha...@gmx.at To: wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 5:26:46 PM Subject: Re: [WiX-users] Does the msi-filename matter? Dear Blair, Dear Christopher, Thank you for your reply. Am 22.07.2010 00:11, schrieb Blair: [...] This is part of the reason huge numbers of software producers distributing over the internet use self-extract-and-launch-style wrappers (zip-exe style) for their MSI distribution. Do you have a recommendation for such a tool? [...] It is true that changing the MSI file name forces a major upgrade. Isn't this really dumb? I am kind of disappointed of MSI... Everything gets a GUID in order to be REALLY sure that everything just depends on an ID and not on a name etc. And then...that?! [...] I would suggest something like [OriginalDatabase] \MYSUPPORTEDFILENAME.msi http://msdn.microsoft.com/en-us/library/aa370562(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx Is this what you mean? Condition Message=You must not rename the msi file! OriginalDatabase ~ \MYSUPPORTEDFILENAME.msi /Condition Regards, Luke Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Lukas Haaselukasha...@gmx.at To: wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 4:42:20 PM Subject: [WiX-users] Does the msi-filename matter? Hi, Does the filename of the msi file matter in any way? I really DO NOT hope so! Because I have no influence if the user renames the file before installing?! [1] says: There are cases when the Windows Installer forces you to use a major upgrade [...] You have to when you change the name of the .msi file for any reason. [...] Regards, Luke [1] http://www.tramontana.co.hu/wix/lesson4.php#4.1 -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does the msi-filename matter?
Same here. I've heard people post for years about how Major Upgrades are a pain and you better follow the component rules to a letter if you want minor upgrades, small updates and patching to work. I've choosen to only support Major Upgrades and it's a bit of a vindication to now see the likes of Rob talk about why WiX's own installer only does Major Upgrades. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Neil Sleightholm n...@x2systems.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 5:58:54 PM Subject: Re: [WiX-users] Does the msi-filename matter? But a key point is that this is only a possible** problem for minor upgrades. If you do major upgrades you can ignore it. **I say possible because I have never seen an issue but I mainly stick to major upgrade because they are less hassle. Neil -Original Message- From: Blair [mailto:os...@live.com] Sent: 21 July 2010 23:12 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Does the msi-filename matter? That could help reduce the chance of that problem, but depending on which file the user changes (the initial or the update) you may not get a chance to warn the user to not rename the MSI. In most of the failure cases I have seen due to not finding the MSI file at the indicated directory caused by looking for a different name than expected (usually due to attempting a minor upgrade using an MSI downloaded using IE) Windows Installer never even starts parsing any sequence table. This is part of the reason huge numbers of software producers distributing over the internet use self-extract-and-launch-style wrappers (zip-exe style) for their MSI distribution. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, July 21, 2010 2:51 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Does the msi-filename matter? It is true that changing the MSI file name forces a major upgrade. If you are concerned that your user will interfere with your servicing strategy by renaming the MSI, you can use the OriginalDatabase property in a LaunchCondition to abort the install if they have renamed the MSI. I would suggest something like [OriginalDatabase] \MYSUPPORTEDFILENAME.msi http://msdn.microsoft.com/en-us/library/aa370562(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Lukas Haase lukasha...@gmx.at To: wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 4:42:20 PM Subject: [WiX-users] Does the msi-filename matter? Hi, Does the filename of the msi file matter in any way? I really DO NOT hope so! Because I have no influence if the user renames the file before installing?! [1] says: There are cases when the Windows Installer forces you to use a major upgrade [...] You have to when you change the name of the .msi file for any reason. [...] Regards, Luke [1] http://www.tramontana.co.hu/wix/lesson4.php#4.1 -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does the msi-filename matter?
I have often said (even on this list) that for most products, Major Upgrades are the way to go. Until your distribution strategy requires supporting MSP files, and you feel more technically confident in your abilities in Windows Installer deployment technologies, just set things up for Major Upgrades and get on with your life. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, July 21, 2010 4:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Does the msi-filename matter? Same here. I've heard people post for years about how Major Upgrades are a pain and you better follow the component rules to a letter if you want minor upgrades, small updates and patching to work. I've choosen to only support Major Upgrades and it's a bit of a vindication to now see the likes of Rob talk about why WiX's own installer only does Major Upgrades. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Neil Sleightholm n...@x2systems.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 5:58:54 PM Subject: Re: [WiX-users] Does the msi-filename matter? But a key point is that this is only a possible** problem for minor upgrades. If you do major upgrades you can ignore it. **I say possible because I have never seen an issue but I mainly stick to major upgrade because they are less hassle. Neil -Original Message- From: Blair [mailto:os...@live.com] Sent: 21 July 2010 23:12 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Does the msi-filename matter? That could help reduce the chance of that problem, but depending on which file the user changes (the initial or the update) you may not get a chance to warn the user to not rename the MSI. In most of the failure cases I have seen due to not finding the MSI file at the indicated directory caused by looking for a different name than expected (usually due to attempting a minor upgrade using an MSI downloaded using IE) Windows Installer never even starts parsing any sequence table. This is part of the reason huge numbers of software producers distributing over the internet use self-extract-and-launch-style wrappers (zip-exe style) for their MSI distribution. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, July 21, 2010 2:51 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Does the msi-filename matter? It is true that changing the MSI file name forces a major upgrade. If you are concerned that your user will interfere with your servicing strategy by renaming the MSI, you can use the OriginalDatabase property in a LaunchCondition to abort the install if they have renamed the MSI. I would suggest something like [OriginalDatabase] \MYSUPPORTEDFILENAME.msi http://msdn.microsoft.com/en-us/library/aa370562(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Lukas Haase lukasha...@gmx.at To: wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 4:42:20 PM Subject: [WiX-users] Does the msi-filename matter? Hi, Does the filename of the msi file matter in any way? I really DO NOT hope so! Because I have no influence if the user renames the file before installing?! [1] says: There are cases when the Windows Installer forces you to use a major upgrade [...] You have to when you change the name of the .msi file for any reason. [...] Regards, Luke [1] http://www.tramontana.co.hu/wix/lesson4.php#4.1 -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu
Re: [WiX-users] Does the msi-filename matter?
#1 How long before you ship? Search for self-extract and many of what comes up can be set to run a command-line at the end of the extract. I recently used some sort of WinZip-like program. I've also successfully used IExpress in the past. #2 As far as I have been able to gather the reason is that Windows Installer stores two bits of data separately: the SourceList which are a list of directories used to search for cached copies of the original MSI file, and the name of the MSI, in case some of those cache directories contain other MSI files as well. So, they combine each path with the expected filename and if they don't find the package with the needed PackageGuid, they continue on to the next path in the list, prompting and/or failing when they are done. #3 I can't speak for Christopher but I would assume he was indicating something like this: Condition Message=You must not rename the msi file! [OriginalDatabase] \MYSUPPORTEDFILENAME.msi /Condition The comparison operator is (that isn't an email artifact). However, I'm concerned that may cause repairs and/or removals to fail. -Original Message- From: Lukas Haase [mailto:lukasha...@gmx.at] Sent: Wednesday, July 21, 2010 3:27 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Does the msi-filename matter? Dear Blair, Dear Christopher, Thank you for your reply. Am 22.07.2010 00:11, schrieb Blair: [...] This is part of the reason huge numbers of software producers distributing over the internet use self-extract-and-launch-style wrappers (zip-exe style) for their MSI distribution. Do you have a recommendation for such a tool? [...] It is true that changing the MSI file name forces a major upgrade. Isn't this really dumb? I am kind of disappointed of MSI... Everything gets a GUID in order to be REALLY sure that everything just depends on an ID and not on a name etc. And then...that?! [...] I would suggest something like [OriginalDatabase] \MYSUPPORTEDFILENAME.msi http://msdn.microsoft.com/en-us/library/aa370562(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx Is this what you mean? Condition Message=You must not rename the msi file! OriginalDatabase ~ \MYSUPPORTEDFILENAME.msi /Condition Regards, Luke Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Lukas Haaselukasha...@gmx.at To: wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 4:42:20 PM Subject: [WiX-users] Does the msi-filename matter? Hi, Does the filename of the msi file matter in any way? I really DO NOT hope so! Because I have no influence if the user renames the file before installing?! [1] says: There are cases when the Windows Installer forces you to use a major upgrade [...] You have to when you change the name of the .msi file for any reason. [...] Regards, Luke [1] http://www.tramontana.co.hu/wix/lesson4.php#4.1 -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does the msi-filename matter?
Uhh, I personally always recommend Major Upgrades over all the other options. IMHO, the other options (minor updates and small updates) add pain that is rarely worth it (i.e. you have to be really big with lots of customers to bother with .msp's). I'd be curious to see who actually recommends anything but Major Upgrades for the general case. On Wed, Jul 21, 2010 at 4:07 PM, Christopher Painter chr...@deploymentengineering.com wrote: Same here. I've heard people post for years about how Major Upgrades are a pain and you better follow the component rules to a letter if you want minor upgrades, small updates and patching to work. I've choosen to only support Major Upgrades and it's a bit of a vindication to now see the likes of Rob talk about why WiX's own installer only does Major Upgrades. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Neil Sleightholm n...@x2systems.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 5:58:54 PM Subject: Re: [WiX-users] Does the msi-filename matter? But a key point is that this is only a possible** problem for minor upgrades. If you do major upgrades you can ignore it. **I say possible because I have never seen an issue but I mainly stick to major upgrade because they are less hassle. Neil -Original Message- From: Blair [mailto:os...@live.com] Sent: 21 July 2010 23:12 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Does the msi-filename matter? That could help reduce the chance of that problem, but depending on which file the user changes (the initial or the update) you may not get a chance to warn the user to not rename the MSI. In most of the failure cases I have seen due to not finding the MSI file at the indicated directory caused by looking for a different name than expected (usually due to attempting a minor upgrade using an MSI downloaded using IE) Windows Installer never even starts parsing any sequence table. This is part of the reason huge numbers of software producers distributing over the internet use self-extract-and-launch-style wrappers (zip-exe style) for their MSI distribution. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, July 21, 2010 2:51 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Does the msi-filename matter? It is true that changing the MSI file name forces a major upgrade. If you are concerned that your user will interfere with your servicing strategy by renaming the MSI, you can use the OriginalDatabase property in a LaunchCondition to abort the install if they have renamed the MSI. I would suggest something like [OriginalDatabase] \MYSUPPORTEDFILENAME.msi http://msdn.microsoft.com/en-us/library/aa370562(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Lukas Haase lukasha...@gmx.at To: wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 4:42:20 PM Subject: [WiX-users] Does the msi-filename matter? Hi, Does the filename of the msi file matter in any way? I really DO NOT hope so! Because I have no influence if the user renames the file before installing?! [1] says: There are cases when the Windows Installer forces you to use a major upgrade [...] You have to when you change the name of the .msi file for any reason. [...] Regards, Luke [1] http://www.tramontana.co.hu/wix/lesson4.php#4.1 -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
Re: [WiX-users] Does the msi-filename matter?
Rob- I seem to recall several blog articles years ago talking about how major upgrades are ugly. One was from an active blogger at the time ( Vagmi ) but I don't remember the others. http://geekswithblogs.net/Vagmi.Mudumbai/archive/2006/06/11/81426.aspx Blair- My MSI mojo is good, but what development throws over the wall to me frequently will not end well with anything other then a major upgrade with respect to msi servicing patterns and rules. I'm sure you've seen that also. Chris - Original Message From: Rob Mensching r...@robmensching.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 9:33:40 PM Subject: Re: [WiX-users] Does the msi-filename matter? Uhh, I personally always recommend Major Upgrades over all the other options. IMHO, the other options (minor updates and small updates) add pain that is rarely worth it (i.e. you have to be really big with lots of customers to bother with .msp's). I'd be curious to see who actually recommends anything but Major Upgrades for the general case. On Wed, Jul 21, 2010 at 4:07 PM, Christopher Painter chr...@deploymentengineering.com wrote: Same here. I've heard people post for years about how Major Upgrades are a pain and you better follow the component rules to a letter if you want minor upgrades, small updates and patching to work. I've choosen to only support Major Upgrades and it's a bit of a vindication to now see the likes of Rob talk about why WiX's own installer only does Major Upgrades. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Neil Sleightholm n...@x2systems.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 5:58:54 PM Subject: Re: [WiX-users] Does the msi-filename matter? But a key point is that this is only a possible** problem for minor upgrades. If you do major upgrades you can ignore it. **I say possible because I have never seen an issue but I mainly stick to major upgrade because they are less hassle. Neil -Original Message- From: Blair [mailto:os...@live.com] Sent: 21 July 2010 23:12 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Does the msi-filename matter? That could help reduce the chance of that problem, but depending on which file the user changes (the initial or the update) you may not get a chance to warn the user to not rename the MSI. In most of the failure cases I have seen due to not finding the MSI file at the indicated directory caused by looking for a different name than expected (usually due to attempting a minor upgrade using an MSI downloaded using IE) Windows Installer never even starts parsing any sequence table. This is part of the reason huge numbers of software producers distributing over the internet use self-extract-and-launch-style wrappers (zip-exe style) for their MSI distribution. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, July 21, 2010 2:51 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Does the msi-filename matter? It is true that changing the MSI file name forces a major upgrade. If you are concerned that your user will interfere with your servicing strategy by renaming the MSI, you can use the OriginalDatabase property in a LaunchCondition to abort the install if they have renamed the MSI. I would suggest something like [OriginalDatabase] \MYSUPPORTEDFILENAME.msi http://msdn.microsoft.com/en-us/library/aa370562(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Lukas Haase lukasha...@gmx.at To: wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 4:42:20 PM Subject: [WiX-users] Does the msi-filename matter? Hi, Does the filename of the msi file matter in any way? I really DO NOT hope so! Because I have no influence if the user renames the file before installing?! [1] says: There are cases when the Windows Installer forces you to use a major upgrade [...] You have to when you change the name of the .msi file for any reason. [...] Regards, Luke [1] http://www.tramontana.co.hu/wix/lesson4.php#4.1 -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net
Re: [WiX-users] Does the msi-filename matter?
I think you have me confused with someone else. I've always had the stance: If you can use a Major Upgrade do so. Life is too short to deal with the difficulties otherwise. What else have you told people I believe? smile/ On Wed, Jul 21, 2010 at 7:53 PM, Christopher Painter chr...@deploymentengineering.com wrote: Rob- I seem to recall several blog articles years ago talking about how major upgrades are ugly. One was from an active blogger at the time ( Vagmi ) but I don't remember the others. http://geekswithblogs.net/Vagmi.Mudumbai/archive/2006/06/11/81426.aspx Blair- My MSI mojo is good, but what development throws over the wall to me frequently will not end well with anything other then a major upgrade with respect to msi servicing patterns and rules. I'm sure you've seen that also. Chris - Original Message From: Rob Mensching r...@robmensching.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 9:33:40 PM Subject: Re: [WiX-users] Does the msi-filename matter? Uhh, I personally always recommend Major Upgrades over all the other options. IMHO, the other options (minor updates and small updates) add pain that is rarely worth it (i.e. you have to be really big with lots of customers to bother with .msp's). I'd be curious to see who actually recommends anything but Major Upgrades for the general case. On Wed, Jul 21, 2010 at 4:07 PM, Christopher Painter chr...@deploymentengineering.com wrote: Same here. I've heard people post for years about how Major Upgrades are a pain and you better follow the component rules to a letter if you want minor upgrades, small updates and patching to work. I've choosen to only support Major Upgrades and it's a bit of a vindication to now see the likes of Rob talk about why WiX's own installer only does Major Upgrades. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Neil Sleightholm n...@x2systems.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 5:58:54 PM Subject: Re: [WiX-users] Does the msi-filename matter? But a key point is that this is only a possible** problem for minor upgrades. If you do major upgrades you can ignore it. **I say possible because I have never seen an issue but I mainly stick to major upgrade because they are less hassle. Neil -Original Message- From: Blair [mailto:os...@live.com] Sent: 21 July 2010 23:12 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Does the msi-filename matter? That could help reduce the chance of that problem, but depending on which file the user changes (the initial or the update) you may not get a chance to warn the user to not rename the MSI. In most of the failure cases I have seen due to not finding the MSI file at the indicated directory caused by looking for a different name than expected (usually due to attempting a minor upgrade using an MSI downloaded using IE) Windows Installer never even starts parsing any sequence table. This is part of the reason huge numbers of software producers distributing over the internet use self-extract-and-launch-style wrappers (zip-exe style) for their MSI distribution. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, July 21, 2010 2:51 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Does the msi-filename matter? It is true that changing the MSI file name forces a major upgrade. If you are concerned that your user will interfere with your servicing strategy by renaming the MSI, you can use the OriginalDatabase property in a LaunchCondition to abort the install if they have renamed the MSI. I would suggest something like [OriginalDatabase] \MYSUPPORTEDFILENAME.msi http://msdn.microsoft.com/en-us/library/aa370562(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Lukas Haase lukasha...@gmx.at To: wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 4:42:20 PM Subject: [WiX-users] Does the msi-filename matter? Hi, Does the filename of the msi file matter in any way? I really DO NOT hope so! Because I have no influence if the user renames the file before installing?! [1] says: There are cases when the Windows Installer forces you to use a major upgrade [...] You have to when you change the name of the .msi file
Re: [WiX-users] Does the msi-filename matter?
I wrote thatI had read several blog posts over the years and cited one of them as Vagmi and couldn't recall who the others were. I didn't say any of them were from you. In fact, I recall you writing a post about why WiX uses Major Upgrades and I referred to that as vindication; evidence that we have shared beliefs. BTW, I could ask you the same question considering your still unapologetic personal attack on me several years ago. I still believe that if we ever met in real life we'd hit it really well. I for one sure wish you could spend some time in Austin seeing the work I've done combining WiX with InstallShield. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Rob Mensching r...@robmensching.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 10:10:42 PM Subject: Re: [WiX-users] Does the msi-filename matter? I think you have me confused with someone else. I've always had the stance: If you can use a Major Upgrade do so. Life is too short to deal with the difficulties otherwise. What else have you told people I believe? smile/ On Wed, Jul 21, 2010 at 7:53 PM, Christopher Painter chr...@deploymentengineering.com wrote: Rob- I seem to recall several blog articles years ago talking about how major upgrades are ugly. One was from an active blogger at the time ( Vagmi ) but I don't remember the others. http://geekswithblogs.net/Vagmi.Mudumbai/archive/2006/06/11/81426.aspx Blair- My MSI mojo is good, but what development throws over the wall to me frequently will not end well with anything other then a major upgrade with respect to msi servicing patterns and rules. I'm sure you've seen that also. Chris - Original Message From: Rob Mensching r...@robmensching.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 9:33:40 PM Subject: Re: [WiX-users] Does the msi-filename matter? Uhh, I personally always recommend Major Upgrades over all the other options. IMHO, the other options (minor updates and small updates) add pain that is rarely worth it (i.e. you have to be really big with lots of customers to bother with .msp's). I'd be curious to see who actually recommends anything but Major Upgrades for the general case. On Wed, Jul 21, 2010 at 4:07 PM, Christopher Painter chr...@deploymentengineering.com wrote: Same here. I've heard people post for years about how Major Upgrades are a pain and you better follow the component rules to a letter if you want minor upgrades, small updates and patching to work. I've choosen to only support Major Upgrades and it's a bit of a vindication to now see the likes of Rob talk about why WiX's own installer only does Major Upgrades. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Neil Sleightholm n...@x2systems.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, July 21, 2010 5:58:54 PM Subject: Re: [WiX-users] Does the msi-filename matter? But a key point is that this is only a possible** problem for minor upgrades. If you do major upgrades you can ignore it. **I say possible because I have never seen an issue but I mainly stick to major upgrade because they are less hassle. Neil -Original Message- From: Blair [mailto:os...@live.com] Sent: 21 July 2010 23:12 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Does the msi-filename matter? That could help reduce the chance of that problem, but depending on which file the user changes (the initial or the update) you may not get a chance to warn the user to not rename the MSI. In most of the failure cases I have seen due to not finding the MSI file at the indicated directory caused by looking for a different name than expected (usually due to attempting a minor upgrade using an MSI downloaded using IE) Windows Installer never even starts parsing any sequence table. This is part of the reason huge numbers of software producers distributing over the internet use self-extract-and-launch-style wrappers (zip-exe style) for their MSI distribution. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, July 21, 2010 2:51 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Does the msi-filename matter? It is true that changing the MSI file name forces a major upgrade. If you are concerned that your user will interfere with your servicing strategy
