Only the description. You shouldn’t add length restrictions to the XSD. Pretty
much everything can have a preprocessor variable in it (that can be basically
as long as the user desires) that reduces down to the appropriate length.
Restrictions in XSD end up doing more harm than good.
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
From: Stephen Tunney [mailto:stephen.tun...@gmail.com]
Sent: Friday, May 23, 2014 12:26 PM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] Pyro exception on MsiInterop.MsiDatabaseCommit
Does it pick up on restrictions in the xsd or just the descriptions? My pull
request only has an xsd restriction on the attribute but I can easily
incorporate something into the Id description. I'll do that too :)
On 23 May 2014 14:47, Rob Mensching
<r...@firegiant.com<mailto:r...@firegiant.com>> wrote:
First, very cool that you jumped in and took on the fix. Thanks!
Second, in this case, you can just add documentation to the wix.xsd for the
attribute in question. The documentation in the wix.xsd is compiled and made
part of the WiX.chm and available on the http://wixtoolset.org/ as part of the
official build.
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
From: Tunney, Stephen
[mailto:stephen.tun...@nuance.com<mailto:stephen.tun...@nuance.com>]
Sent: Friday, May 23, 2014 7:44 AM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] Pyro exception on MsiInterop.MsiDatabaseCommit
Also, how would I go about updating the WiX 3.x Documentation on the website to
add this restriction for posterity? :)
Stephen Tunney
Nuance Communications, Inc.
Solutions Architect, Imaging Division
Waterloo, Ontario, Canada
stephen.tun...@nuance.com<mailto:stephen.tun...@nuance.com>
519-880-7463<tel:519-880-7463> Office
NUANCE.COM<http://NUANCE.COM>
The experience speaks for itself ™
From: Tunney, Stephen [mailto:stephen.tun...@nuance.com]
Sent: May-23-14 10:36 AM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] Pyro exception on MsiInterop.MsiDatabaseCommit
Bah, 28 characters. Sorry :@
Stephen Tunney
Nuance Communications, Inc.
Solutions Architect, Imaging Division
Waterloo, Ontario, Canada
stephen.tun...@nuance.com<mailto:stephen.tun...@nuance.com>
519-880-7463<tel:519-880-7463> Office
NUANCE.COM<http://NUANCE.COM>
The experience speaks for itself ™
From: Tunney, Stephen [mailto:stephen.tun...@nuance.com]
Sent: May-23-14 10:29 AM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] Pyro exception on MsiInterop.MsiDatabaseCommit
Based on my primitive test the max length is 38 of ASCII characters. That’s
quite the strange number. Is this a certain number of bytes like other fields
in the MSI tables have perhaps?
Stephen Tunney
Nuance Communications, Inc.
Solutions Architect, Imaging Division
Waterloo, Ontario, Canada
stephen.tun...@nuance.com<mailto:stephen.tun...@nuance.com>
519-880-7463<tel:519-880-7463> Office
NUANCE.COM<http://NUANCE.COM>
The experience speaks for itself ™
From: Tunney, Stephen [mailto:stephen.tun...@nuance.com]
Sent: May-23-14 9:52 AM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] Pyro exception on MsiInterop.MsiDatabaseCommit
Bob, do you know the maximum length off hand? I can’t seem to find anything on
the internets regarding this limitation.
Also, another question: Now that wix40 is in high-gear, do I need to create a
pull request for both repos in order to get a fix in there or will the WiX team
be doing a strategic merge of 3.x into 4.0 at set intervals?
Stephen Tunney
Nuance Communications, Inc.
Solutions Architect, Imaging Division
Waterloo, Ontario, Canada
stephen.tun...@nuance.com<mailto:stephen.tun...@nuance.com>
519-880-7463<tel:519-880-7463> Office
NUANCE.COM<http://NUANCE.COM>
The experience speaks for itself ™
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: May-23-14 12:09 AM
To: wix-devs@lists.sourceforge.net<mailto:wix-devs@lists.sourceforge.net>
Subject: Re: [WiX-devs] Pyro exception on MsiInterop.MsiDatabaseCommit
On 21-May-14 20:41, Tunney, Stephen wrote:
More details, here is the full exception ErrorInfo value:
"Internal MSI failure. Win32 error: 1627, MSI error: 2213, detail:
C:\\Users\\stephen_tunney\\AppData\\Local\\Temp\\vefiavqt\\Patch.msp, , "
Does anyone have any idea what I'm doing wrong? I really need some assistance
here please :(
Make the id shorter. There's an MSI limitation on substorage names.
--
sig://boB
http://joyofsetup.com/
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net<mailto:WiX-devs@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
