[WiX-users] Bootstrapper for multiple cultures

[vikasyv]

Hi,

 Please excuse me if this has already been discussed before. I am trying to
implement a bootstrapper for multiple cultures. After searching around, I
found some help but with that, I am only able to build 2 separate MSIs for 2
cultures and I now have to build 2 separate bootstrapper exe packages, one
for each culture. I need some help regarding this:

- Once we have 2 MSIs, for say English and Japanese, how do I create
Multiple bootstrappers for the same where the
WixStandardBootstrapperApplication  application strings also need to be
localized? Please provide some examples or links for the same.

- The Ideal solution would be to create a page for language selection in the
bootstrapper which will then apply the required localizations. That way, I
will have only 1 MSI package with default language but since localization
will be applied on the bootstrapper, the user sees the Installation in his
local language. How can we achieve this in Wix? If you have any examples,
can you please share them?

Thanks and Regards
Vikas



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-for-multiple-cultures-tp7598840.html
Sent from the wix-users mailing list archive at Nabble.com.

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Access installation progress values outside Bootstrapper application

[Mohamed Yasir]

Hi, 

Could you please update any idea on this? 

Thanks in advance. 

Regards, 
Mohamed Yasir K



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Access-installation-progress-values-outside-Bootstrapper-application-tp7598824p7598839.html
Sent from the wix-users mailing list archive at Nabble.com.

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Uniting Burn and WiX(MSI) projects

[Rob Mensching]

No. You'd have to hack up the wix MSBuild targets *significantly* to get there. 
Not at all designed to work that way.
_
 Short replies here. Complete answers over there: http://www.firegiant.com/


-Original Message-
From: ronif [mailto:ro...@microsoft.com] 
Sent: Monday, January 12, 2015 9:00 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Uniting Burn and WiX(MSI) projects

Hi,

Is it possible to have only one project the contains both Burn related parts 
(installing prerequisites,...) and regular MSI parts?

(i.e. uniting  and ?)

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
www.gigenet.com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Two Mutually Exclusive Products

[Marc Beaudry]

You are correct: ProductSearch does have an UpgradeCode too, I am using wix
3.8 and the documentation of 3.8 doesn't make reference to the UpgradeCode.
I will try using 3.9.

I will also investigate (learn)  what you mean by implementing code in the
ba (???) for the OnDetect handlers.

Thanks for your input, 
Marc

-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com] 
Sent: January-12-2015 11:48 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Two Mutually Exclusive Products

I'm a little confused by the comment about ProductSearch, sorry.

- ProductSearch: requires a product code which I cannot use

The wix:ProductSearch for use in authoring an MSI takes
ProductSearch/@UpgradeCode as the input.

The util:ProductSearch for use in a bundle takes either a ProductCode or an
UpgradeCode (which I think was added in wix 3.9 ).

I use a bundle driven msi(s) method and so in a similar situation where I
have mutually exclusive 'products' (suites of products).  In my situation
rather than use a bal:Condition, I implement code in the ba, which is called
in the OnDetectXxx handlers to determine if I need to communicate with the
user and terminate the setup.  



--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Two-Mutually-E
xclusive-Products-tp7598832p7598833.html
Sent from the wix-users mailing list archive at Nabble.com.


--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
www.gigenet.com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
www.gigenet.com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Uniting Burn and WiX(MSI) projects

[Phill Hogland]

I suspect that you might be able to create a MSBuild targets file that would
do that.  The wix source tree uses MSBuild targets files (.proj) which
reference groups of projects.  Each project still has a project file (.proj
or .wixproj), which is unique to the type of project being output (by
setting the OutputType property).  It seems like creating a single file for
all of the projects would be rather complex.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Uniting-Burn-and-WiX-MSI-projects-tp7598834p7598835.html
Sent from the wix-users mailing list archive at Nabble.com.

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
www.gigenet.com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Uniting Burn and WiX(MSI) projects

[ronif]

Hi,

Is it possible to have only one project the contains both Burn related parts
(installing prerequisites,...) and regular MSI parts?

(i.e. uniting  and ?)





--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Uniting-Burn-and-WiX-MSI-projects-tp7598834.html
Sent from the wix-users mailing list archive at Nabble.com.

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
www.gigenet.com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Two Mutually Exclusive Products

[Phill Hogland]

I'm a little confused by the comment about ProductSearch, sorry.

- ProductSearch: requires a product code which I cannot use

The wix:ProductSearch for use in authoring an MSI takes
ProductSearch/@UpgradeCode as the input.

