subject:"\[WiX\-users\] Adding language transform .mst's to Burn Bundle Chain\?"

When I added the WixExtendedBootstraperApplication to my Wix 3.7.1224
installation, I downloaded the zip package from:

 http://wixextba.codeplex.com/releases/view/105895

And I put the one DLL in that package into my Wix Toolset 3.7.1224\bin
folder.  

At a later point I did what I described in another post where I created a
\Development\Tools\Wix 3.7.1224\bin folder and simply copied all of the
files from the \Wix toolset 3.7.1224\bin to that location,
which allows me to check the tools into svn so they can be used on another
build box.  At this later point I also modified the WIX environment variable
to point at my tools folder rather than my  folder.

But no, when I added the extended BA to the project I did not add anything
else to get it to work.

I later switched to Wix 3.8 (and have been switching back and forth).



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7588209.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

Okay, when I installed the latest WiX 3.8 and Updated my project files to use
3.8 the build correctly built in the UI so that on German the UI/EULA is
German, on French it is French and on English and unsupported languages it
shows English.

So yes 3.8 has the fixes in it. So my version of 3.7 has an issue and
therefore have to wonder about that. When you update your 3.7 with the
WixBalExtensionExt.dll file was this the only file that you copied into your
WiX 3.7\bin folder and rename it to WixBalExtension.dll or did you have to
update any other files?




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7588201.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

Well, I am sorry to hear that it is not working for you. Since I can build
it with 3.7 and it works, I think I would try to use ProcessMon or WinDbg to
figure out what the issue is, focusing only on the German Wix 3.7 exe which
I complied for you and your compilation of the same thing. Originally I
thought that WiX 3.8 was needed, but I have proven that it works with 3.7.

Prior to installing Wix 3.8 I created a folder in my svn tree for the 3.7
binaries, and after installing Wix 3.8 a similar folder in my svn tree for
the WiX 3.8 binaries. Then I created a batch file that calls setx to set
the environment variable WIX to the path to the 3.7 binaries.

The WiX Toolset 3.8 setup creates a system wide WIX variable, and when I
want to switch to 3.7 my batch file creates a user environment variable of
the same name. To switch back to 3.8 I delete the user WIX variable. I
also close VS2010 prior to changing the WIX variable or deleting it. Since
I never change the system variable created by the WiX Toolset 3.8 setup it
still exists when I am building to 3.8.

In this way I can switch back and forth and test either environment. I
would use ProcessMon or WinDbg to figure out why your results are different
than the exe that I sent you, which tests showed worked. I would focus on
the difference between the EXE that I compiled which does display both a
German strings and German EULA and your build of this same project in Wix
3.7 which you report does not display by watching each under ProcessMon.

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7588197.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

Okay after getting your install to build I test and it will still not show
German or French licenses on German and French systems. This is still
building with WiX 3.7 and having the updated WiXBalExtentionExt.dll file
into my WiX 3.7 bin folder.

So just having no luck what so ever.

I'll look at installing Wix 3.8 and giving that a try. 



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7588193.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

After doing this experiment with your code and demonstrating that
automatically detecting languages works using WiX 3.7, even without
specifically using the WiXExtenededBootstraperApplication, I switched my
main project (seven languages) back to Wix 3.7.  I did limited testing on my
Windows 8 test box successfully and then I handed the package of to my QA
group which is testing it on a larger variation of OS and languages.  So far
no problems reported, but I am not sure how far they have proceeded with
that testing.  (One tester reports that it (build with 3.7) worked fine on
XP Japanese system, detecting the language, installing and properly
configuring the applications.) 



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7588184.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

Placing the WiXBalExtentionExt.dll file into my WiX 3.7 bin folder did not
make a difference. So was there anything else you had to do or did to make
this work?

Can both 3.7 and 3.8 reside on the machine at the same time? If as you said
that 3.8 already has the fix in it then I was thinking of installing 3.8 on
my main machine to test and verify if it works without changing anything in
my Burn wrapper code.

If it does then I'll make the suggestion to our group to upgrade to 3.8 when
we can, but if it does not simply work out of the box then I'll have to do
more research before I can make the suggestion to upgrade to 3.8.

Tim.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7588181.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

No, but I had a similar issue and determined that Symantec is assuming that
if the package does not have a valid Code Signing signature it is a virus. 
There is no virus, it is a FALSE Positive which many others have also had
issues with.  If you use your code signing certificate to sign the bundle
then Symantec will leave you alone.  I lost several hours figuring that out.

The German wxl file has a title string set to:
[WixBundleName] de-de

so that you can see that the German strings were loaded (even if they were
not translated).  A similar change was made to the EULA so that you can tell
when the 'German' EULA is displayed.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7588182.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

