Re: [WiX-users] Error 0x80070057: Failed to parse @Code value: -1
I see the fix in wix39rtm. WiX 3.9 and Bullseye appear to work better together. We're going to recommend upgrading to WiX 3.9. On Fri, Jul 3, 2015 at 8:54 AM, Rob Mensching r...@firegiant.com wrote: I was looking at HEAD. Bug fix in WiX v3.9 or v3.10? ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: CastroAlicea, Edwin [mailto:edwin_castroali...@mcafee.com] Sent: Thursday, July 2, 2015 5:42 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Error 0x80070057: Failed to parse @Code value: -1 Ok, that's really weird. That's not what I see at all. ExitCodeInfo.cs:38:this.Code = value.ToString(); I'm looking at wix38rtm. Does WiX 3.8.1128.0 not correspond to wix38rtm? -- Edwin G. Castro -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Edwin G. Castro -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 0x80070057: Failed to parse @Code value: -1
I was looking at HEAD. Bug fix in WiX v3.9 or v3.10? ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: CastroAlicea, Edwin [mailto:edwin_castroali...@mcafee.com] Sent: Thursday, July 2, 2015 5:42 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Error 0x80070057: Failed to parse @Code value: -1 Ok, that's really weird. That's not what I see at all. ExitCodeInfo.cs:38:this.Code = value.ToString(); I'm looking at wix38rtm. Does WiX 3.8.1128.0 not correspond to wix38rtm? -- Edwin G. Castro -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 0x80070057: Failed to parse @Code value: -1
I forgot to mention that I'm using WiX 3.8.1128.0. On Thu, Jul 2, 2015 at 5:07 PM, Edwin Castro egca...@gmail.com wrote: Our bundle fails to install when our product is built with bullseye for code coverage. The bundle log is not created. Instead Setup_timestamp_Failed.txt is created and contains the following: [04AC:0744][2015-07-02T14:59:01]e000: Error 0x80070057: Failed to parse @Code value: -1 [04AC:0744][2015-07-02T14:59:01]e000: Error 0x80070057: Failed to parse EXE package. [04AC:0744][2015-07-02T14:59:01]e000: Error 0x80070057: Failed to parse packages. [04AC:0744][2015-07-02T14:59:01]e000: Error 0x80070057: Failed to load manifest. [04AC:0744][2015-07-02T14:59:01]e000: Error 0x80070057: Failed to initialize core. Burn is failing to parse manifest.xml because it finds an ExitCode element with Code=-1 ExitCode Type=error Code=-1 / I compared the bad manifest.xml to a good manifest.xml from a normal, non-bullseye bundle which has the following ExitCode element: ExitCode Type=error Code=4294967295 / I think something performs a conversion from int to unsigned int under normal conditions and that thing is somehow getting interfered with when we have bullseye enabled. But I can't figure out what that thing is. I've looked the wixobj files created by candle and they appear to use -1: table name=ExitCode row sourceLineNumber=path\to\source\file.wxs*28 fieldVSCore32/field field-1/field fielderror/field /row /table The ExitCodeInfo constructor casts to an int before converting the value to a string and stored in the Code property. As far as I can tell the Code string is passed to XmlTextWriter.WriteAttributeString without further modification in Binder.CreateBurnManifest. I don't see where a signed int gets converted to unsigned when it gets written to manifest.xml. Field.Parse calls Convert.ToInt64 on the value read from the wixobj file and then casts it to an int. I think a -1 would still parse as -1 (signed integer) with this code. I'm still no closer to figuring out how I get Code=4294967295 on good builds. The code I read suggests I should get Code=-1 which clearly doesn't work. What am I missing? -- Edwin G. Castro -- Edwin G. Castro -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 0x80070057: Failed to parse @Code value: -1
Ok, that's really weird. That's not what I see at all. ExitCodeInfo.cs:38:this.Code = value.ToString(); I'm looking at wix38rtm. Does WiX 3.8.1128.0 not correspond to wix38rtm? -- Edwin G. Castro -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Thursday, July 02, 2015 5:18 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Error 0x80070057: Failed to parse @Code value: -1 ExitCodeInfo.cs:38:this.Code = unchecked((uint)value).ToString(); _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Edwin Castro [mailto:egca...@gmail.com] Sent: Thursday, July 2, 2015 5:08 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Error 0x80070057: Failed to parse @Code value: -1 Our bundle fails to install when our product is built with bullseye for code coverage. The bundle log is not created. Instead Setup_timestamp_Failed.txt is created and contains the following: [04AC:0744][2015-07-02T14:59:01]e000: Error 0x80070057: Failed to parse @Code value: -1 [04AC:0744][2015-07-02T14:59:01]e000: Error 0x80070057: Failed to parse EXE package. [04AC:0744][2015-07-02T14:59:01]e000: Error 0x80070057: Failed to parse packages. [04AC:0744][2015-07-02T14:59:01]e000: Error 0x80070057: Failed to load manifest. [04AC:0744][2015-07-02T14:59:01]e000: Error 0x80070057: Failed to initialize core. Burn is failing to parse manifest.xml because it finds an ExitCode element with Code=-1 ExitCode Type=error Code=-1 / I compared the bad manifest.xml to a good manifest.xml from a normal, non-bullseye bundle which has the following ExitCode element: ExitCode Type=error Code=4294967295 / I think something performs a conversion from int to unsigned int under normal conditions and that thing is somehow getting interfered with when we have bullseye enabled. But I can't figure out what that thing is. I've looked the wixobj files created by candle and they appear to use -1: table name=ExitCode row sourceLineNumber=path\to\source\file.wxs*28 fieldVSCore32/field field-1/field fielderror/field /row /table The ExitCodeInfo constructor casts to an int before converting the value to a string and stored in the Code property. As far as I can tell the Code string is passed to XmlTextWriter.WriteAttributeString without further modification in Binder.CreateBurnManifest. I don't see where a signed int gets converted to unsigned when it gets written to manifest.xml. Field.Parse calls Convert.ToInt64 on the value read from the wixobj file and then casts it to an int. I think a -1 would still parse as -1 (signed integer) with this code. I'm still no closer to figuring out how I get Code=4294967295 on good builds. The code I read suggests I should get Code=-1 which clearly doesn't work. What am I missing? -- Edwin G. Castro -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
