Re: [WiX-users] Setting up .net version check and halting install

2014-06-17 Thread Devin Morrow
Ok... Sorry for the spam but I think I'm almost there. I have modified the mbapreq files to display only the buttons and text I want. The only problem is I can't seem to localize them. It looks like I could handle forcing it into one language or another but I can't have it do all of them depending

[WiX-users] Distinguishing in between installation with pre-requisites and maintenance modes.

2014-06-17 Thread alex.fedin
Hello everybody, Here in our group we're working on a managed installation bootstrapper application based on Wix Burn. There are at least two scenarios in question: * Clean machine, no .NET Framework, the bundle has .NET Framework as pre-requisite. o The Wix Burn Runtime checks if pr

[WiX-users] Removing the line "Will be installed on local hard drive"

2014-06-17 Thread Pavan Konduru
Hi All, Looks like I have been sending my mail to the wrong group. Finally, got it right I guess!! Has anyone tried removing the option "Will be installed on local hard drive" in the feature selection page? I have an installer with 3 features(visible to user), I don't have any sub-features. I h

Re: [WiX-users] Setting up .net version check and halting install

2014-06-17 Thread Devin Morrow
Ok so after looking into mbapreq.thm and wxl I'm noit sure that is all that I want. On the positive side, it's exactly what I need for the localization task. On the other hand I don't see I think these files alone are going to get me the logic I want. I think what I need is something like a mbapr

Re: [WiX-users] Setting up .net version check and halting install

2014-06-17 Thread Devin Morrow
"Put the check I described as the First Condition in your first MSI in your bundle chain. Coding a link in the message box may require escaping characters and such, but is doable. With that in mind, the code you removed in your first post is the most elegant method of doing this. Inste

Re: [WiX-users] Wix 3.8 - Burn - DetectCondition string compare syntax

2014-06-17 Thread froggie
Ah damn! This gets me every time. Thank you for your help! I think the offical documentation needs some additional advices/hints/tricks/examples. Am 17.06.2014 14:04, schrieb Phill Hogland: > A string should be enclosed in quotes, but in a XML statement use the html > entity " or use CDATA.

Re: [WiX-users] Wix 3.8 - Burn - DetectCondition string compare syntax

2014-06-17 Thread Phill Hogland
A string should be enclosed in quotes, but in a XML statement use the html entity " or use CDATA. http://wix.tramontana.co.hu/tutorial/com-expression-syntax-miscellanea/expression-syntax http://www.ascii.cl/htmlcodes.htm DetectCondition=" GOTO_ASSISTEXISTS = &qout;$(var.GoToAssistExpertName)

Re: [WiX-users] Wix 3.8 - Burn - DetectCondition string compare syntax

2014-06-17 Thread froggie
Is there any information available about the syntax and string compare? Am 16.06.2014 11:27, schrieb froggie: > Hi! > I'm trying to do a string compare in a DetectCondition. According to the > log the syntax is wrong. > But what is the correct syntax? > > What I want: Check wether a registry value

Re: [WiX-users] How to make a condition that works both for silent and interactive install

2014-06-17 Thread Dolevo Jay
I had already a Feature table in my wxs file. I have changed the Feature='DefaultFeature' to point to the existing feature. The below is gone but I have a new error: light.exe : error LGHT0130 : The primary key 'DefaultFeature/WebAppSettings' is duplicated in table 'FeatureComponents'. Please

Re: [WiX-users] How to make a condition that works both for silent and interactive install

2014-06-17 Thread Dolevo Jay
As far as I understood from the tutorial that you linked, I don't need so, I deleted it. But now I got light.exe : error LGHT0204 : ICE03: Not a valid foreign key; Table: FeatureComponents, Column: Feature_, Key(s): ProductFeature.WebAppSettings Here is the related code part: