Re: [WiX-users] Install Localisation

[Bob Arnson]

Rob Mensching wrote:
> For the guys in Microsoft that are big enough to have a gazillion languages, 
> I've seen the push towards multiple MSI packages.
>   

MUI/language pack MSI + language-neutral executable MSI. It also 
simplifies patching, since you're targeting one product for your code 
changes (more common than localizable patches).

-- 
sig://boB
http://joyofsetup.com/


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Rob Mensching]

For the guys in Microsoft that are big enough to have a gazillion languages, 
I've seen the push towards multiple MSI packages.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 02, 2008 09:14
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I would be interested in finding out how anyone else does this.

Most Microsoft applications seem to be shipped on one language per
install, I would prefer not to do that as it seems unnecessary and the
sales guys hate the idea of creating lots of different product CDs.

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 02 December 2008 17:01
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Torch has been written by guys that think mostly in terms of patching.
Changing a ProductCode in a patch would be bad, I think they forgot
about the case where torch is used standalone.  I'll follow up this
week.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 23:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I read that and at first it made sense but as it doesn't put it in
context I chose to ignore it! I can see it makes sense if the French
install should run side-by-side with German but if the only difference
is the install wizard UI and this is controlled via a transform not
separate MSI I would expect to see the same ProductCode. In fact when
you run torch if displays a warning if you are changing the ProductCode
advising against it, so someone agrees with me.

Neil

-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 02 December 2008 01:48
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Neil Sleightholm wrote:
> 2. Every time I run light it will create a new product code but I
don't
> want that, I want one product code and simply install with a different
> UI language. From what I have read this seems to be a valid approach.
>

The MSI SDK disagrees. In fact, it's unusually unambiguous [emphasis
mine]:

A localized product is considered a different product. For example, the
German and English versions of an application are considered two
different products and /must /have different product codes.

--
sig://boB
http://joyofsetup.com/


-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to a

Re: [WiX-users] Install Localisation

[Neil Sleightholm]

I would be interested in finding out how anyone else does this. 

Most Microsoft applications seem to be shipped on one language per
install, I would prefer not to do that as it seems unnecessary and the
sales guys hate the idea of creating lots of different product CDs.

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED] 
Sent: 02 December 2008 17:01
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Torch has been written by guys that think mostly in terms of patching.
Changing a ProductCode in a patch would be bad, I think they forgot
about the case where torch is used standalone.  I'll follow up this
week.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 23:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I read that and at first it made sense but as it doesn't put it in
context I chose to ignore it! I can see it makes sense if the French
install should run side-by-side with German but if the only difference
is the install wizard UI and this is controlled via a transform not
separate MSI I would expect to see the same ProductCode. In fact when
you run torch if displays a warning if you are changing the ProductCode
advising against it, so someone agrees with me.

Neil

-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 02 December 2008 01:48
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Neil Sleightholm wrote:
> 2. Every time I run light it will create a new product code but I
don't
> want that, I want one product code and simply install with a different
> UI language. From what I have read this seems to be a valid approach.
>

The MSI SDK disagrees. In fact, it's unusually unambiguous [emphasis
mine]:

A localized product is considered a different product. For example, the
German and English versions of an application are considered two
different products and /must /have different product codes.

--
sig://boB
http://joyofsetup.com/


-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Rob Mensching]

Torch has been written by guys that think mostly in terms of patching.  
Changing a ProductCode in a patch would be bad, I think they forgot about the 
case where torch is used standalone.  I'll follow up this week.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 23:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I read that and at first it made sense but as it doesn't put it in
context I chose to ignore it! I can see it makes sense if the French
install should run side-by-side with German but if the only difference
is the install wizard UI and this is controlled via a transform not
separate MSI I would expect to see the same ProductCode. In fact when
you run torch if displays a warning if you are changing the ProductCode
advising against it, so someone agrees with me.

Neil

-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 02 December 2008 01:48
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Neil Sleightholm wrote:
> 2. Every time I run light it will create a new product code but I
don't
> want that, I want one product code and simply install with a different
> UI language. From what I have read this seems to be a valid approach.
>

The MSI SDK disagrees. In fact, it's unusually unambiguous [emphasis
mine]:

A localized product is considered a different product. For example, the
German and English versions of an application are considered two
different products and /must /have different product codes.

--
sig://boB
http://joyofsetup.com/


-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Bob Arnson]

Neil Sleightholm wrote:
> I read that and at first it made sense but as it doesn't put it in
> context I chose to ignore it! 

A perilous choice with MSI. I understand and don't disagree with your 
choice.

-- 
sig://boB
http://joyofsetup.com/



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Neil Sleightholm]

I read that and at first it made sense but as it doesn't put it in
context I chose to ignore it! I can see it makes sense if the French
install should run side-by-side with German but if the only difference
is the install wizard UI and this is controlled via a transform not
separate MSI I would expect to see the same ProductCode. In fact when
you run torch if displays a warning if you are changing the ProductCode
advising against it, so someone agrees with me.

Neil

-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED] 
Sent: 02 December 2008 01:48
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Neil Sleightholm wrote:
> 2. Every time I run light it will create a new product code but I
don't
> want that, I want one product code and simply install with a different
> UI language. From what I have read this seems to be a valid approach.
>   

The MSI SDK disagrees. In fact, it's unusually unambiguous [emphasis
mine]:

A localized product is considered a different product. For example, the 
German and English versions of an application are considered two 
different products and /must /have different product codes.

-- 
sig://boB
http://joyofsetup.com/


-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Neil Sleightholm]

Good point (I don't care as we only do major upgrades - at the moment)
but this is a simple solution.

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED] 
Sent: 01 December 2008 22:43
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Most people that are attempting to do what you are doing, care about
their ProductCodes so they can tightly manage upgrades in the future.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 14:33
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I guess it is laziness on my part :-) I am just going to have to write
some code.

