Hi,
I'm having trouble with pyro, I get the PYRO0227 error even though I know there
are changes between the files it's comparing.
I even debugged the pyro c# code, what I saw was that the
FileManager.CompareFiles works great, and the rows are marked
RowOperation.Modify. but the GenerateTransform
Hi all,
I'm having trouble with pyro, I get the PYRO0227 error even though I
know there are changes between the files it's comparing.
I even debugged the pyro c# code, what I saw was that the
FileManager.CompareFiles works great, and the rows are marked
RowOperation.Modify. but the GenerateTransfor
Hi all,
I'm having trouble with pyro, I get the PYRO0227 error even though I
know there are changes between the files it's comparing.
I even debugged the pyro c# code, what I saw was that the
FileManager.CompareFiles works great, and the rows are marked
RowOperation.Modify. but the GenerateTransfor
Hi.
I'm having problems with pyro.
I get this error: (note the weird Patch.msp in the temp directory
showing twice?!)
Copyright (C) Microsoft Corporation. All rights reserved.
Updating file information.
Creating cabinet files.
There will be '4' threads used to produce CAB files.
Creating cabinet
As always, you are correct :)
And yes, when I remove that line, or add an After/Before, it works
great...
Too bad, I was hoping on using dark to avoid having to save the PDB of
each released version...
I don't wanna hard code removal of this line in my script...
Got any ideas?
And Thanks again!
One more thing I found out: (concerning the msi to wixpdb using dark,
candle, light)
I have another tag in my setup.wxs:
(NOT Installed AND RUN_QSCONFIG = "true") OR (REINSTALL)
(Installed)
Maybe it ha
Hi,
Good to know about Dark.exe, didn't notice it till now :)
I'm having problems after converting my Original MSI to WXS file, I try
to Candle it so I can then light it to get the wixpdb, but I get this
error:
\\sqlsrv\tsinstallers\TestShell Suite\4.6.255 SP1\Data\Driver
Builder\TestShell
DriverB
Hi,
After all your help :) I think I have a solution to my problem, please
let me know what you think:
My product is already installed on customers machines, I didn't save the
wixpdb nor the files.wxs (the Heat harvest file) of those releases,
since I didn't know I'll need them to issue a patch, I
Thanks for the reply!
I did find reference to a file I was concerned about...
The problem is, that I changed the file locally on the "customers"
machine, then I installed the patch, the file wasn't replaced... that
led me to think that there was something wrong with the patch...
By the way the fil
One more thing, I opened the msp file with z7, there are only: exe dll
(.net assemblies) and one txt file!? there.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Friday, January 27, 2012 10:24 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-u
I'm creating a patch, I'm not sure that the patch includes all of my
files even though I'm passing the -p flag to the torch.exe.
Can someone please explain to me the logic that torch uses to determine
what files are included in the patch.
Thanks.
---
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.co
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
t
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 feat
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 wha
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...
-Origin
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
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 t
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 produ
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 Pa
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
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 fi
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, a
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 wix
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 wix
25 matches
Mail list logo
