This probably happens because you are trying to build a culture other then
en-us.
Get WiX source code, go to folder \src\ext\SqlExtension\wixlib\ and get the
en-us.wxl language file. Make a copy of it, but translated to the culture
you are using, and include it in your project.
Joel Paula
Brian,
XmlConfig only allows for adding or deleting elements.
I understand this is more straightforward when you want to rollback.
How do you "edit" an XML file?
XmlFile seemed to be the thing to use, but it always throws the error "
ExecXmlFile: Found Wow64 API, but unable to link to
Wow64Di
Sorry, I was using my own code and didn't complete the example. Here is the
correction:
Joel
-Original Message-
From: Joel Paula (hotmail) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 5:11 PM
To: 'General discussion for Windows Installer XML toolset.'
Su
esve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20
0SP
Email Disclaimer
-----Original Message-
From: Joel Paula (hotmail) [mailto:
Hi,
I was stuck with the same error. I moved on to use XmlConfig instead.
I guess there really is a bug with XmlFile.
Anyway, those commands only add or delete nodes. I had to delete nodes and then
re-add them with the correct information.
Example using XmlConfig:
HTH
Joel
-Original Me
I had a problem this morning with XMLConfig. Somebody also had a similar
problem.
Here is the code to add a value to an element (not an attribute):
Hope it helps someone.
Joel
-
This SF.Net email is sponsored
Logan,
Thanks for the tip.
You can also use 7-zip. It does that for free.
It even has a special SFx for windows installation and you can configure the
dialogs messages (if needed).
But doesn't provide options for configuring icons and such.
-Original Message-
From: chaiguy1337 [mailto
I have an Xml file I need to put in another application file, write some xml
to it and run it with that 3rd party application.
Sequence of events:
1. Write Xml to file
2. Get the Directory/Folder where the 3rd party application is sitting from
win.ini
3. Copy Xml file to 3rd party app folder
4.
Correction to the GenerateBootstrapper elements, using properties:
-Original Message-
From: Joel Paula (hotmail) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 1:08 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] How
[WiX-users] How to for non english culture?
Joel, that's the vision for WiX v3.5. We just don't have the bootstrapper
right now.
-Original Message-
From: Joel Paula (hotmail) [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2008 16:18
To: wix-users@lists.sourceforge.net
Subj
y, October 20, 2008 11:58 PM
To: Joel Paula (hotmail)
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to for non english culture?
It's also worth noting that it's not awfully hard to write your own --
which has some advantages, in that you can customize it to your li
After 1 week of struggling with WiX, I am ready to give up. This is my last
attempt to save the time I have spent with it.
My project:
. Install a product that has a VB6 application and a .Net 2.0 application.
. Install all required run times (It Just Works style)
. Works for English (en)
12 matches
Mail list logo