Re: [WiX-users] creating a WIX small or minor patch
No. The recommendation is to use heat to generate your first version and then make the changes manually thereafter. Our product and work practices make this a suitable way to work. We use * for component guids to keep them constant. We have one product that heats files with each build but we service it with major upgrades. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 25 January 2012 09:10 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Found Paraffin! http://www.wintellect.com/CS/blogs/jrobbins/archive/2010/08/31/zen-of-paraffi n.aspx I think that this is what I need! So that my HEAT won't generate different GUIDs each time. Are you familiar with it? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 4:18 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch I don't think your problems are related to patch building. I think your second MSI is not a valid minor update. Try running the second MSI as an upgrade of the first one using the command line mentioned in Rob's blog http://robmensching.com/blog/posts/2007/1/4/Doing-a-small-update-or-minor-upg rade-in-MSI-Use I think you'll get some similar errors in the log. If this is the case, you go through the MSDN sections mentioned on making minor upgrades and check both of your MSIs to ensure you're following all the rules - they are quick tricky. Comparing the two MSIs by looking at them in Orca rather than by looking at the code so you can see what's actually been generated. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 14:00 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch I see, the other reason we don't compress into cab is time, since we compress everything into RARs for client delivery... so a cab will be redundant. But point taken, I won't let anyone change a thing :). To the main problem... I still can't seem to be able to run the Pyro command no matter what... After taking your advice I removed the from within the tag And then I did get errors referring to my files, that is progress... but the errors are as mentioned before: C:\Sample_1>pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. The first section is: Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information I understand, I won't change the product ID between builds. The second part: E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. That I don't understand, I didn't remove anything, maybe they are getting different ids!? Both MSIs I used to generate the diff.wixmst are the same except for some code change in one of the assemblies... Thanks again! -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 3:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That would invalidate the MSI if you don't keep the relevant tables up to date too. Its not a recommended practice - do a proper build instead. I've not built a patch targeting an unpacked MSI but I believe the media number would still need to be higher than the highest file id in the MSI file table. The patch itself will contain cabinets for the altered files using the media cabinet name. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 13:01 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or mino
Re: [WiX-users] creating a WIX small or minor patch
Found Paraffin! http://www.wintellect.com/CS/blogs/jrobbins/archive/2010/08/31/zen-of-paraffin.aspx I think that this is what I need! So that my HEAT won't generate different GUIDs each time. Are you familiar with it? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 4:18 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch I don't think your problems are related to patch building. I think your second MSI is not a valid minor update. Try running the second MSI as an upgrade of the first one using the command line mentioned in Rob's blog http://robmensching.com/blog/posts/2007/1/4/Doing-a-small-update-or-minor-upg rade-in-MSI-Use I think you'll get some similar errors in the log. If this is the case, you go through the MSDN sections mentioned on making minor upgrades and check both of your MSIs to ensure you're following all the rules - they are quick tricky. Comparing the two MSIs by looking at them in Orca rather than by looking at the code so you can see what's actually been generated. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 14:00 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch I see, the other reason we don't compress into cab is time, since we compress everything into RARs for client delivery... so a cab will be redundant. But point taken, I won't let anyone change a thing :). To the main problem... I still can't seem to be able to run the Pyro command no matter what... After taking your advice I removed the from within the tag And then I did get errors referring to my files, that is progress... but the errors are as mentioned before: C:\Sample_1>pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. The first section is: Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information I understand, I won't change the product ID between builds. The second part: E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. That I don't understand, I didn't remove anything, maybe they are getting different ids!? Both MSIs I used to generate the diff.wixmst are the same except for some code change in one of the assemblies... Thanks again! -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 3:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That would invalidate the MSI if you don't keep the relevant tables up to date too. Its not a recommended practice - do a proper build instead. I've not built a patch targeting an unpacked MSI but I believe the media number would still need to be higher than the highest file id in the MSI file table. The patch itself will contain cabinets for the altered files using the media cabinet name. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 13:01 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch One more thing I remembered, in our MSIs we don't use CAB, we just create a folder next to the MSI, it's easier for us to replace/fix text/config files after a build was already create... Does this influence the patch.wxs? I see that there is a Media tag that points to a cab file... -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 11:35 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creati
Re: [WiX-users] creating a WIX small or minor patch
Hi again. Take a look at this WixHarvest.targets file. As far as I see I do pass the true... I thought that this should keep the GUIDs consistent between builds... I'm wrong. http://schemas.microsoft.com/developer/msbuild/2003";> true $(ProjectDir)\files.wxs ProductFolder true -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 4:18 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch I don't think your problems are related to patch building. I think your second MSI is not a valid minor update. Try running the second MSI as an upgrade of the first one using the command line mentioned in Rob's blog http://robmensching.com/blog/posts/2007/1/4/Doing-a-small-update-or-minor-upg rade-in-MSI-Use I think you'll get some similar errors in the log. If this is the case, you go through the MSDN sections mentioned on making minor upgrades and check both of your MSIs to ensure you're following all the rules - they are quick tricky. Comparing the two MSIs by looking at them in Orca rather than by looking at the code so you can see what's actually been generated. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 14:00 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch I see, the other reason we don't compress into cab is time, since we compress everything into RARs for client delivery... so a cab will be redundant. But point taken, I won't let anyone change a thing :). To the main problem... I still can't seem to be able to run the Pyro command no matter what... After taking your advice I removed the from within the tag And then I did get errors referring to my files, that is progress... but the errors are as mentioned before: C:\Sample_1>pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. The first section is: Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information I understand, I won't change the product ID between builds. The second part: E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. That I don't understand, I didn't remove anything, maybe they are getting different ids!? Both MSIs I used to generate the diff.wixmst are the same except for some code change in one of the assemblies... Thanks again! -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 3:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That would invalidate the MSI if you don't keep the relevant tables up to date too. Its not a recommended practice - do a proper build instead. I've not built a patch targeting an unpacked MSI but I believe the media number would still need to be higher than the highest file id in the MSI file table. The patch itself will contain cabinets for the altered files using the media cabinet name. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 13:01 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch One more thing I remembered, in our MSIs we don't use CAB, we just create a folder next to the MSI, it's easier for us to replace/fix text/config files after a build was already create... Does this influence the patch.wxs? I see that there is a Media tag that points to a cab file... -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January
Re: [WiX-users] creating a WIX small or minor patch
Hi,
Yes, I think you are right, I got this when running the command you suggested:
MSI (s) (F8:34) [08:51:01:014]: SELMGR: ComponentId
'{9CD3A290-0DD5-4416-85D1-4781D9C8C0B6}' is registered to feature
'ProductFeature', but is not present in the Component table. Removal of
components from a feature is not supported!
I think it has to do with the fact that we are using HeatDirectory to harvest
the files, each component gets a different GUID every build... right?
So I'll have to look for a way to keep the IDs consistent over builds...
Thanks again.
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Tuesday, January 24, 2012 4:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] creating a WIX small or minor patch
I don't think your problems are related to patch building. I think your second
MSI is not a valid minor update.
Try running the second MSI as an upgrade of the first one using the command
line mentioned in Rob's blog
http://robmensching.com/blog/posts/2007/1/4/Doing-a-small-update-or-minor-upg
rade-in-MSI-Use
I think you'll get some similar errors in the log.
If this is the case, you go through the MSDN sections mentioned on making minor
upgrades and check both of your MSIs to ensure you're following all the rules -
they are quick tricky. Comparing the two MSIs by looking at them in Orca rather
than by looking at the code so you can see what's actually been generated.
-Original Message-
From: tome...@qualisystems.com [mailto:tome...@qualisystems.com]
Sent: 24 January 2012 14:00
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] creating a WIX small or minor patch
I see, the other reason we don't compress into cab is time, since we compress
everything into RARs for client delivery... so a cab will be redundant. But
point taken, I won't let anyone change a thing :).
To the main problem... I still can't seem to be able to run the Pyro command no
matter what...
After taking your advice I removed the
from within the tag
And then I did get errors referring to my files, that is progress... but the
errors are as mentioned before:
C:\Sample_1>pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM
patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version
3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved.
pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not
recommended because the patch cannot be uninstalled nor can it be sequenced
along with other patches for the target product.
See http://msdn2.microsoft.com/library/aa367571.aspx for more information.
E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 :
Removing component 'QsConfig.exe' from feature 'ProductFeature' is not
supported. Either the component was removed or the guid changed. Add the
component back, undo the change to the component guid, or remove the entire
feature.
The first section is:
Changing the ProductCode in a patch is not recommended because the patch cannot
be uninstalled nor can it be sequenced along with other patches for the target
product.
See http://msdn2.microsoft.com/library/aa367571.aspx for more information
I understand, I won't change the product ID between builds.
The second part:
E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 :
Removing component 'QsConfig.exe' from feature 'ProductFeature' is not
supported. Either the component was removed or the guid changed. Add the
component back, undo the change to the component guid, or remove the entire
feature.
That I don't understand, I didn't remove anything, maybe they are getting
different ids!? Both MSIs I used to generate the diff.wixmst are the same
except for some code change in one of the assemblies...
Thanks again!
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Tuesday, January 24, 2012 3:09 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] creating a WIX small or minor patch
That would invalidate the MSI if you don't keep the relevant tables up to date
too. Its not a recommended practice - do a proper build instead.
I've not built a patch targeting an unpacked MSI but I believe the media number
would still need to be higher than the highest file id in the MSI file table.
The patch itself will contain cabinets for the altered files using the media
cabinet name.
-Original Message-
From: tome...@qualisystems.com [mailto:tome...@qualisystems.com]
Sent: 24 January 2012 13:01
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] creating a WIX small or minor patch
One more thing I remembered, in our MSIs we don't use CAB, we just create a
folder next to the MSI, it's easier for us to replace/fix text/
Re: [WiX-users] creating a WIX small or minor patch
I don't think your problems are related to patch building. I think your second MSI is not a valid minor update. Try running the second MSI as an upgrade of the first one using the command line mentioned in Rob's blog http://robmensching.com/blog/posts/2007/1/4/Doing-a-small-update-or-minor-upg rade-in-MSI-Use I think you'll get some similar errors in the log. If this is the case, you go through the MSDN sections mentioned on making minor upgrades and check both of your MSIs to ensure you're following all the rules - they are quick tricky. Comparing the two MSIs by looking at them in Orca rather than by looking at the code so you can see what's actually been generated. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 14:00 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch I see, the other reason we don't compress into cab is time, since we compress everything into RARs for client delivery... so a cab will be redundant. But point taken, I won't let anyone change a thing :). To the main problem... I still can't seem to be able to run the Pyro command no matter what... After taking your advice I removed the from within the tag And then I did get errors referring to my files, that is progress... but the errors are as mentioned before: C:\Sample_1>pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. The first section is: Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information I understand, I won't change the product ID between builds. The second part: E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. That I don't understand, I didn't remove anything, maybe they are getting different ids!? Both MSIs I used to generate the diff.wixmst are the same except for some code change in one of the assemblies... Thanks again! -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 3:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That would invalidate the MSI if you don't keep the relevant tables up to date too. Its not a recommended practice - do a proper build instead. I've not built a patch targeting an unpacked MSI but I believe the media number would still need to be higher than the highest file id in the MSI file table. The patch itself will contain cabinets for the altered files using the media cabinet name. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 13:01 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch One more thing I remembered, in our MSIs we don't use CAB, we just create a folder next to the MSI, it's easier for us to replace/fix text/config files after a build was already create... Does this influence the patch.wxs? I see that there is a Media tag that points to a cab file... -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 11:35 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The product code and the upgrade code are 2 different things. Don't mix them up. You can get the product code from the property table of the original MSI. Just open it in Orca or InstEd. The * means "generate me a guid at build time" - it isn't actually stored as a *. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 08:23 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-
Re: [WiX-users] creating a WIX small or minor patch
I see, the other reason we don't compress into cab is time, since we compress everything into RARs for client delivery... so a cab will be redundant. But point taken, I won't let anyone change a thing :). To the main problem... I still can't seem to be able to run the Pyro command no matter what... After taking your advice I removed the from within the tag And then I did get errors referring to my files, that is progress... but the errors are as mentioned before: C:\Sample_1>pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. The first section is: Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information I understand, I won't change the product ID between builds. The second part: E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. That I don't understand, I didn't remove anything, maybe they are getting different ids!? Both MSIs I used to generate the diff.wixmst are the same except for some code change in one of the assemblies... Thanks again! -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 3:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That would invalidate the MSI if you don't keep the relevant tables up to date too. Its not a recommended practice - do a proper build instead. I've not built a patch targeting an unpacked MSI but I believe the media number would still need to be higher than the highest file id in the MSI file table. The patch itself will contain cabinets for the altered files using the media cabinet name. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 13:01 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch One more thing I remembered, in our MSIs we don't use CAB, we just create a folder next to the MSI, it's easier for us to replace/fix text/config files after a build was already create... Does this influence the patch.wxs? I see that there is a Media tag that points to a cab file... -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 11:35 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The product code and the upgrade code are 2 different things. Don't mix them up. You can get the product code from the property table of the original MSI. Just open it in Orca or InstEd. The * means "generate me a guid at build time" - it isn't actually stored as a *. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 08:23 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, I tried replacing the * with the UpgradeCode Guid. Still the same errors... I must say the erros seem to be related to the fact that the patch.wxs has nothing to do with the build diff.wixmst generated from the 2 winxobj... Anyway I have products installed at customers already with the * in the product Id, how do I get the Guid that was generated for those MSIs? Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 23, 2012 1:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch Have you used "*" as the product code guid ? If so, youll need to change the updated MSI's product code to match the originals and rebuild. Removing a component in a minor update/patch is not allowed. Usually
Re: [WiX-users] creating a WIX small or minor patch
That would invalidate the MSI if you don't keep the relevant tables up to date too. Its not a recommended practice - do a proper build instead. I've not built a patch targeting an unpacked MSI but I believe the media number would still need to be higher than the highest file id in the MSI file table. The patch itself will contain cabinets for the altered files using the media cabinet name. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 13:01 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch One more thing I remembered, in our MSIs we don't use CAB, we just create a folder next to the MSI, it's easier for us to replace/fix text/config files after a build was already create... Does this influence the patch.wxs? I see that there is a Media tag that points to a cab file... -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 11:35 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The product code and the upgrade code are 2 different things. Don't mix them up. You can get the product code from the property table of the original MSI. Just open it in Orca or InstEd. The * means "generate me a guid at build time" - it isn't actually stored as a *. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 08:23 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, I tried replacing the * with the UpgradeCode Guid. Still the same errors... I must say the erros seem to be related to the fact that the patch.wxs has nothing to do with the build diff.wixmst generated from the 2 winxobj... Anyway I have products installed at customers already with the * in the product Id, how do I get the Guid that was generated for those MSIs? Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 23, 2012 1:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch Have you used "*" as the product code guid ? If so, youll need to change the updated MSI's product code to match the originals and rebuild. Removing a component in a minor update/patch is not allowed. Usually you just leave the file there until the next major upgrade. You can also replace the file with a zero length file if necessary. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 22 January 2012 06:41 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, Thanks for the replay, you are right, removing the children from the PatchFamily element does include everything. But now I have a new problems :) I get this error: C:\Sample_1>pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. What does it mean? -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 20, 2012 1:35 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] creating a WIX small or minor patch Do you really need to exclude anything from your patch? Do you really need more than one PatchFamily? If "no" on both questions then remove all children from the PatchFamily element. No references means include everything. Otherwise you will need to examine the generated WXS files and ensure that the IDs are stable and include all of them that you intend to possibly upgrade. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 19, 2012 5:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Sure. I got that. I did make sure that the "placeholder" id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then wi
Re: [WiX-users] creating a WIX small or minor patch
One more thing I remembered, in our MSIs we don't use CAB, we just create a folder next to the MSI, it's easier for us to replace/fix text/config files after a build was already create... Does this influence the patch.wxs? I see that there is a Media tag that points to a cab file... -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 11:35 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The product code and the upgrade code are 2 different things. Don't mix them up. You can get the product code from the property table of the original MSI. Just open it in Orca or InstEd. The * means "generate me a guid at build time" - it isn't actually stored as a *. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 08:23 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, I tried replacing the * with the UpgradeCode Guid. Still the same errors... I must say the erros seem to be related to the fact that the patch.wxs has nothing to do with the build diff.wixmst generated from the 2 winxobj... Anyway I have products installed at customers already with the * in the product Id, how do I get the Guid that was generated for those MSIs? Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 23, 2012 1:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch Have you used "*" as the product code guid ? If so, youll need to change the updated MSI's product code to match the originals and rebuild. Removing a component in a minor update/patch is not allowed. Usually you just leave the file there until the next major upgrade. You can also replace the file with a zero length file if necessary. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 22 January 2012 06:41 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, Thanks for the replay, you are right, removing the children from the PatchFamily element does include everything. But now I have a new problems :) I get this error: C:\Sample_1>pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. What does it mean? -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 20, 2012 1:35 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] creating a WIX small or minor patch Do you really need to exclude anything from your patch? Do you really need more than one PatchFamily? If "no" on both questions then remove all children from the PatchFamily element. No references means include everything. Otherwise you will need to examine the generated WXS files and ensure that the IDs are stable and include all of them that you intend to possibly upgrade. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 19, 2012 5:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Sure. I got that. I did make sure that the "placeholder" id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then with the help of the HeatDirectory I Harvest and create the Files.wxs dynamically for each product. Thanks! Ask me if something is missing! Don't work too hard to understand, just ask! :) Thanks again -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Wednesday, January 18, 2012 10:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The problem is a mismatch between the PatchBaseline you have in the patch wxs and the baseline you are specifying to pyro to attach the transform to.
Re: [WiX-users] creating a WIX small or minor patch
Yea, I got that, Thanks. What I meant was that I can use the same Guid for the Product ID and the UpgradeCode as the example do. That way I won't have to open the MSI with ORCA and find the generated Product ID Guid. But anyway, it doesn't help :( I really don't understand the problem... I take 2 wixpdb files that where generated during 2 different builds of the same product, the later one has a change somewhere in the code. All I want it to generate the patch, I don't mind if the patch will include all the .NET assemblies and not only the changed ones - since I know every build they are different. Thanks for the fast replay - any help will be appreciated greatly! P.S I'm trying to find an official Microsoft representative that can grant our company (we are a Microsoft gold partner) consulting hours for this issue. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 11:35 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The product code and the upgrade code are 2 different things. Don't mix them up. You can get the product code from the property table of the original MSI. Just open it in Orca or InstEd. The * means "generate me a guid at build time" - it isn't actually stored as a *. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 08:23 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, I tried replacing the * with the UpgradeCode Guid. Still the same errors... I must say the erros seem to be related to the fact that the patch.wxs has nothing to do with the build diff.wixmst generated from the 2 winxobj... Anyway I have products installed at customers already with the * in the product Id, how do I get the Guid that was generated for those MSIs? Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 23, 2012 1:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch Have you used "*" as the product code guid ? If so, youll need to change the updated MSI's product code to match the originals and rebuild. Removing a component in a minor update/patch is not allowed. Usually you just leave the file there until the next major upgrade. You can also replace the file with a zero length file if necessary. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 22 January 2012 06:41 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, Thanks for the replay, you are right, removing the children from the PatchFamily element does include everything. But now I have a new problems :) I get this error: C:\Sample_1>pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. What does it mean? -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 20, 2012 1:35 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] creating a WIX small or minor patch Do you really need to exclude anything from your patch? Do you really need more than one PatchFamily? If "no" on both questions then remove all children from the PatchFamily element. No references means include everything. Otherwise you will need to examine the generated WXS files and ensure that the IDs are stable and include all of them that you intend to possibly upgrade. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 19, 2012 5:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Sure. I got that. I did make sure that the "placeholder" id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then with the help of the HeatDirectory I H
Re: [WiX-users] creating a WIX small or minor patch
The product code and the upgrade code are 2 different things. Don't mix them up. You can get the product code from the property table of the original MSI. Just open it in Orca or InstEd. The * means "generate me a guid at build time" - it isn't actually stored as a *. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 08:23 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, I tried replacing the * with the UpgradeCode Guid. Still the same errors... I must say the erros seem to be related to the fact that the patch.wxs has nothing to do with the build diff.wixmst generated from the 2 winxobj... Anyway I have products installed at customers already with the * in the product Id, how do I get the Guid that was generated for those MSIs? Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 23, 2012 1:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch Have you used "*" as the product code guid ? If so, youll need to change the updated MSI's product code to match the originals and rebuild. Removing a component in a minor update/patch is not allowed. Usually you just leave the file there until the next major upgrade. You can also replace the file with a zero length file if necessary. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 22 January 2012 06:41 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, Thanks for the replay, you are right, removing the children from the PatchFamily element does include everything. But now I have a new problems :) I get this error: C:\Sample_1>pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. What does it mean? -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 20, 2012 1:35 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] creating a WIX small or minor patch Do you really need to exclude anything from your patch? Do you really need more than one PatchFamily? If "no" on both questions then remove all children from the PatchFamily element. No references means include everything. Otherwise you will need to examine the generated WXS files and ensure that the IDs are stable and include all of them that you intend to possibly upgrade. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 19, 2012 5:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Sure. I got that. I did make sure that the "placeholder" id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then with the help of the HeatDirectory I Harvest and create the Files.wxs dynamically for each product. Thanks! Ask me if something is missing! Don't work too hard to understand, just ask! :) Thanks again -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Wednesday, January 18, 2012 10:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The problem is a mismatch between the PatchBaseline you have in the patch wxs and the baseline you are specifying to pyro to attach the transform to. The first argument after the -t is the baseline. If your patch targets RTM (your patch will apply to an RTM install) then you should have Id="RTM" for PatchBaseline\@Id. -t RTM out\patch\diff.wixmst -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 18, 2012 1:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The pyro command looks OK. Could you post your torch, candle and light command lines and your patch wxs pl
Re: [WiX-users] creating a WIX small or minor patch
Hi, I tried replacing the * with the UpgradeCode Guid. Still the same errors... I must say the erros seem to be related to the fact that the patch.wxs has nothing to do with the build diff.wixmst generated from the 2 winxobj... Anyway I have products installed at customers already with the * in the product Id, how do I get the Guid that was generated for those MSIs? Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 23, 2012 1:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch Have you used "*" as the product code guid ? If so, youll need to change the updated MSI's product code to match the originals and rebuild. Removing a component in a minor update/patch is not allowed. Usually you just leave the file there until the next major upgrade. You can also replace the file with a zero length file if necessary. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 22 January 2012 06:41 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, Thanks for the replay, you are right, removing the children from the PatchFamily element does include everything. But now I have a new problems :) I get this error: C:\Sample_1>pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. What does it mean? -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 20, 2012 1:35 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] creating a WIX small or minor patch Do you really need to exclude anything from your patch? Do you really need more than one PatchFamily? If "no" on both questions then remove all children from the PatchFamily element. No references means include everything. Otherwise you will need to examine the generated WXS files and ensure that the IDs are stable and include all of them that you intend to possibly upgrade. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 19, 2012 5:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Sure. I got that. I did make sure that the "placeholder" id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then with the help of the HeatDirectory I Harvest and create the Files.wxs dynamically for each product. Thanks! Ask me if something is missing! Don't work too hard to understand, just ask! :) Thanks again -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Wednesday, January 18, 2012 10:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The problem is a mismatch between the PatchBaseline you have in the patch wxs and the baseline you are specifying to pyro to attach the transform to. The first argument after the -t is the baseline. If your patch targets RTM (your patch will apply to an RTM install) then you should have Id="RTM" for PatchBaseline\@Id. -t RTM out\patch\diff.wixmst -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 18, 2012 1:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The pyro command looks OK. Could you post your torch, candle and light command lines and your patch wxs please ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 18 January 2012 08:02 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right I
Re: [WiX-users] creating a WIX small or minor patch
I did have a mailto:pshirtcli...@sdl.com] Sent: Monday, January 23, 2012 1:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch Have you used "*" as the product code guid ? If so, youll need to change the updated MSI's product code to match the originals and rebuild. Removing a component in a minor update/patch is not allowed. Usually you just leave the file there until the next major upgrade. You can also replace the file with a zero length file if necessary. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 22 January 2012 06:41 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, Thanks for the replay, you are right, removing the children from the PatchFamily element does include everything. But now I have a new problems :) I get this error: C:\Sample_1>pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. What does it mean? -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 20, 2012 1:35 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] creating a WIX small or minor patch Do you really need to exclude anything from your patch? Do you really need more than one PatchFamily? If "no" on both questions then remove all children from the PatchFamily element. No references means include everything. Otherwise you will need to examine the generated WXS files and ensure that the IDs are stable and include all of them that you intend to possibly upgrade. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 19, 2012 5:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Sure. I got that. I did make sure that the "placeholder" id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then with the help of the HeatDirectory I Harvest and create the Files.wxs dynamically for each product. Thanks! Ask me if something is missing! Don't work too hard to understand, just ask! :) Thanks again -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Wednesday, January 18, 2012 10:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The problem is a mismatch between the PatchBaseline you have in the patch wxs and the baseline you are specifying to pyro to attach the transform to. The first argument after the -t is the baseline. If your patch targets RTM (your patch will apply to an RTM install) then you should have Id="RTM" for PatchBaseline\@Id. -t RTM out\patch\diff.wixmst -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 18, 2012 1:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The pyro command looks OK. Could you post your torch, candle and light command lines and your patch wxs please ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 18 January 2012 08:02 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but when I use the same technique on my wixpdb's I get the error mentioned below. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 11, 2012 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That is a e
Re: [WiX-users] creating a WIX small or minor patch
Have you used "*" as the product code guid ? If so, youll need to change the updated MSI's product code to match the originals and rebuild. Removing a component in a minor update/patch is not allowed. Usually you just leave the file there until the next major upgrade. You can also replace the file with a zero length file if necessary. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 22 January 2012 06:41 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, Thanks for the replay, you are right, removing the children from the PatchFamily element does include everything. But now I have a new problems :) I get this error: C:\Sample_1>pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. What does it mean? -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 20, 2012 1:35 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] creating a WIX small or minor patch Do you really need to exclude anything from your patch? Do you really need more than one PatchFamily? If "no" on both questions then remove all children from the PatchFamily element. No references means include everything. Otherwise you will need to examine the generated WXS files and ensure that the IDs are stable and include all of them that you intend to possibly upgrade. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 19, 2012 5:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Sure. I got that. I did make sure that the "placeholder" id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then with the help of the HeatDirectory I Harvest and create the Files.wxs dynamically for each product. Thanks! Ask me if something is missing! Don't work too hard to understand, just ask! :) Thanks again -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Wednesday, January 18, 2012 10:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The problem is a mismatch between the PatchBaseline you have in the patch wxs and the baseline you are specifying to pyro to attach the transform to. The first argument after the -t is the baseline. If your patch targets RTM (your patch will apply to an RTM install) then you should have Id="RTM" for PatchBaseline\@Id. -t RTM out\patch\diff.wixmst -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 18, 2012 1:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The pyro command looks OK. Could you post your torch, candle and light command lines and your patch wxs please ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 18 January 2012 08:02 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but when I use the same technique on my wixpdb's I get the error mentioned below. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 11, 2012 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That is a example from one of our released products. The Id in the patchbaseline is something you invent and only appears otherwise on the pyro command line. Why do you say that your files are relevant ? -Original Message- Fr
Re: [WiX-users] creating a WIX small or minor patch
Hi, Thanks for the replay, you are right, removing the children from the PatchFamily element does include everything. But now I have a new problems :) I get this error: C:\Sample_1>pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. What does it mean? -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 20, 2012 1:35 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] creating a WIX small or minor patch Do you really need to exclude anything from your patch? Do you really need more than one PatchFamily? If "no" on both questions then remove all children from the PatchFamily element. No references means include everything. Otherwise you will need to examine the generated WXS files and ensure that the IDs are stable and include all of them that you intend to possibly upgrade. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 19, 2012 5:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Sure. I got that. I did make sure that the "placeholder" id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then with the help of the HeatDirectory I Harvest and create the Files.wxs dynamically for each product. Thanks! Ask me if something is missing! Don't work too hard to understand, just ask! :) Thanks again -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Wednesday, January 18, 2012 10:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The problem is a mismatch between the PatchBaseline you have in the patch wxs and the baseline you are specifying to pyro to attach the transform to. The first argument after the -t is the baseline. If your patch targets RTM (your patch will apply to an RTM install) then you should have Id="RTM" for PatchBaseline\@Id. -t RTM out\patch\diff.wixmst -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 18, 2012 1:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The pyro command looks OK. Could you post your torch, candle and light command lines and your patch wxs please ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 18 January 2012 08:02 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but when I use the same technique on my wixpdb's I get the error mentioned below. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 11, 2012 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That is a example from one of our released products. The Id in the patchbaseline is something you invent and only appears otherwise on the pyro command line. Why do you say that your files are relevant ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 10 January 2012 11:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Yea, that I got from the sample, the problem is that our build.wxs files are a "bit" more complicated than the example ones... We are using HearDirectory to create our file list, and the file list generated doesn't have a nice ID that I can reference too... What I really need is a good example, an example that shows how to work with re
Re: [WiX-users] creating a WIX small or minor patch
Do you really need to exclude anything from your patch? Do you really need more than one PatchFamily? If "no" on both questions then remove all children from the PatchFamily element. No references means include everything. Otherwise you will need to examine the generated WXS files and ensure that the IDs are stable and include all of them that you intend to possibly upgrade. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 19, 2012 5:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Sure. I got that. I did make sure that the "placeholder" id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then with the help of the HeatDirectory I Harvest and create the Files.wxs dynamically for each product. Thanks! Ask me if something is missing! Don't work too hard to understand, just ask! :) Thanks again -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Wednesday, January 18, 2012 10:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The problem is a mismatch between the PatchBaseline you have in the patch wxs and the baseline you are specifying to pyro to attach the transform to. The first argument after the -t is the baseline. If your patch targets RTM (your patch will apply to an RTM install) then you should have Id="RTM" for PatchBaseline\@Id. -t RTM out\patch\diff.wixmst -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 18, 2012 1:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The pyro command looks OK. Could you post your torch, candle and light command lines and your patch wxs please ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 18 January 2012 08:02 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but when I use the same technique on my wixpdb's I get the error mentioned below. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 11, 2012 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That is a example from one of our released products. The Id in the patchbaseline is something you invent and only appears otherwise on the pyro command line. Why do you say that your files are relevant ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 10 January 2012 11:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Yea, that I got from the sample, the problem is that our build.wxs files are a "bit" more complicated than the example ones... We are using HearDirectory to create our file list, and the file list generated doesn't have a nice ID that I can reference too... What I really need is a good example, an example that shows how to work with real life scenarios... Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 09, 2012 6:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch This goes in the Patch element. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 09 January 2012 15:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] creating a WIX small or minor patch HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the c
Re: [WiX-users] creating a WIX small or minor patch
Sure. I got that. I did make sure that the "placeholder" id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then with the help of the HeatDirectory I Harvest and create the Files.wxs dynamically for each product. Thanks! Ask me if something is missing! Don't work too hard to understand, just ask! :) Thanks again -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Wednesday, January 18, 2012 10:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The problem is a mismatch between the PatchBaseline you have in the patch wxs and the baseline you are specifying to pyro to attach the transform to. The first argument after the -t is the baseline. If your patch targets RTM (your patch will apply to an RTM install) then you should have Id="RTM" for PatchBaseline\@Id. -t RTM out\patch\diff.wixmst -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 18, 2012 1:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The pyro command looks OK. Could you post your torch, candle and light command lines and your patch wxs please ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 18 January 2012 08:02 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but when I use the same technique on my wixpdb's I get the error mentioned below. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 11, 2012 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That is a example from one of our released products. The Id in the patchbaseline is something you invent and only appears otherwise on the pyro command line. Why do you say that your files are relevant ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 10 January 2012 11:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Yea, that I got from the sample, the problem is that our build.wxs files are a "bit" more complicated than the example ones... We are using HearDirectory to create our file list, and the file list generated doesn't have a nice ID that I can reference too... What I really need is a good example, an example that shows how to work with real life scenarios... Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 09, 2012 6:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch This goes in the Patch element. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 09 January 2012 15:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] creating a WIX small or minor patch HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, R&D QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax: +972-77-9014099 phone: +972-77-9014094 Mobile: +972-52-3362846 Email: tome...@qualisystems.com Web: www.qualisystems.com QualiSystems | 20 Hacarmel St. Ganey Tikva, Israel 55900 Learn about our NEW Test Automation S
Re: [WiX-users] creating a WIX small or minor patch
The problem is a mismatch between the PatchBaseline you have in the patch wxs and the baseline you are specifying to pyro to attach the transform to. The first argument after the -t is the baseline. If your patch targets RTM (your patch will apply to an RTM install) then you should have Id="RTM" for PatchBaseline\@Id. -t RTM out\patch\diff.wixmst -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 18, 2012 1:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The pyro command looks OK. Could you post your torch, candle and light command lines and your patch wxs please ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 18 January 2012 08:02 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but when I use the same technique on my wixpdb's I get the error mentioned below. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 11, 2012 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That is a example from one of our released products. The Id in the patchbaseline is something you invent and only appears otherwise on the pyro command line. Why do you say that your files are relevant ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 10 January 2012 11:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Yea, that I got from the sample, the problem is that our build.wxs files are a "bit" more complicated than the example ones... We are using HearDirectory to create our file list, and the file list generated doesn't have a nice ID that I can reference too... What I really need is a good example, an example that shows how to work with real life scenarios... Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 09, 2012 6:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch This goes in the Patch element. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 09 January 2012 15:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] creating a WIX small or minor patch HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, R&D QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax: +972-77-9014099 phone: +972-77-9014094 Mobile: +972-52-3362846 Email: tome...@qualisystems.com Web: www.qualisystems.com QualiSystems | 20 Hacarmel St. Ganey Tikva, Israel 55900 Learn about our NEW Test Automation Solution - TestShell Studio Join our QA Test Automation Group on LinkedIn Standards of Excellence This email including any attachment may contain confidential and/or privileged information intended solely for the use of the specified addressee[s]. Its contents shall not be copied, reproduced, changed or communicated to another - either in whole or in part. If you have received this email or parts thereof in error we request that you immediately notify us and delete this email. - - Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure acce
Re: [WiX-users] creating a WIX small or minor patch
The pyro command looks OK. Could you post your torch, candle and light command lines and your patch wxs please ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 18 January 2012 08:02 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but when I use the same technique on my wixpdb's I get the error mentioned below. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 11, 2012 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That is a example from one of our released products. The Id in the patchbaseline is something you invent and only appears otherwise on the pyro command line. Why do you say that your files are relevant ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 10 January 2012 11:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Yea, that I got from the sample, the problem is that our build.wxs files are a "bit" more complicated than the example ones... We are using HearDirectory to create our file list, and the file list generated doesn't have a nice ID that I can reference too... What I really need is a good example, an example that shows how to work with real life scenarios... Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 09, 2012 6:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch This goes in the Patch element. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 09 January 2012 15:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] creating a WIX small or minor patch HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, R&D QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax: +972-77-9014099 phone: +972-77-9014094 Mobile: +972-52-3362846 Email: tome...@qualisystems.com Web: www.qualisystems.com QualiSystems | 20 Hacarmel St. Ganey Tikva, Israel 55900 Learn about our NEW Test Automation Solution - TestShell Studio Join our QA Test Automation Group on LinkedIn Standards of Excellence This email including any attachment may contain confidential and/or privileged information intended solely for the use of the specified addressee[s]. Its contents shall not be copied, reproduced, changed or communicated to another - either in whole or in part. If you have received this email or parts thereof in error we request that you immediately notify us and delete this email. - - Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited
Re: [WiX-users] creating a WIX small or minor patch
Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but when I use the same technique on my wixpdb's I get the error mentioned below. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 11, 2012 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That is a example from one of our released products. The Id in the patchbaseline is something you invent and only appears otherwise on the pyro command line. Why do you say that your files are relevant ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 10 January 2012 11:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Yea, that I got from the sample, the problem is that our build.wxs files are a "bit" more complicated than the example ones... We are using HearDirectory to create our file list, and the file list generated doesn't have a nice ID that I can reference too... What I really need is a good example, an example that shows how to work with real life scenarios... Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 09, 2012 6:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch This goes in the Patch element. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 09 January 2012 15:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] creating a WIX small or minor patch HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, R&D QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax: +972-77-9014099 phone: +972-77-9014094 Mobile: +972-52-3362846 Email: tome...@qualisystems.com Web: www.qualisystems.com QualiSystems | 20 Hacarmel St. Ganey Tikva, Israel 55900 Learn about our NEW Test Automation Solution - TestShell Studio Join our QA Test Automation Group on LinkedIn Standards of Excellence This email including any attachment may contain confidential and/or privileged information intended solely for the use of the specified addressee[s]. Its contents shall not be copied, reproduced, changed or communicated to another - either in whole or in part. If you have received this email or parts thereof in error we request that you immediately notify us and delete this email. - - Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. - - Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a
Re: [WiX-users] creating a WIX small or minor patch
That is a example from one of our released products. The Id in the patchbaseline is something you invent and only appears otherwise on the pyro command line. Why do you say that your files are relevant ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 10 January 2012 11:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Yea, that I got from the sample, the problem is that our build.wxs files are a "bit" more complicated than the example ones... We are using HearDirectory to create our file list, and the file list generated doesn't have a nice ID that I can reference too... What I really need is a good example, an example that shows how to work with real life scenarios... Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 09, 2012 6:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch This goes in the Patch element. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 09 January 2012 15:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] creating a WIX small or minor patch HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, R&D QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax: +972-77-9014099 phone: +972-77-9014094 Mobile: +972-52-3362846 Email: tome...@qualisystems.com Web: www.qualisystems.com QualiSystems | 20 Hacarmel St. Ganey Tikva, Israel 55900 Learn about our NEW Test Automation Solution - TestShell Studio Join our QA Test Automation Group on LinkedIn Standards of Excellence This email including any attachment may contain confidential and/or privileged information intended solely for the use of the specified addressee[s]. Its contents shall not be copied, reproduced, changed or communicated to another - either in whole or in part. If you have received this email or parts thereof in error we request that you immediately notify us and delete this email. - - Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. - - Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Ex
Re: [WiX-users] creating a WIX small or minor patch
Yea, that I got from the sample, the problem is that our build.wxs files are a "bit" more complicated than the example ones... We are using HearDirectory to create our file list, and the file list generated doesn't have a nice ID that I can reference too... What I really need is a good example, an example that shows how to work with real life scenarios... Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 09, 2012 6:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch This goes in the Patch element. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 09 January 2012 15:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] creating a WIX small or minor patch HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, R&D QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax: +972-77-9014099 phone: +972-77-9014094 Mobile: +972-52-3362846 Email: tome...@qualisystems.com Web: www.qualisystems.com QualiSystems | 20 Hacarmel St. Ganey Tikva, Israel 55900 Learn about our NEW Test Automation Solution - TestShell Studio Join our QA Test Automation Group on LinkedIn Standards of Excellence This email including any attachment may contain confidential and/or privileged information intended solely for the use of the specified addressee[s]. Its contents shall not be copied, reproduced, changed or communicated to another - either in whole or in part. If you have received this email or parts thereof in error we request that you immediately notify us and delete this email. - - Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] creating a WIX small or minor patch
This goes in the Patch element. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 09 January 2012 15:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] creating a WIX small or minor patch HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, R&D QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax: +972-77-9014099 phone: +972-77-9014094 Mobile: +972-52-3362846 Email: tome...@qualisystems.com Web: www.qualisystems.com QualiSystems | 20 Hacarmel St. Ganey Tikva, Israel 55900 Learn about our NEW Test Automation Solution - TestShell Studio Join our QA Test Automation Group on LinkedIn Standards of Excellence This email including any attachment may contain confidential and/or privileged information intended solely for the use of the specified addressee[s]. Its contents shall not be copied, reproduced, changed or communicated to another - either in whole or in part. If you have received this email or parts thereof in error we request that you immediately notify us and delete this email. - - Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] creating a WIX small or minor patch
HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, R&D QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax: +972-77-9014099 phone: +972-77-9014094 Mobile: +972-52-3362846 Email: tome...@qualisystems.com Web: www.qualisystems.com QualiSystems | 20 Hacarmel St. Ganey Tikva, Israel 55900 Learn about our NEW Test Automation Solution - TestShell Studio Join our QA Test Automation Group on LinkedIn Standards of Excellence This email including any attachment may contain confidential and/or privileged information intended solely for the use of the specified addressee[s]. Its contents shall not be copied, reproduced, changed or communicated to another - either in whole or in part. If you have received this email or parts thereof in error we request that you immediately notify us and delete this email. -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
