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.
<PatchBaseline Id="SP3" />
-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.
<!-- Id must be higher than any sequence number in the baseline msi's
Media/File table. Cabinet must match the original cabinet file name. -->
<Media Id="5728" Cabinet="Product.cab">
<!-- Id created for the patches' baseline. Referenced in the command
line. -->
<PatchBaseline Id="SP3" />
</Media>
-----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
-----------------------------------------------------------------------------
-
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
-----------------------------------------------------------------------------
-
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers is just
$99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style
Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers is just
$99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style
Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers is just
$99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style
Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Hi,
Attached are all the files concerning our setup, I will explain our installer
creation procedure and then Ill explain our attempts to create a patch.
The FoundationClient.proj is the starting point, it calls the BaseSetup.wixproj
that calls the WixHarverst.targets (that creates the files.wxs) and the
setup.wxs.
The output is an MSI file with a folder next to it that has all the files that
need to be installed (not using a cab file).
Besides the msi file we are also keeping the .wixpdb file.
After generating a setup for our product we fix some bugs, and generate another
setup, after that we have 2 .wixpdb files.
Using them we generate a diff.wixmst using torch.exe.
So far so good.
Our problem begin when we try to create a patch.wxs and use it with the
diff.wixmst to create a .msp file.
We cant seem to find any good documentation of how to do this, the only
documentation we have is the patch example from the web, it is very simple.
We are missing some parts; what do I have to write in the patch.wxs in order
for it to work with my current .wixmst generated from the .wixpdb files.
The pyro.exe command in the example passes a t flag for transformation
followed by the path to the diff.wixmst, I want it to work with my diff.wixmst
Either I get:
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.
Or if I change the Patch.wxs file section:
<Fragment>
<PatchFamily Id='SamplePatchFamily' Version='1.0.0' Supersede='yes'>
<ComponentRef Id="SampleComponent"/>
</PatchFamily>
</Fragment>
Changing the sampleComponent to the ID of the first Component in the files.wxs
file: ActiveDatabaseSoftware.ActiveQueryBuilder.dll
Then I get: (for every file in the files.wxs file)
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.
We are using wix 3.5
using those commands:
http://wix.sourceforge.net/manual-wix3/wix_patching.htm
candle.exe -dVersion=1.0 Build0.wxs
candle.exe -dVersion=1.1 Build1.wxs
light.exe Build0.wixobj -out out\1.0\product.msi
light.exe Build1.wixobj -out out\1.1\product.msi
torch.exe -p -xi out\1.0\product.wixpdb out\1.1\product.wixpdb -out
out\patch\diff.wixmst
candle.exe patch.wxs
light.exe patch.wixobj -out out\patch\patch.wixmsp
pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM
out\patch\diff.wixmst------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