The util:ProductSearch for use in a bundle takes either a ProductCode or an
UpgradeCode (which I think was added in wix 3.9 ).

I use a bundle driven msi(s) method and so in a similar situation where I
have mutually exclusive 'products' (suites of products).  In my situation
rather than use a bal:Condition, I implement code in the ba, which is called
in the OnDetectXxx handlers to determine if I need to communicate with the
user and terminate the setup.  



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Two-Mutually-Exclusive-Products-tp7598832p7598833.html
Sent from the wix-users mailing list archive at Nabble.com.

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
www.gigenet.com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Two Mutually Exclusive Products

[Marc Beaudry]

Hello Everyone,

I have two mutually exclusive products I need to write an installation for.
These two products are part of our daily builds so I cannot predict what the
Package and Product codes will be for the current and future releases.

I have done some research and have found a few alternatives as solutions,
but none seem to be the correct way of doing this.

- ProductSearch: requires a product code which I cannot use
- AppSerach???
- FileSearch
- RegistrySearch
- Custom Action (To detect if other product is installed and warn user to
uninstall product before running the current installation)

The only thing (Unless I am misunderstanding something) is that I know the
UpgradeCode of both products,, as these never change.  

Ideally here is the behavior I would like in the end.
- If other product is installed, then warn the user of the condition and
cancel the current installation
- Upgrades of the same product behave as normal. Using the 
Tag 

Here is something I tried based on some code I found on StackOverflow



  
  
 


  




Let me know if this is the best approach, or if you have a better
suggestion, I would welcome that too.

Thanks
Marc







--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
vanity: www.gigenet.com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Creating patches using wixout (-bf flag deprecated)

[Nick Ball]

Thanks for the fantastic detailed clarification on this issue! I will endeavour 
to use the melt approach outlined in Bob's post. 

-Nick



--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
vanity: www.gigenet.com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bootstrapper doesn't run MSI package

[Phill Hogland]

[1D28:0570][2015-01-12T15:19:10]i101: Detected package: Application, state:
Obsolete, cached: None 

[1D28:0570][2015-01-12T15:19:12]i201: Planned package: Application, state:
Obsolete, default requested: None, ba requested: None, execute: None,
rollback: None, cache: No, uncache: No, dependency: None 

When I have seen "state: Obsolete" the package in the setup is older (down
version) than the package already on the system.  For me this has pointed to
to possible problems.
1) Clean up my test process and always start with a clean VM when initially
testing a msi.
2) Make sure my build process always increments something in the first three
parts of the msi version (as well as the Product Code) to qualify as a MSI
Major Upgrade.

I don't claim to have a lot of experience with this so maybe someone else
can clarify.




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-doesn-t-run-MSI-package-tp7598826p7598830.html
Sent from the wix-users mailing list archive at Nabble.com.

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
vanity: www.gigenet.com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Strange behavior of SetupAPI function : InstallHInfSection

[Phill Hogland]

I would also enable MSI extra debug logging and evaluate the msi logs,
typically in %temp%.  My first guess, and it is only a guess (without
specific data from the log) is that on a x64 system, if the msi CA tried to
launch a 32 bit version of the api it would fail.  But again this is only
one possible guess.  If the call to the Setupapi.dll failed due to bitness,
I would not expect any entry in the setupapi.xxx.log, but you should see
info in a verbose msi log.

On Win7, I assume that you looked at both the setupapi.app.log and the
setupapi.dev.log (and not setupapi.log).  I also assume that you enabled
full verbose setupapi logging prior to running the setup, as the default
logging often does not provide much information.  For info see  here

 
.

I would use the Wix DifxAppExtension, and avoid using a CA to call
InstallHInfSection.
In a Component element, which includes the File Element for the INF file,
add the following (and adjust the parameters to your needs):

 





--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Strange-behavior-of-SetupAPI-function-InstallHInfSection-tp7598825p7598828.html
Sent from the wix-users mailing list archive at Nabble.com.

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
vanity: www.gigenet.com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bootstrapper doesn't run MSI package

[Phill Hogland]

You need to evaluate the verbose log (or past to a post relevant parts for
others to help).  It is typically in your %temp% folder, with obvious name
based on your product name.  There will be a log for the bootstrapper which
contains the 'plan' and for each msi, if launched.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-doesn-t-run-MSI-package-tp7598826p7598827.html
Sent from the wix-users mailing list archive at Nabble.com.

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
vanity: www.gigenet.com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users