I just strikes me as a common requirement to generate a transform
without a different ProductCode - I guess that makes it a feature
request. May be it should be a torch change rather than light.

I'll look at that package code issue and see what I can find.

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 01 December 2008 22:08
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

2.  The PackageCode should be regenerated with every run of light.  If
not, that would be a bad bug.  There is no scope like you are asking
for.  IMHO, if you want to manage your ProductCode then you should
manage your ProductCode.  You could open a feature request if you want.

Nothing in you scenario is completely unexpected.  Generating transforms
is complete supported.  You'll need something to apply the transforms at
run time, presumably.

The bugs in the WiX toolset are being fixed, BTW.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 13:59
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

2. Is there any scope for making this optional or replacing
Product/@Id="*" on the first pass of light? The PackageCode is not
regenerated on every run of light, is this not the same?

I can't find any good documentation on Windows Installer localisation,
do you think I am doing the right thing to localise my install or is it
my approach that is floored.

Thanks

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 01 December 2008 20:12
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

1.  Don't know.

2.  If you use Product/@Id="*" then it always generates a new
ProductCode.  If you don't want that, don't use "*".

3.  No.  There are cases where you'll end up with a binary .wixout even
if you don't use -bf, especially around the use of CustomActions.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 10:34
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Having worked through a few bugs in light I am now back to looking at
this problem again. What I would like to do is create an MSI with a
separate transform (MST) for each language. So the process I intend to
use is:

1. Create wixout for my install using the -sloc parameter.
2. Link the wixout to create the English MSI.
3. For each language run light on the wixout to create a new translated
MSI or wixout.
4. Use torch to create an MST for each language from 3.

Until the next WiX release I am not able to try this but I can see a
couple of problems:

1. The documentation for torch says that if you use a wixout input file
it will only create a wixout (-xo set by default if -xi set). Is this
correct? If it is, how do you create an MST from a wixout?

2. Every time I run light it will create a new product code but I don't
want that, I want one product code and simply install with a different
UI language. From what I have read this seems to be a valid approach.
Can anyone suggest how I can do this?

3. I thought I could solve 2 but editing the wixout file and putting in
my own ProductCode so that it is not regenerated but it appears to start
with some binary data. I think that it is always binding the files into
wixout not just when -bf is used. Does this sound like a bug?

Thanks for your help

Neil

Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]



-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 06 November 2008 22:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

0.  *Every* MSI should have a different PackageCode.  Even two builds of
the same MSI.

1.  You *can* have different ProductCodes for all of your languages.
Depends on what your SxS story is.

2.  The most efficient way I've seen this done is:

a.  Link to ".wixout" files.  This will get you 

Re: [WiX-users] Install Localisation

[Bob Arnson]

Neil Sleightholm wrote:
> 2. Every time I run light it will create a new product code but I don't
> want that, I want one product code and simply install with a different
> UI language. From what I have read this seems to be a valid approach.
>   

The MSI SDK disagrees. In fact, it's unusually unambiguous [emphasis mine]:

A localized product is considered a different product. For example, the 
German and English versions of an application are considered two 
different products and /must /have different product codes.

-- 
sig://boB
http://joyofsetup.com/

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Rob Mensching]

Most people that are attempting to do what you are doing, care about their 
ProductCodes so they can tightly manage upgrades in the future.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 14:33
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I guess it is laziness on my part :-) I am just going to have to write
some code.

I just strikes me as a common requirement to generate a transform
without a different ProductCode - I guess that makes it a feature
request. May be it should be a torch change rather than light.

I'll look at that package code issue and see what I can find.

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 01 December 2008 22:08
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

2.  The PackageCode should be regenerated with every run of light.  If
not, that would be a bad bug.  There is no scope like you are asking
for.  IMHO, if you want to manage your ProductCode then you should
manage your ProductCode.  You could open a feature request if you want.

Nothing in you scenario is completely unexpected.  Generating transforms
is complete supported.  You'll need something to apply the transforms at
run time, presumably.

The bugs in the WiX toolset are being fixed, BTW.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 13:59
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

2. Is there any scope for making this optional or replacing
Product/@Id="*" on the first pass of light? The PackageCode is not
regenerated on every run of light, is this not the same?

I can't find any good documentation on Windows Installer localisation,
do you think I am doing the right thing to localise my install or is it
my approach that is floored.

Thanks

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 01 December 2008 20:12
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

1.  Don't know.

2.  If you use Product/@Id="*" then it always generates a new
ProductCode.  If you don't want that, don't use "*".

3.  No.  There are cases where you'll end up with a binary .wixout even
if you don't use -bf, especially around the use of CustomActions.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 10:34
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Having worked through a few bugs in light I am now back to looking at
this problem again. What I would like to do is create an MSI with a
separate transform (MST) for each language. So the process I intend to
use is:

1. Create wixout for my install using the -sloc parameter.
2. Link the wixout to create the English MSI.
3. For each language run light on the wixout to create a new translated
MSI or wixout.
4. Use torch to create an MST for each language from 3.

Until the next WiX release I am not able to try this but I can see a
couple of problems:

1. The documentation for torch says that if you use a wixout input file
it will only create a wixout (-xo set by default if -xi set). Is this
correct? If it is, how do you create an MST from a wixout?

2. Every time I run light it will create a new product code but I don't
want that, I want one product code and simply install with a different
UI language. From what I have read this seems to be a valid approach.
Can anyone suggest how I can do this?

3. I thought I could solve 2 but editing the wixout file and putting in
my own ProductCode so that it is not regenerated but it appears to start
with some binary data. I think that it is always binding the files into
wixout not just when -bf is used. Does this sound like a bug?

Thanks for your help

Neil

Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]



-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 06 November 2008 22:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

0.  *Every* MSI should have a different PackageCode.  Even two builds of
the same MSI.

1.  You *can* have different ProductCodes for all of your languages.
Depends on what your SxS story is.

2.  The most efficient way I've seen this done is:

a.  Link to ".wixout" files.  This will get you everything but the final
localized build.

b.  Use cab cache to minimize the number of cabinets rebuilt.  If you
are really careful with your Media elements this can lead to huge
savings.

c.  Link the ".wixout" file with each ".wxl" file in turn, to build the
final MSI files.

d.  Use torch to build t

Re: [WiX-users] Install Localisation

[Neil Sleightholm]

I guess it is laziness on my part :-) I am just going to have to write
some code.

I just strikes me as a common requirement to generate a transform
without a different ProductCode - I guess that makes it a feature
request. May be it should be a torch change rather than light.

I'll look at that package code issue and see what I can find.

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED] 
Sent: 01 December 2008 22:08
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

2.  The PackageCode should be regenerated with every run of light.  If
not, that would be a bad bug.  There is no scope like you are asking
for.  IMHO, if you want to manage your ProductCode then you should
manage your ProductCode.  You could open a feature request if you want.

Nothing in you scenario is completely unexpected.  Generating transforms
is complete supported.  You'll need something to apply the transforms at
run time, presumably.

The bugs in the WiX toolset are being fixed, BTW.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 13:59
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

2. Is there any scope for making this optional or replacing
Product/@Id="*" on the first pass of light? The PackageCode is not
regenerated on every run of light, is this not the same?

I can't find any good documentation on Windows Installer localisation,
do you think I am doing the right thing to localise my install or is it
my approach that is floored.

Thanks

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 01 December 2008 20:12
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

1.  Don't know.

2.  If you use Product/@Id="*" then it always generates a new
ProductCode.  If you don't want that, don't use "*".

3.  No.  There are cases where you'll end up with a binary .wixout even
if you don't use -bf, especially around the use of CustomActions.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 10:34
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Having worked through a few bugs in light I am now back to looking at
this problem again. What I would like to do is create an MSI with a
separate transform (MST) for each language. So the process I intend to
use is:

1. Create wixout for my install using the -sloc parameter.
2. Link the wixout to create the English MSI.
3. For each language run light on the wixout to create a new translated
MSI or wixout.
4. Use torch to create an MST for each language from 3.

Until the next WiX release I am not able to try this but I can see a
couple of problems:

1. The documentation for torch says that if you use a wixout input file
it will only create a wixout (-xo set by default if -xi set). Is this
correct? If it is, how do you create an MST from a wixout?

2. Every time I run light it will create a new product code but I don't
want that, I want one product code and simply install with a different
UI language. From what I have read this seems to be a valid approach.
Can anyone suggest how I can do this?

3. I thought I could solve 2 but editing the wixout file and putting in
my own ProductCode so that it is not regenerated but it appears to start
with some binary data. I think that it is always binding the files into
wixout not just when -bf is used. Does this sound like a bug?

Thanks for your help

Neil

Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]



-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 06 November 2008 22:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

0.  *Every* MSI should have a different PackageCode.  Even two builds of
the same MSI.

1.  You *can* have different ProductCodes for all of your languages.
Depends on what your SxS story is.

2.  The most efficient way I've seen this done is:

a.  Link to ".wixout" files.  This will get you everything but the final
localized build.

b.  Use cab cache to minimize the number of cabinets rebuilt.  If you
are really careful with your Media elements this can lead to huge
savings.

c.  Link the ".wixout" file with each ".wxl" file in turn, to build the
final MSI files.

d.  Use torch to build transforms from all of the MSIs.


There may be an optimization where you can build .wixouts with .wxl
files to create localized .wixouts and torch those .wixouts.  This will
not have the file table information correct so it may not work for you.
Also, Peter was talking about issues with torch and .wixouts but I don't
remember them right now.

It's be

Re: [WiX-users] Install Localisation

[Rob Mensching]

2.  The PackageCode should be regenerated with every run of light.  If not, 
that would be a bad bug.  There is no scope like you are asking for.  IMHO, if 
you want to manage your ProductCode then you should manage your ProductCode.  
You could open a feature request if you want.

Nothing in you scenario is completely unexpected.  Generating transforms is 
complete supported.  You'll need something to apply the transforms at run time, 
presumably.

The bugs in the WiX toolset are being fixed, BTW.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 13:59
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

2. Is there any scope for making this optional or replacing
Product/@Id="*" on the first pass of light? The PackageCode is not
regenerated on every run of light, is this not the same?

I can't find any good documentation on Windows Installer localisation,
do you think I am doing the right thing to localise my install or is it
my approach that is floored.

Thanks

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 01 December 2008 20:12
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

1.  Don't know.

2.  If you use Product/@Id="*" then it always generates a new
ProductCode.  If you don't want that, don't use "*".

3.  No.  There are cases where you'll end up with a binary .wixout even
if you don't use -bf, especially around the use of CustomActions.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 10:34
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Having worked through a few bugs in light I am now back to looking at
this problem again. What I would like to do is create an MSI with a
separate transform (MST) for each language. So the process I intend to
use is:

1. Create wixout for my install using the -sloc parameter.
2. Link the wixout to create the English MSI.
3. For each language run light on the wixout to create a new translated
MSI or wixout.
4. Use torch to create an MST for each language from 3.

Until the next WiX release I am not able to try this but I can see a
couple of problems:

1. The documentation for torch says that if you use a wixout input file
it will only create a wixout (-xo set by default if -xi set). Is this
correct? If it is, how do you create an MST from a wixout?

2. Every time I run light it will create a new product code but I don't
want that, I want one product code and simply install with a different
UI language. From what I have read this seems to be a valid approach.
Can anyone suggest how I can do this?

3. I thought I could solve 2 but editing the wixout file and putting in
my own ProductCode so that it is not regenerated but it appears to start
with some binary data. I think that it is always binding the files into
wixout not just when -bf is used. Does this sound like a bug?

Thanks for your help

Neil

Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]



-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 06 November 2008 22:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

0.  *Every* MSI should have a different PackageCode.  Even two builds of
the same MSI.

1.  You *can* have different ProductCodes for all of your languages.
Depends on what your SxS story is.

2.  The most efficient way I've seen this done is:

a.  Link to ".wixout" files.  This will get you everything but the final
localized build.

b.  Use cab cache to minimize the number of cabinets rebuilt.  If you
are really careful with your Media elements this can lead to huge
savings.

c.  Link the ".wixout" file with each ".wxl" file in turn, to build the
final MSI files.

d.  Use torch to build transforms from all of the MSIs.


There may be an optimization where you can build .wixouts with .wxl
files to create localized .wixouts and torch those .wixouts.  This will
not have the file table information correct so it may not work for you.
Also, Peter was talking about issues with torch and .wixouts but I don't
remember them right now.

It's been a long while since I did all the above so YMMV and please feel
free to correct me where I'm wrong.  It might be a bug.  


-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 14:19
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Install Localisation

I am looking for advise in localising installs.



I need to deploy an application in several languages and I thought I had
the solution, what I did was this:

1.   Set the CAB file as not embedded as the f

Re: [WiX-users] Install Localisation

[Neil Sleightholm]

2. Is there any scope for making this optional or replacing
Product/@Id="*" on the first pass of light? The PackageCode is not
regenerated on every run of light, is this not the same?

I can't find any good documentation on Windows Installer localisation,
do you think I am doing the right thing to localise my install or is it
my approach that is floored.

Thanks 

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED] 
Sent: 01 December 2008 20:12
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

1.  Don't know.

2.  If you use Product/@Id="*" then it always generates a new
ProductCode.  If you don't want that, don't use "*".

3.  No.  There are cases where you'll end up with a binary .wixout even
if you don't use -bf, especially around the use of CustomActions.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 10:34
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Having worked through a few bugs in light I am now back to looking at
this problem again. What I would like to do is create an MSI with a
separate transform (MST) for each language. So the process I intend to
use is:

1. Create wixout for my install using the -sloc parameter.
2. Link the wixout to create the English MSI.
3. For each language run light on the wixout to create a new translated
MSI or wixout.
4. Use torch to create an MST for each language from 3.

Until the next WiX release I am not able to try this but I can see a
couple of problems:

1. The documentation for torch says that if you use a wixout input file
it will only create a wixout (-xo set by default if -xi set). Is this
correct? If it is, how do you create an MST from a wixout?

2. Every time I run light it will create a new product code but I don't
want that, I want one product code and simply install with a different
UI language. From what I have read this seems to be a valid approach.
Can anyone suggest how I can do this?

3. I thought I could solve 2 but editing the wixout file and putting in
my own ProductCode so that it is not regenerated but it appears to start
with some binary data. I think that it is always binding the files into
wixout not just when -bf is used. Does this sound like a bug?

Thanks for your help

Neil

Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]



-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 06 November 2008 22:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

0.  *Every* MSI should have a different PackageCode.  Even two builds of
the same MSI.

1.  You *can* have different ProductCodes for all of your languages.
Depends on what your SxS story is.

2.  The most efficient way I've seen this done is:

a.  Link to ".wixout" files.  This will get you everything but the final
localized build.

b.  Use cab cache to minimize the number of cabinets rebuilt.  If you
are really careful with your Media elements this can lead to huge
savings.

c.  Link the ".wixout" file with each ".wxl" file in turn, to build the
final MSI files.

d.  Use torch to build transforms from all of the MSIs.


There may be an optimization where you can build .wixouts with .wxl
files to create localized .wixouts and torch those .wixouts.  This will
not have the file table information correct so it may not work for you.
Also, Peter was talking about issues with torch and .wixouts but I don't
remember them right now.

It's been a long while since I did all the above so YMMV and please feel
free to correct me where I'm wrong.  It might be a bug.  


-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 14:19
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Install Localisation

I am looking for advise in localising installs.



I need to deploy an application in several languages and I thought I had
the solution, what I did was this:

1.   Set the CAB file as not embedded as the files are the same for
all languages.

2.   Run candle for wxs files

3.   Run light against the wixobj files but specifying a different
culture each time I ran it

4.   This creates an msi for each language with an external CAB
file.



This works but I have just noticed a major problem, each time I run
light it generates a new product and package code (I use the Guid="*"
syntax for them). So this means that each language has a different
product/package code and this is clear not really correct.



Can anyone suggest a better method for doing this? Ideally I would like
to generate one msi and then run some command to generate a tra

Re: [WiX-users] Install Localisation

[Rob Mensching]

1.  Don't know.

2.  If you use Product/@Id="*" then it always generates a new ProductCode.  If 
you don't want that, don't use "*".

3.  No.  There are cases where you'll end up with a binary .wixout even if you 
don't use -bf, especially around the use of CustomActions.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 10:34
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Having worked through a few bugs in light I am now back to looking at
this problem again. What I would like to do is create an MSI with a
separate transform (MST) for each language. So the process I intend to
use is:

1. Create wixout for my install using the -sloc parameter.
2. Link the wixout to create the English MSI.
3. For each language run light on the wixout to create a new translated
MSI or wixout.
4. Use torch to create an MST for each language from 3.

Until the next WiX release I am not able to try this but I can see a
couple of problems:

1. The documentation for torch says that if you use a wixout input file
it will only create a wixout (-xo set by default if -xi set). Is this
correct? If it is, how do you create an MST from a wixout?

2. Every time I run light it will create a new product code but I don't
want that, I want one product code and simply install with a different
UI language. From what I have read this seems to be a valid approach.
Can anyone suggest how I can do this?