Ok Phill, I was able to download and extract the files from your zip. I tried
out both .exe that you created and created a German VM to test on. They did
show the German EULA and when I switched to my French image it showed the
English EULA.

I then updated your German .wxl file with German text strings so that I
could see if I could build it and show the UI in German just to verify the
UI as well as to add a French file, but when the build completes my Symantec
AntiVirus Detection pops up stating there is a Heuristic Virus in the .exe
file that is created and therefore it will NOT let me create the .exe file.

So there is something in the code that you supplied that it does not like
and therefore I can not test the UI correctly.

Now if I go back to my project, I'll try it again with copying the
WiXBalExtention.dll from the specified link and place into my bin folder to
test and see it that makes a difference.

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7588177.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

2013-08-17 Thread Phill Hogland

Tim; I took your wxs file and added it to a new WiX bootstrapper setup
project (in VS2010). I tried to recreated your file tree as closely as
possible and I stripped out the code that was not related to testing whether
the localized files were displayed, without needing to provide the -lang
switch.

For the file tree I used RTF files that I have and a simple MSI test
package. Since my test box is currently configured to test either English
or German, for simplicity I eliminated the other languages. But otherwise I
tried to use your code as you presented it.

I tested this on Windows 8 x64, which is configured to set the
SystemDefaultLanguageID based on the UserDefaultLanguageID. And it is
configured to set the UserDefaultLanguageID to the top item in the Input
Language display list.

First I built the package using Wix 3.8.722 and tested it with German set as
the Default Language, successfully. Then I changed to English for the
default language, and the English dialog was displayed successfully.

Then I reconfigured my build box to build the project using WiX 3.7.1224. I
tested this build in the German configuration, and it displayed the German
dialogs and German EULA successfully. Then I switched the default to
English and ran the setup. It detected and displayed the English dialogs
and EULA successfully. Actually this surprised me, as I thought I would
have to convert your code to use the WixExtenededBootstrapperApplication in
WiX 3.7 for this to work. But that was not necessary. However my WiX
3.7.1224 does have the WixBalExtensionExt.dll from:
http://wixextba.codeplex.com/releases/view/105895

which I copied to my WiX 3.7.1224\bin folder. So maybe when Neil says that
there was a bug in 3.7 which is fixed in the Extended Bootstrapper, it is
only necessary to have his DLL in the Wix 3.7 bin folder to get the fix,
without actually using the WiXExtendedBA UI. I will have to research this
further.

I will try to attach a zip package of the project as I built it.
Test_SmartTable.txt

If it works you will find both the 3.7 and the 3.8 build which I tested.
Because of the antivirus configuration on our network I had to sign the test
builds with my certificate, but I removed those steps from the archived
project. Bottom line is I don't know if this is all that helpful since it
does not explain your observations, but your code does automatically display
the translated EULA for me. Phill

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7588148.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

2013-08-16 Thread Phill Hogland

Tim, I'm sorry.  You are correct that I did not read down far enough.

I looked it over more carefully and I do not see a problem with your code. 
I guess I would study a ProcessMon log or setup WinDbg.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7588134.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

2013-08-16 Thread TimM

Thanks Neil...

Phill you mentioned the following:

Phill Hogland wrote
> I looked at your code.  You do not have any translated Payload .wxl files
> with name attributes in the form "LCID\thm.wxl" , etc. 

And I do have translated Payload .wxl files, they are listed in the
PayloadGroup ID="RtfTheme_Strings element fragment shown further down in
that file. So this should not be an issue and other than that and that you
now use the Hyperlink BA our code is is basically the same.

I have not yet had a chance to look at the examples and the code fixes that
Niel has for WiX 3.7, but when I do I'll let you know if the language
example work as expected.

Tim.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7588127.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

2013-08-16 Thread Phill Hogland

Here is my code:

I looked at your code. You do not have any translated Payload .wxl files
with name attributes in the form "LCID\thm.wxl" , etc. So when the bundle
runs it looks for these added payloads in sub folders named by the LCID
(such as 1031, 1033, etc) and selects the one that matches, first the
UserDefaultLangID and then the SystemDefaultLangID ( from reading the post
that Neil made). You can use ProcessMon to see it try to find these files
even if you do not have them in your project. When you add them to you r
project it will select the correct one (if you either use a 3.7 Extended BA
or 3.8).

