To build a localization I build an XML with the root being WixLocalization
now from looking at some examples will String
Id=ProgressTextPublishComponents for example replace the ProgressText Id
called PublishComponents ? Second, how do I make my WIX actually USE this
localization (making it
Are you using WiX 2.0 or WiX 3.0?
Anyway, one MSI can only contain one language. To support 3 languages you need
to create 3 MSIs. You can then convert 2 of them to MSTs to reduce the final
size of your deployment package. (Or maybe 1 MSI and 3 MSTs - I'm not even sure
of that.) You then use
Are you using WiX 2.0 or WiX 3.0?
I'm using Wix 2.0
Anyway, one MSI can only contain one language. To support 3 languages you
need to create 3 MSIs. You can then convert 2 of them to MSTs to reduce
the final size of your deployment package. (Or maybe 1 MSI and 3 MSTs -
I'm not even sure of
Igor,
I appreciate the time you're taking to try to explain this to me.
Just to be sure that we are talking about the same thing: you
want to put all languages in a single msi file. Right?
No, my understanding is that this is impossible.
1. You localized all your code.
Yes.
2. You
As long as you have defined all strings in your ui using localization
variables (like WixUI) then it shouldn't matter, AFAIK
On 5/3/07, Pseudonymic Wannabe [EMAIL PROTECTED] wrote:
I also forgot to add, I'm NOT using WixUI I built a new UI based on the
example from WixEdit, I doubt
I first tried using WiXEdit, but could never get it to work. (Maybe I
gave up too quickly.)
If you look at my tutorial you can see how to do it with SharpDevelop,
and using the WiX sample UI as starting point, but then modifying the UI
to be what you want. With everything localized.
Rennie
I didn't quite get your tutorial since it messes around with user-selection
and using $loc quite heavily. I thought if you create a WixLocalization
file and have say String Id=ButtonNextNeste/String inn it and you
loaded that file then a button with Text=[ButtonNext] would have Neste
as the
Don't really understand your first question, sorry.
Don't quite see in your tutorial how you specify which loc.wxs file to
use either.
Thanks for pointing that out - I'm trying to improve my tutorial. (I may
even format and upload the last page someday :-)
The localization file is specified
In WiX 2.0 you would use Text=$(loc.ButtonNext) to reference the
string you defined in your localization file.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Pseudonymic Wannabe
Sent: Thursday, May 03, 2007 5:38 AM
To: wix-users@lists.sourceforge.net
Not today. That's a pretty strange thing to do. To go modify some other file
to remove some attribute off of it. Usually, people just build up ACLs on
the files they own to make sure the right stuff is there.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Rob Mensching wrote:
Not today. That's a pretty strange thing to do. To go modify some
other file to remove some attribute off of it. Usually, people
just build up ACLs on the files they own to make sure the right stuff
is there.
Also with inheritance 'removing' might have no effect anyway
I downloaded/installed Wix 3.0.2813 and don't see tallow, as far as I can
tell I need it to put together a large Web Application Project distribution.
Thanks.
_
Exercise your brain! Try Flexicon.
Hi All,
We're using setupbld.exe to chain two MSIs together (the first one say A.msi
spec'ed with -mu, the second B.msi with -mus). This works fine, except we're
testing the scenario where the user might try and run the setup.exe more than
once.
B.msi has some code to detect and prevent
I have created a WIX installer that works perfectly on XP and it also
works, almost perfectly, on Vista.
The problem I'm having is that after the installation has completed
Vista puts up a message box that says ProductName installer has stopped
working. The software has been installed properly
[EMAIL PROTECTED] wrote:
I had originally copied the WixMondoUI fileset from wix 2.0 and
modified it to create my custom UI.
What effect does that have on your answer?
You can still use the copy embedded in WixUIExtension and add your own
overrides and new loc strings. But yes, the
Best practice is to avoid self-registration - Windows Installer cannot
repair what it does not know about.
WiX does not provide any tools to extract registration information from
EXEs, only DLLs. This is due to a limitation on the technique used. Some
people have reported success with RegCap.exe,
16 matches
Mail list logo