3. I thought I could solve 2 but editing the wixout file and putting in
my own ProductCode so that it is not regenerated but it appears to start
with some binary data. I think that it is always binding the files into
wixout not just when -bf is used. Does this sound like a bug?

Thanks for your help

Neil

Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]



-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 06 November 2008 22:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

0.  *Every* MSI should have a different PackageCode.  Even two builds of
the same MSI.

1.  You *can* have different ProductCodes for all of your languages.
Depends on what your SxS story is.

2.  The most efficient way I've seen this done is:

a.  Link to ".wixout" files.  This will get you everything but the final
localized build.

b.  Use cab cache to minimize the number of cabinets rebuilt.  If you
are really careful with your Media elements this can lead to huge
savings.

c.  Link the ".wixout" file with each ".wxl" file in turn, to build the
final MSI files.

d.  Use torch to build transforms from all of the MSIs.


There may be an optimization where you can build .wixouts with .wxl
files to create localized .wixouts and torch those .wixouts.  This will
not have the file table information correct so it may not work for you.
Also, Peter was talking about issues with torch and .wixouts but I don't
remember them right now.

It's been a long while since I did all the above so YMMV and please feel
free to correct me where I'm wrong.  It might be a bug.  


-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 14:19
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Install Localisation

I am looking for advise in localising installs.



I need to deploy an application in several languages and I thought I had
the solution, what I did was this:

1.   Set the CAB file as not embedded as the files are the same for
all languages.

2.   Run candle for wxs files

3.   Run light against the wixobj files but specifying a different
culture each time I ran it

4.   This creates an msi for each language with an external CAB
file.



This works but I have just noticed a major problem, each time I run
light it generates a new product and package code (I use the Guid="*"
syntax for them). So this means that each language has a different
product/package code and this is clear not really correct.



Can anyone suggest a better method for doing this? Ideally I would like
to generate one msi and then run some command to generate a transform
for each language.



Thanks



Neil



Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/list

Re: [WiX-users] Install Localisation

[Neil Sleightholm]

Having worked through a few bugs in light I am now back to looking at
this problem again. What I would like to do is create an MSI with a
separate transform (MST) for each language. So the process I intend to
use is:

1. Create wixout for my install using the -sloc parameter.
2. Link the wixout to create the English MSI.
3. For each language run light on the wixout to create a new translated
MSI or wixout.
4. Use torch to create an MST for each language from 3.

Until the next WiX release I am not able to try this but I can see a
couple of problems:

1. The documentation for torch says that if you use a wixout input file
it will only create a wixout (-xo set by default if -xi set). Is this
correct? If it is, how do you create an MST from a wixout?

2. Every time I run light it will create a new product code but I don't
want that, I want one product code and simply install with a different
UI language. From what I have read this seems to be a valid approach.
Can anyone suggest how I can do this?

3. I thought I could solve 2 but editing the wixout file and putting in
my own ProductCode so that it is not regenerated but it appears to start
with some binary data. I think that it is always binding the files into
wixout not just when -bf is used. Does this sound like a bug?

Thanks for your help

Neil

Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]



-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED] 
Sent: 06 November 2008 22:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

0.  *Every* MSI should have a different PackageCode.  Even two builds of
the same MSI.

1.  You *can* have different ProductCodes for all of your languages.
Depends on what your SxS story is.

2.  The most efficient way I've seen this done is:

a.  Link to ".wixout" files.  This will get you everything but the final
localized build.

b.  Use cab cache to minimize the number of cabinets rebuilt.  If you
are really careful with your Media elements this can lead to huge
savings.

c.  Link the ".wixout" file with each ".wxl" file in turn, to build the
final MSI files.

d.  Use torch to build transforms from all of the MSIs.


There may be an optimization where you can build .wixouts with .wxl
files to create localized .wixouts and torch those .wixouts.  This will
not have the file table information correct so it may not work for you.
Also, Peter was talking about issues with torch and .wixouts but I don't
remember them right now.

It's been a long while since I did all the above so YMMV and please feel
free to correct me where I'm wrong.  It might be a bug.  


-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 14:19
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Install Localisation

I am looking for advise in localising installs.



I need to deploy an application in several languages and I thought I had
the solution, what I did was this:

1.   Set the CAB file as not embedded as the files are the same for
all languages.

2.   Run candle for wxs files

3.   Run light against the wixobj files but specifying a different
culture each time I ran it

4.   This creates an msi for each language with an external CAB
file.



This works but I have just noticed a major problem, each time I run
light it generates a new product and package code (I use the Guid="*"
syntax for them). So this means that each language has a different
product/package code and this is clear not really correct.



Can anyone suggest a better method for doing this? Ideally I would like
to generate one msi and then run some command to generate a transform
for each language.



Thanks



Neil



Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/l

Re: [WiX-users] Install Localisation

[Neil Sleightholm]

I'll update the bug report to include this.

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED] 
Sent: 18 November 2008 16:02
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

That's the bug.  I bet this is a regression from trying to get all those
other .wxl bugs fixed in .wixlibs that we addressed a couple months ago.


-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2008 23:36
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

The problem is that if I don't supply -loc then light fails to resolve
any of my localisation variables and generates these errors:
Product.wxs(15) : error LGHT0102 : The localization variable
!(loc.ProductLanguage) is unknown.  Please ensure the variable is
defined.

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 17 November 2008 23:19
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I'm sorry if I asked this already but what happens if you don't specify
a -loc file on the first linking?  The command line you provided in the
bug has light behaving the way I would expect.  If you provide a .wxl
file then it will replace as many of the variables as it can in the
.wixout.  Subsequent bindings can only fill in remaining variables.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2008 12:16
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I seems to be that whatever I try the wixout file is localised and
re-binding leaves it as US English. I'll raise a bug report for this.

Neil

-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 15 November 2008 22:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Neil Sleightholm wrote:
> I have tried -bf but it doesn't solve the problem, the localisation is
> applied to the wixout when you first create it and no further
> localisation is applied by subsequent re-light commands.
>