Also it is my understanding that WiX 3.7.1224 has a bug that affects this
behavior, but Neil says that if you use the code from the Extended
Bootstrapper site (http://wixextba.codeplex.com/releases/view/105895) he has
fixed that issue. He has also included this code in WiX 3.8 which is the
path I took.

The examples are in the zip package at the above link, or you can look at
them at:
http://wixextba.codeplex.com/SourceControl/latest

Once you add the wxl payloads to the Extended Bootstrapper Application, and
get that working, then you can eliminate the SysLang and UserLang variables
in your code and create string entries in your wxl table like I did. Pass
the string entry to a TRANSFORMS property for your MSI and that prevent your
MSI from getting a unsupported value because you have a LCID\thm.wxl file
for each supported language and burn will only select on of the .wxl.

I have two msi packges in my chain, and they require that the TRANSFORMS
property be different so I use (in 1031\thm.wxl):
1031.mst
:1031.mst

One of my MSIs does not have a 1033.mst and the other does so I do this for
English 1033\thm.wxl (passing a null string to the TRANSFORMS property does
not select any trasnform):
1033.mst

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7588124.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

2013-08-16 Thread TimM

Attached is my main WiX Burn .wxs file:

TableToolkitBootStrapper.wxs

Now again this will correctly add the .mst files and push the correct .mst
file on the command line to the .msi as long as the the system language ID
is within the conditioned ID's.

The only thing that I do not have working here is that the Burn .exe will
not run in the correct language. It will only do that if you pass in the
-lang LANGID, where LANGID is the language code that you want the wrapper to
run in. So if you wanted French you would use -lang 1036 on cmd line.

So far with WiX 3.7 my wrapper will not launch in the language of the OS and
therefore that is what I am trying to get working. So far all examples that
I have found have not worked for me... So if you have any examples on that
then could you share??

Thanks,

Tim.

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7588120.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

2013-08-13 Thread TimM

Brian,

I currently already have English MSI and supported language .mst's in my
Burn Wrapper .exe. I generated the language .mst in my VS 2010 project by
running the PostBuildEvent Torch.exe -t language command on each of the
language .msi file compared against the English .msi.

So the Burn Wrapper never got the other language .msi files, only the .mst
files for those languages.

So am I mis-understanding what you are refering to?

So what is the difference between Torch.exe and msitran.exe? In your sample
command:
msitran.exe -g $engMsi $l10nMsi $mstFile

I assume that $engMsi is the English msi and $l10nMsi is the language .msi
that you want translations extracted from and placed into .mst file.

So is this method faster than Torch.exe?

Couple other questions, you mentioned that when the .exe is ran the UI
provides the supported languages and the user selects the language desired
for the installation.
What setting to you use to have this language selection dialog come up?
Is there any way for the .exe to detect the language of the OS and
automatically start in that language?

I have been trying to get my burn wrapper .exe to launch in the language of
the OS, I am using the rtftheme with translated rtftheme.wxl files, but so
far the only way to get it to launch in a different language is by using the
-lang , where is the language ID (1036). So do you know if there is
a way/setting that can be used to have Burn launch in the language of the
OS?

Thanks.

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7587973.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

There should not be a problem with Product Codes as I am using the same .msi
in both MsiPackage entries, not multiple msi's that are language specific.

I have again just the one .msi and the language .mst's files. So if one of
the supported languages exists it will trigger the first MsiPackage ID and
pass in the correct TRANSFORMS=[SystemLanguageID].mst.

If the language of SystemLanguageID is not supported it will trigger the 2nd
MsiPackage ID and simply pass in TRANSFORMS=1033.mst.

So again I have tested with supported and non-supported language OS's and it
seems to work. So it should be good.

Tim.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7587227.html
Sent from the wix-users mailing list archive at Nabble.com.

--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

2013-07-08 Thread Hoover, Jacob

Hmm, are you sure that is going to work?  If the product code is the same for 
all of them, I am betting the upgrade/repair scenario isn't going to work as 
expected. (If the install condition is false, but it detects the product is 
installed...)

-Original Message-
From: TimM [mailto:timmay...@smarttech.com] 
Sent: Monday, July 08, 2013 4:34 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

Okay thanks Jacob...

After a bit more testing I was able to get this to work by using the 
InstallCondition. When I first tried using the InstallCondition I was looking 
for languages like this:
InstallCondition="[SystemLanguageID]=1036" and this was failing.

After some research I found out that I was formatting it incorrectly it should 
have been:
InstallCondition="SystemLanguageID=@quote;1036@quote;"

So I have a MsiPackage ID that will only trigger if the install is ran on the 
correctly supported Language OS and if it does not then I have another 
MsiPackage ID that will trigger the install in English if to Language OS is not 
any of the supported languages.

Have tested this and it now works as expected... So it took longer than I 
expected to get this working, but at least it is working without having to do a 
lot of extra work.

Tim.

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7587224.html
Sent from the wix-users mailing list archive at Nabble.com.

--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

Okay thanks Jacob...

After a bit more testing I was able to get this to work by using the
InstallCondition. When I first tried using the InstallCondition I was
looking for languages like this:
InstallCondition="[SystemLanguageID]=1036" and this was failing.

After some research I found out that I was formatting it incorrectly it
should have been:
InstallCondition="SystemLanguageID=@quote;1036@quote;"

So I have a MsiPackage ID that will only trigger if the install is ran on
the correctly supported Language OS and if it does not then I have another
MsiPackage ID that will trigger the install in English if to Language OS is
not any of the supported languages.

Have tested this and it now works as expected... So it took longer than I
expected to get this working, but at least it is working without having to
do a lot of extra work.

Tim.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7587224.html
Sent from the wix-users mailing list archive at Nabble.com.

--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

2013-07-08 Thread Hoover, Jacob

Did you look at my previous suggestion 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multiple-shortcut-localizations-in-one-MSI-td3437236.html
 ? (I know they didn't have conditions, but it appears as if they had a 
functional work around.)

-Original Message-
From: TimM [mailto:timmay...@smarttech.com] 
Sent: Monday, July 08, 2013 12:01 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

Okay thanks Jacob...

So figuring I would go with the easiest method I started to convert my main 
project with conditioned language components and then when I build I then 
receivce a bunch of errors stating:

error LGHT0311: A string was provided with characters that are not available in 
the specified database code page '1256'. Either change these characters to ones 
that exist in the database's code page, or update the database's code page by 
modifying one of the following attributes: Product/@Codepage, Module/@Codepage, 
Patch/@Codepage, PatchCreation/@Codepage, or WixLocalization/@Codepage.

Geez I just can not get a break!!!

Since my install has mulitple languages, some with different codepage support, 
I was using the language .wxl files to support this. So having all the shortcut 
strings inside each component is an issue because of the codepage support.

So I am back to the beginning. Where I'll either get an error during the 
install if using:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7587220.html
Sent from the wix-users mailing list archive at Nabble.com.

--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

Okay thanks Jacob...

So figuring I would go with the easiest method I started to convert my main
project with conditioned language components and then when I build I then
receivce a bunch of errors stating:

error LGHT0311: A string was provided with characters that are not available
in the specified database code page '1256'. Either change these characters
to ones that exist in the database's code page, or update the database's
code page by modifying one of the following attributes: Product/@Codepage,
Module/@Codepage, Patch/@Codepage, PatchCreation/@Codepage, or
WixLocalization/@Codepage.

Geez I just can not get a break!!!

Since my install has mulitple languages, some with different codepage
support, I was using the language .wxl files to support this. So having all
the shortcut strings inside each component is an issue because of the
codepage support.

So I am back to the beginning. Where I'll either get an error during the
install if using:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7587220.html
Sent from the wix-users mailing list archive at Nabble.com.

--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?

2013-07-08 Thread Hoover, Jacob

Burn and its existing WixStdBA don't support this out of the box today. I see 
two choices for you.  The first is to have a single msi with no transforms and 
either use multiple components with conditions on the localized shortcuts or 
utilize a CA at runtime to inject the localized shortcuts into the appropriate 
tables. The second choice would be to extend the toolset to allow for 
conditional properties. I floated a variation of the second option across 
wix-devs, but if this were to become a feature of the engine then the questions 
of when should the conditions be evaluated and what other elements should 
support conditions would need to be answered.

The first option can be done without fear of breaking forward compatibility, 
while the second would require the feature to be accepted by Rob or you to 
maintain your customizations.

On Jul 8, 2013, at 9:04 AM, "TimM"  wrote:

> Okay I have not yet figured this out. I have tried placing the calling of my
> MsiPackage into a separate Fragment file and add a property definition to
> default language and then conditioned custom actions for the supportted
> languages, but it looks like Burn completely ignores this default property
> and custom actions and therefore when triggering the .msi with TRANSFORM= in
> the command line that it will fail as it is not filling in the languageID
> .mst.
> 
> So again could I get a simple example on how to create a Burn custom action
> (BA) or pointed in the correct direction that will provide some help in how
> to create a BA?
> 
> Just as a note I do not have much programming language experience and the
> little that I do is with C++. So examples in C++ would be perferable. If not
> then what ever I get then I'll pass on to other developers that my have
> experience in other languages.
> 
> Thanks again for any help on this issue.
> 
> Tim.
> 
> 
> 
> --
> View this message in context: 
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7587202.html
> Sent from the wix-users mailing list archive at Nabble.com.
> 
> --
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?