You are correct Rob (as usual) :)
http://wixtoolset.org/issues/4072/
Guess I'll have to upgrade from 3.7 to 3.8 then for a more meaningful exception
for my co-workers to read.
Cheers guys, many thanks!
Stephen Tunney
Nuance Communications, Inc.
Solutions Architect, Imaging Division
Waterloo, Ontario, Canada
stephen.tun...@nuance.com<mailto:stephen.tun...@nuance.com>
519-880-7463 Office
NUANCE.COM
The experience speaks for itself (tm)
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: January-22-14 3:25 PM
To: WiX toolset developer mailing list; Toby Hu
Subject: Re: [WiX-devs] Pyro exception
If there isn't a bug already. This sounds very familiar to something was fixed
or considered for fixing in v3.8.
From: Tunney, Stephen [mailto:stephen.tun...@nuance.com]
Sent: Wednesday, January 22, 2014 11:13 AM
To: Toby Hu; WiX toolset developer mailing list
Subject: Re: [WiX-devs] Pyro exception
I think you are on the right track. Fortunately for my scenario we are only
half way through a major release cycle so I will simply bump my patch baseline
version to match the version that has the component deletions. Another team
member was doing some cleanup which I love.
Should I log a bug that perhaps a more meaningful exception should be logged in
this case?
Stephen Tunney
Nuance Communications, Inc.
Solutions Architect, Imaging Division
Waterloo, Ontario, Canada
stephen.tun...@nuance.com<mailto:stephen.tun...@nuance.com>
519-880-7463 Office
NUANCE.COM
The experience speaks for itself (tm)
From: Toby Hu [mailto:tob...@microsoft.com]
Sent: January-22-14 2:00 PM
To: WiX toolset developer mailing list; Tunney, Stephen
Subject: RE: Pyro exception
Hi Tunney,
Does your later build have deleted components? If you are creating a patch
between two build, where the later build has deleted components. I am not sure
if Wix allow this scenario. This scenario will result in unserviceable state
for the component.
Looking at the wix source, I think the NullReferenceException is thrown because
pyro was checking to see if the file from the deleted component is in the
"RemoveFile" table. If you don't specify the removed files in the table. The
following code would throw.
Table removeFileTable =
this.Transform.Tables["RemoveFile"];
foreach (Row removeFileRow in
removeFileTable.Rows) << removeFileTable can be null.
Can you try undoing the deleted components in later build and see if it works
for you?
Thanks
toby
From: Tunney, Stephen [mailto:stephen.tun...@nuance.com]
Sent: Wednesday, January 22, 2014 9:47 AM
To: wix-devs@lists.sourceforge.net<mailto:wix-devs@lists.sourceforge.net>
Subject: [WiX-devs] Pyro exception
Hey guys, getting an exception in pyro.
[exec] pyro.exe : error PYRO0001 : Object reference not set to an instance of
an object.
[exec]
[exec] Exception Type: System.NullReferenceException
[exec]
[exec] Stack Trace:
[exec] at Microsoft.Tools.WindowsInstallerXml.PatchTransform.Validate()
[exec] at
Microsoft.Tools.WindowsInstallerXml.Patch.AttachTransforms(ArrayList transforms)
[exec] at Microsoft.Tools.WindowsInstallerXml.Tools.Pyro.Run(String[]
args)
[exec]
[exec] Unhandled Exception: System.NullReferenceException: Object
reference not set to an instance of an object.
[exec] at Microsoft.Tools.WindowsInstallerXml.PatchTransform.Validate()
[exec] at
Microsoft.Tools.WindowsInstallerXml.Patch.AttachTransforms(ArrayList transforms)
[exec] at Microsoft.Tools.WindowsInstallerXml.Tools.Pyro.Run(String[]
args)
[exec] at Microsoft.Tools.WindowsInstallerXml.Tools.Pyro.Main(String[]
args)
Here is my command line (slightly redacted)
[exec] Starting 'C:\Program Files (x86)\WiX Toolset v3.7\bin\pyro.exe
("D:\Jenkins\workspace\Wasabi5_5.3_Patches/out/Patch/Patch.WebClient.wixmsp"
-out "D:\Jenkins\workspace\Wasabi5_5.3_Patches/out/Patch/Patch.WebClient.msp"
-t Product1.x64
"D:\Jenkins\workspace\Root_Patches/out/Patch/Patch.Product1.x64.wixmst" -t
Product2.x64
"D:\Jenkins\workspace\Root_Patches/out/Patch/Patch.Product2.x64.wixmst" -t
Product3.x64
"D:\Jenkins\workspace\Root_Patches/out/Patch/Patch.Product3.x64.wixmst" -t
PRODUCT4.x64
"D:\Jenkins\workspace\Root_Patches/out/Patch/Patch.PRODUCT4.x64.wixmst" -t
Product1.x86
"D:\Jenkins\workspace\Root_Patches/out/Patch/Patch.Product1.x86.wixmst" -t
Product2.x86
"D:\Jenkins\workspace\Root_Patches/out/Patch/Patch.Product2.x86.wixmst" -t
Product3.x86
"D:\Jenkins\workspace\Root_Patches/out/Patch/Patch.Product3.x86.wixmst" -t
PRODUCT4.x86
"D:\Jenkins\workspace\Root_Patches/out/Patch/Patch.PRODUCT4.x86.wixmst" )' in
'D:\Jenkins\workspace\Root_Patches\Installation\Patch'
Is there anything else I need to send out?
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