Sorry, I meant to say that if you didn't use -bf, the binding process
would be skipped and, I thought, the localization.

> It also doesn't solve the problem that on each call to light a new
> ProductId is generated.
>

Same thing -- binding is what generates the product code, so I'd expect
generating a .wixout to leave it "*" so you can re-link (and bind).

--
sig://boB
http://joyofsetup.com/




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Mobli

Re: [WiX-users] Install Localisation

[Rob Mensching]

That's the bug.  I bet this is a regression from trying to get all those other 
.wxl bugs fixed in .wixlibs that we addressed a couple months ago.  

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2008 23:36
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

The problem is that if I don't supply -loc then light fails to resolve
any of my localisation variables and generates these errors:
Product.wxs(15) : error LGHT0102 : The localization variable
!(loc.ProductLanguage) is unknown.  Please ensure the variable is
defined.

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 17 November 2008 23:19
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I'm sorry if I asked this already but what happens if you don't specify
a -loc file on the first linking?  The command line you provided in the
bug has light behaving the way I would expect.  If you provide a .wxl
file then it will replace as many of the variables as it can in the
.wixout.  Subsequent bindings can only fill in remaining variables.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2008 12:16
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I seems to be that whatever I try the wixout file is localised and
re-binding leaves it as US English. I'll raise a bug report for this.

Neil

-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 15 November 2008 22:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Neil Sleightholm wrote:
> I have tried -bf but it doesn't solve the problem, the localisation is
> applied to the wixout when you first create it and no further
> localisation is applied by subsequent re-light commands.
>

Sorry, I meant to say that if you didn't use -bf, the binding process
would be skipped and, I thought, the localization.

> It also doesn't solve the problem that on each call to light a new
> ProductId is generated.
>

Same thing -- binding is what generates the product code, so I'd expect
generating a .wixout to leave it "*" so you can re-link (and bind).

--
sig://boB
http://joyofsetup.com/




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url

Re: [WiX-users] Install Localisation

[Neil Sleightholm]

The problem is that if I don't supply -loc then light fails to resolve
any of my localisation variables and generates these errors:
Product.wxs(15) : error LGHT0102 : The localization variable
!(loc.ProductLanguage) is unknown.  Please ensure the variable is
defined.

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED] 
Sent: 17 November 2008 23:19
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I'm sorry if I asked this already but what happens if you don't specify
a -loc file on the first linking?  The command line you provided in the
bug has light behaving the way I would expect.  If you provide a .wxl
file then it will replace as many of the variables as it can in the
.wixout.  Subsequent bindings can only fill in remaining variables.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2008 12:16
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I seems to be that whatever I try the wixout file is localised and
re-binding leaves it as US English. I'll raise a bug report for this.

Neil

-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 15 November 2008 22:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Neil Sleightholm wrote:
> I have tried -bf but it doesn't solve the problem, the localisation is
> applied to the wixout when you first create it and no further
> localisation is applied by subsequent re-light commands.
>

Sorry, I meant to say that if you didn't use -bf, the binding process
would be skipped and, I thought, the localization.

> It also doesn't solve the problem that on each call to light a new
> ProductId is generated.
>

Same thing -- binding is what generates the product code, so I'd expect
generating a .wixout to leave it "*" so you can re-link (and bind).

--
sig://boB
http://joyofsetup.com/




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Rob Mensching]

I'm sorry if I asked this already but what happens if you don't specify a -loc 
file on the first linking?  The command line you provided in the bug has light 
behaving the way I would expect.  If you provide a .wxl file then it will 
replace as many of the variables as it can in the .wixout.  Subsequent bindings 
can only fill in remaining variables.

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2008 12:16
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I seems to be that whatever I try the wixout file is localised and
re-binding leaves it as US English. I'll raise a bug report for this.

Neil

-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 15 November 2008 22:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Neil Sleightholm wrote:
> I have tried -bf but it doesn't solve the problem, the localisation is
> applied to the wixout when you first create it and no further
> localisation is applied by subsequent re-light commands.
>

Sorry, I meant to say that if you didn't use -bf, the binding process
would be skipped and, I thought, the localization.

> It also doesn't solve the problem that on each call to light a new
> ProductId is generated.
>

Same thing -- binding is what generates the product code, so I'd expect
generating a .wixout to leave it "*" so you can re-link (and bind).

--
sig://boB
http://joyofsetup.com/




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Neil Sleightholm]

I seems to be that whatever I try the wixout file is localised and
re-binding leaves it as US English. I'll raise a bug report for this.

Neil

-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED] 
Sent: 15 November 2008 22:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Neil Sleightholm wrote:
> I have tried -bf but it doesn't solve the problem, the localisation is
> applied to the wixout when you first create it and no further
> localisation is applied by subsequent re-light commands.
>   

Sorry, I meant to say that if you didn't use -bf, the binding process 
would be skipped and, I thought, the localization.

> It also doesn't solve the problem that on each call to light a new
> ProductId is generated.
>   

Same thing -- binding is what generates the product code, so I'd expect 
generating a .wixout to leave it "*" so you can re-link (and bind).

-- 
sig://boB
http://joyofsetup.com/




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Bob Arnson]

Neil Sleightholm wrote:
> I have tried -bf but it doesn't solve the problem, the localisation is
> applied to the wixout when you first create it and no further
> localisation is applied by subsequent re-light commands.
>   

Sorry, I meant to say that if you didn't use -bf, the binding process 
would be skipped and, I thought, the localization.

> It also doesn't solve the problem that on each call to light a new
> ProductId is generated.
>   

Same thing -- binding is what generates the product code, so I'd expect 
generating a .wixout to leave it "*" so you can re-link (and bind).

-- 
sig://boB
http://joyofsetup.com/



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Neil Sleightholm]

