Re: [WiX-users] unhandled exception in light

That might do it... Quoting Simon Topley : > Although I have just found some localisation code in some old IIS ui > code we... borrowed from a web example. I'd removed all of the > loc.blah values and replaced with hardcoded strings, but missed one. > > -Original Message- > From: Simo

Re: [WiX-users] Code Signing

That's the documented way to sign. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Brian Enderle [mailto:bria...@gmail.com] Sent: Friday, June 27, 2014 5:12 AM To:

Re: [WiX-users] unhandled exception in light

Although I have just found some localisation code in some old IIS ui code we... borrowed from a web example. I'd removed all of the loc.blah values and replaced with hardcoded strings, but missed one. -Original Message- From: Simon Topley [mailto:simon.top...@innovyze.com] Sent: 27 June

Re: [WiX-users] unhandled exception in light

I could believe it was Unicode/ character related but it doesn't explain the intermittent nature of the failure. Are we saying that the wixobj files are sometimes ending up with an invalid character in them due to a codepage mismatch? I'd expect that to cause consistent failures. -Original

Re: [WiX-users] unhandled exception in light

Remove the codepages, and localize using this procedure: http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/make_installer_localizable.html saving each Localization Value in a different wxl file, then build an MSI(1 for each language value), then Bundle them all using Burn

Re: [WiX-users] unhandled exception in light

When I say yes we are localising it I mean we include a codepage value, we don't ship localised string etc. -Original Message- From: Carter Young [mailto:ecyo...@grandecom.net] Sent: 27 June 2014 15:19 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] unhandled exception in lig

Re: [WiX-users] unhandled exception in light

Yes indeed, Is this no longer the done thing? Our wix code is as old as the hills so contains a lot of stuff that is probably not needed anymore. -Original Message- From: Carter Young [mailto:ecyo...@grandecom.net] Sent: 27 June 2014 15:19 To: wix-users@lists.sourceforge.net Subject: Re:

Re: [WiX-users] Build issue

I can now compile the MSI thanks Carter. Michael Ogilvie -Original Message- From: Carter Young [mailto:ecyo...@grandecom.net] Sent: Friday, June 27, 2014 10:08 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Build issue This one gets you everytime. Thanks to Phil for

Re: [WiX-users] Build issue

Thanks, will give it a try and let you know. Michael Ogilvie -Original Message- From: Carter Young [mailto:ecyo...@grandecom.net] Sent: Friday, June 27, 2014 10:08 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Build issue This one gets you everytime. Thanks to Phil

Re: [WiX-users] unhandled exception in light

Googling gave me this: Locale ID: 2057: English - United Kingdom Additional Information 1: 5861 may be an invalid Unicode Character, See: http://www.fileformat.info/info/unicode/char/5861/index.htm Additional Information 3: d1d9 may be an invalid Unicode Character, See: http://www.fileformat.info

Re: [WiX-users] Build issue

That is not valid XML, wrap it into an CDATA block like this http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/block_install_on_os.html -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Build-issue-tp7595557p75

Re: [WiX-users] Build issue

This one gets you everytime. Thanks to Phil for catching this in mine :) Because you can't wrap this in a CDATA Tag, the compile throws the error because < is not valid XML, therefore use < for Less than or > for greaterthan Quoting Michael Ogilvie : > When I add: VersionNT <= 600 > > it c

Re: [WiX-users] Build issue

You need to use CDATA or entities. '<' is a legal XML character. You can either convert it to < or use CDATA to keep it from being interpreted as XML. -- John Merryweather Cooper Build & Install Engineer - ESA Jack Henry & Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x7910

[WiX-users] Build issue

When I add: VersionNT <= 600 it causes an error when I try to build the MSI DRIVER = 1 AND VersionNT <= 600 error CNDL0104 : Not a valid source file; detail: Name cannot begin with the '=' character, hexadecimal value 0x3D. Line 57, position 64. Thank you, Michael Ogilvie ---

[WiX-users] Wix toolset licence

Hi, In most open source software, the name of the licence and the name of the software must be written in the licence agreement file of the product where the open source software is used. Could anyone of you tell me if it is also the case for Wix Toolkit? I know that it is MS-RL licence type but

Re: [WiX-users] Code Signing

Found this method from another post, not sure if it is a best practice but works well for us. In the *.wixproj file add the following just before the closing tag: For signing an MSI: "C:\Program Files (x86)\Windows Kits\8.0\bin\x86\signtool.exe" sign /f "$(ProjectDir)yourFile.pfx" /p y

[WiX-users] Code Signing

Hello, I'm looking for some best practices to sign our application with a .pfx certificate. This is what I have: * DLL's made by us * DLL's signed by others * DLL's made by others but not signed * EXE's made by us Those are packed into a MSI (Msi.wixproj) ( have one .CAB-file defined as Embedded)

[WiX-users] unhandled exception in light

Hello all, We are seeing this same issue on windows 2012, using wix 3.8, same in 3.7. It's been going on for around 6 months and I'm out of ideas about what to do about it. I see a bug was raised for this but I can't find it on the bug tracking system (3310378). I've not managed to attach a deb