I have tried -bf but it doesn't solve the problem, the localisation is
applied to the wixout when you first create it and no further
localisation is applied by subsequent re-light commands.

It also doesn't solve the problem that on each call to light a new
ProductId is generated.

Neil

-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED] 
Sent: 12 November 2008 18:52
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

Neil Sleightholm wrote:
> No, should I?
>   

If you use -xo without -bf, you should be able to build a .wixout 
without needing the files. Then re-light to build the .msi with 
localization.

-- 
sig://boB
http://joyofsetup.com/




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Bob Arnson]

Neil Sleightholm wrote:
> No, should I?
>   

If you use -xo without -bf, you should be able to build a .wixout 
without needing the files. Then re-light to build the .msi with 
localization.

-- 
sig://boB
http://joyofsetup.com/



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Neil Sleightholm]

No, should I?
 
Neil
 
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 
 



From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Wed 12/11/2008 05:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation



Neil Sleightholm wrote:
> I am not sure how I could do that, for my own code it won't link if the files 
> are missing and for the built-in localisation I am not sure how I can exclude 
> it.
>  

Are you using the -bf switch to build your .wixout?

--
sig://boB
http://joyofsetup.com/



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Bob Arnson]

Neil Sleightholm wrote:
> I am not sure how I could do that, for my own code it won't link if the files 
> are missing and for the built-in localisation I am not sure how I can exclude 
> it.
>   

Are you using the -bf switch to build your .wixout?

-- 
sig://boB
http://joyofsetup.com/



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Neil Sleightholm]

I am not sure how I could do that, for my own code it won't link if the files 
are missing and for the built-in localisation I am not sure how I can exclude 
it.
 
Neil
 
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 
 



From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Sun 09/11/2008 22:47
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation



Does the .wixout have the localization if you do not provide the .wxl files?

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 09, 2008 14:37
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I have tried option 2 but am having problems. It seems that when you
link to a wixout it includes the localisation details, so step 2c only
ever builds the same localisation as the file created by the initial
link. In addition the productid is changed every time you run light
against the wixout file.

Is this what you would expect?

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 06 November 2008 22:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

0.  *Every* MSI should have a different PackageCode.  Even two builds of
the same MSI.

1.  You *can* have different ProductCodes for all of your languages.
Depends on what your SxS story is.

2.  The most efficient way I've seen this done is:

a.  Link to ".wixout" files.  This will get you everything but the final
localized build.

b.  Use cab cache to minimize the number of cabinets rebuilt.  If you
are really careful with your Media elements this can lead to huge
savings.

c.  Link the ".wixout" file with each ".wxl" file in turn, to build the
final MSI files.

d.  Use torch to build transforms from all of the MSIs.


There may be an optimization where you can build .wixouts with .wxl
files to create localized .wixouts and torch those .wixouts.  This will
not have the file table information correct so it may not work for you.
Also, Peter was talking about issues with torch and .wixouts but I don't
remember them right now.

It's been a long while since I did all the above so YMMV and please feel
free to correct me where I'm wrong.  It might be a bug.  


-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 14:19
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Install Localisation

I am looking for advise in localising installs.



I need to deploy an application in several languages and I thought I had
the solution, what I did was this:

1.   Set the CAB file as not embedded as the files are the same for
all languages.

2.   Run candle for wxs files

3.   Run light against the wixobj files but specifying a different
culture each time I ran it

4.   This creates an msi for each language with an external CAB
file.



This works but I have just noticed a major problem, each time I run
light it generates a new product and package code (I use the Guid="*"
syntax for them). So this means that each language has a different
product/package code and this is clear not really correct.



Can anyone suggest a better method for doing this? Ideally I would like
to generate one msi and then run some command to generate a transform
for each language.



Thanks



Neil



Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Gr

Re: [WiX-users] Install Localisation

[Rob Mensching]

Does the .wixout have the localization if you do not provide the .wxl files?

-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 09, 2008 14:37
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

I have tried option 2 but am having problems. It seems that when you
link to a wixout it includes the localisation details, so step 2c only
ever builds the same localisation as the file created by the initial
link. In addition the productid is changed every time you run light
against the wixout file.

Is this what you would expect?

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 06 November 2008 22:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

0.  *Every* MSI should have a different PackageCode.  Even two builds of
the same MSI.

1.  You *can* have different ProductCodes for all of your languages.
Depends on what your SxS story is.

2.  The most efficient way I've seen this done is:

a.  Link to ".wixout" files.  This will get you everything but the final
localized build.

b.  Use cab cache to minimize the number of cabinets rebuilt.  If you
are really careful with your Media elements this can lead to huge
savings.

c.  Link the ".wixout" file with each ".wxl" file in turn, to build the
final MSI files.

d.  Use torch to build transforms from all of the MSIs.


There may be an optimization where you can build .wixouts with .wxl
files to create localized .wixouts and torch those .wixouts.  This will
not have the file table information correct so it may not work for you.
Also, Peter was talking about issues with torch and .wixouts but I don't
remember them right now.

It's been a long while since I did all the above so YMMV and please feel
free to correct me where I'm wrong.  It might be a bug.  


-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 14:19
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Install Localisation

I am looking for advise in localising installs.



I need to deploy an application in several languages and I thought I had
the solution, what I did was this:

1.   Set the CAB file as not embedded as the files are the same for
all languages.

2.   Run candle for wxs files

3.   Run light against the wixobj files but specifying a different
culture each time I ran it

4.   This creates an msi for each language with an external CAB
file.



This works but I have just noticed a major problem, each time I run
light it generates a new product and package code (I use the Guid="*"
syntax for them). So this means that each language has a different
product/package code and this is clear not really correct.



Can anyone suggest a better method for doing this? Ideally I would like
to generate one msi and then run some command to generate a transform
for each language.



Thanks



Neil



Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based app

Re: [WiX-users] Install Localisation

[Neil Sleightholm]

I have tried option 2 but am having problems. It seems that when you
link to a wixout it includes the localisation details, so step 2c only
ever builds the same localisation as the file created by the initial
link. In addition the productid is changed every time you run light
against the wixout file.

Is this what you would expect?

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED] 
Sent: 06 November 2008 22:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

0.  *Every* MSI should have a different PackageCode.  Even two builds of
the same MSI.

1.  You *can* have different ProductCodes for all of your languages.
Depends on what your SxS story is.

2.  The most efficient way I've seen this done is:

a.  Link to ".wixout" files.  This will get you everything but the final
localized build.

b.  Use cab cache to minimize the number of cabinets rebuilt.  If you
are really careful with your Media elements this can lead to huge
savings.

c.  Link the ".wixout" file with each ".wxl" file in turn, to build the
final MSI files.

d.  Use torch to build transforms from all of the MSIs.


There may be an optimization where you can build .wixouts with .wxl
files to create localized .wixouts and torch those .wixouts.  This will
not have the file table information correct so it may not work for you.
Also, Peter was talking about issues with torch and .wixouts but I don't
remember them right now.

It's been a long while since I did all the above so YMMV and please feel
free to correct me where I'm wrong.  It might be a bug.  


-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 14:19
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Install Localisation

I am looking for advise in localising installs.



I need to deploy an application in several languages and I thought I had
the solution, what I did was this:

1.   Set the CAB file as not embedded as the files are the same for
all languages.

2.   Run candle for wxs files

3.   Run light against the wixobj files but specifying a different
culture each time I ran it

4.   This creates an msi for each language with an external CAB
file.



This works but I have just noticed a major problem, each time I run
light it generates a new product and package code (I use the Guid="*"
syntax for them). So this means that each language has a different
product/package code and this is clear not really correct.



Can anyone suggest a better method for doing this? Ideally I would like
to generate one msi and then run some command to generate a transform
for each language.



Thanks



Neil



Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Neil Sleightholm]

0/1. So my approach may be valid.

2. I'll give this a try.

It was torch that highlighted the issue to me. I was trying a new
bootstrapper that handles the different languages as transforms and I
thought I could generate them from my MSI's. When I ran torch to
generate the MST is raised a warning to say the product ids where
different.

I may be wrong but I think the bits of torch that I would need to use
aren't implemented, I saw a blog from Derek C the implied they were
future developments and I can't see anything in the help to suggest
otherwise.

Thanks

Neil

-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED] 
Sent: 06 November 2008 22:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation

0.  *Every* MSI should have a different PackageCode.  Even two builds of
the same MSI.

1.  You *can* have different ProductCodes for all of your languages.
Depends on what your SxS story is.

2.  The most efficient way I've seen this done is:

a.  Link to ".wixout" files.  This will get you everything but the final
localized build.

b.  Use cab cache to minimize the number of cabinets rebuilt.  If you
are really careful with your Media elements this can lead to huge
savings.

c.  Link the ".wixout" file with each ".wxl" file in turn, to build the
final MSI files.

d.  Use torch to build transforms from all of the MSIs.


There may be an optimization where you can build .wixouts with .wxl
files to create localized .wixouts and torch those .wixouts.  This will
not have the file table information correct so it may not work for you.
Also, Peter was talking about issues with torch and .wixouts but I don't
remember them right now.

It's been a long while since I did all the above so YMMV and please feel
free to correct me where I'm wrong.  It might be a bug.  


-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 14:19
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Install Localisation

I am looking for advise in localising installs.



I need to deploy an application in several languages and I thought I had
the solution, what I did was this:

1.   Set the CAB file as not embedded as the files are the same for
all languages.

2.   Run candle for wxs files

3.   Run light against the wixobj files but specifying a different
culture each time I ran it

4.   This creates an msi for each language with an external CAB
file.



This works but I have just noticed a major problem, each time I run
light it generates a new product and package code (I use the Guid="*"
syntax for them). So this means that each language has a different
product/package code and this is clear not really correct.



Can anyone suggest a better method for doing this? Ideally I would like
to generate one msi and then run some command to generate a transform
for each language.



Thanks



Neil



Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Localisation

[Rob Mensching]

0.  *Every* MSI should have a different PackageCode.  Even two builds of the 
same MSI.

1.  You *can* have different ProductCodes for all of your languages.  Depends 
on what your SxS story is.

2.  The most efficient way I've seen this done is:

a.  Link to ".wixout" files.  This will get you everything but the final 
localized build.

b.  Use cab cache to minimize the number of cabinets rebuilt.  If you are 
really careful with your Media elements this can lead to huge savings.

c.  Link the ".wixout" file with each ".wxl" file in turn, to build the final 
MSI files.

d.  Use torch to build transforms from all of the MSIs.


There may be an optimization where you can build .wixouts with .wxl files to 
create localized .wixouts and torch those .wixouts.  This will not have the 
file table information correct so it may not work for you.  Also, Peter was 
talking about issues with torch and .wixouts but I don't remember them right 
now.

It's been a long while since I did all the above so YMMV and please feel free 
to correct me where I'm wrong.  It might be a bug.  


-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 14:19
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Install Localisation

I am looking for advise in localising installs.



I need to deploy an application in several languages and I thought I had
the solution, what I did was this:

1.   Set the CAB file as not embedded as the files are the same for
all languages.

2.   Run candle for wxs files

3.   Run light against the wixobj files but specifying a different
culture each time I ran it

4.   This creates an msi for each language with an external CAB
file.



This works but I have just noticed a major problem, each time I run
light it generates a new product and package code (I use the Guid="*"
syntax for them). So this means that each language has a different
product/package code and this is clear not really correct.



Can anyone suggest a better method for doing this? Ideally I would like
to generate one msi and then run some command to generate a transform
for each language.



Thanks



Neil



Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] 



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users