From MSI to WiX, Part 3 - Launch Conditions and Application Search

Fiberglass flowers / WiX linkdump: samples and howto-s I found, mostly .NET deployment

Fri, 21 Mar 2008 02:48:30 GMT

PingBack from http://victorsergienko.com/wix-net-linkdump-samples-howto-s/

rCustomAction Before LaunchConditions generates 2731 error

Baldur van Lew — Wed, 21 May 2008 14:25:43 GMT

Hi Alex,

I'm trying to get a CustomAction running before LaunchConditions (it retrieves som system info I want to check). This works on Vista and XP but not on a Server 2003 SP1.

The error is 2731 Selection Manager not initialized. (I read somewhere that initialization occurs in the file costing).

To be specific the msiexec versions are

Vista: V 4.00.6001.0

XP: V 3.01.4000.1823

Server 2003: V 3.01.4000.3959

Is a there a know difference between 2003 and the other two OS versions as regards this?

re: From MSI to WiX, Part 3 - Launch Conditions and Application Search

Alex Shevchuk — Thu, 22 May 2008 03:51:21 GMT

Sorry, I don't know the answer. Are you using MSI API to get OS info or just regular Win32 API? This error indicates that some MSI API call was in use that required costing to be completed. Also, you might want to get a log file which may help you in identifying the problem. Obviously, your custom action must put detailed log info into log.

Also, is your custom action is scheduled in both UI and execute sequence tables? When you install your application, do you use the same UI level in all three OS's?

re: From MSI to WiX, Part 3 - Launch Conditions and Application Search

Friedrdich — Fri, 13 Jun 2008 10:47:55 GMT

I'm sorry but this does not work

Property Id='TESTAPP' Value='[ProgramFilesFolder]XYZ'>

Regards

Friedrich

re: From MSI to WiX, Part 3 - Launch Conditions and Application Search

Alex Shevchuk — Thu, 26 Jun 2008 06:49:40 GMT

Strange. It does work for me. Here is sample project:

<?xml version="1.0" encoding="UTF-8"?>

</Component>

</Directory>

<RegistrySearch Id='TestAppRegSearch'

Root='HKLM'

Key='SOFTWARE\Microsoft\.NETFramework'

Name='InstallRoot2'

Type='raw' />

</Property>

</InstallExecuteSequence>

</Feature>

</Product>

</Wix>

re: From MSI to WiX, Part 3 - Launch Conditions and Application Search

Lee Parker — Fri, 15 Aug 2008 17:38:45 GMT

I have a wix project that has 2 features and is working the way I want from the UI.

What I need is a way for someone to select features from the commandline without using a transform. Can this be done by setting properties and using condition statements?

re: From MSI to WiX, Part 3 - Launch Conditions and Application Search

Alex Shevchuk — Sat, 16 Aug 2008 03:03:03 GMT

Search for ADDLOCAL/ADDSOURCE properties.

re: From MSI to WiX, Part 3 - Launch Conditions and Application Search

Ram — Thu, 04 Sep 2008 08:02:11 GMT

Hi Alex,

I'm using setup and deployment project to create setup for my vb.net windows application.

while deploying the application on target machine i need to check the user permissions. if the user is administrator then it should install. if not the installation should terminate.

please help me to achieve this.

thanks

re: From MSI to WiX, Part 3 - Launch Conditions and Application Search

Alex Shevchuk — Sun, 07 Sep 2008 00:25:26 GMT

Hi Ram,

Best practice for checking if user has administrative privileges is to use Custom Action Type 19:

Not Privileged

</Custom>

</InstallExecuteSequence>

You need to schedule it in both InstallExecuteSequence and InstallUISequence. Keep in mind that on Vista with UAC on, Privileged may be defined even if user is not an Admin.

Alex

re: From MSI to WiX, Part 3 - Launch Conditions and Application Search

Amir — Tue, 25 Nov 2008 00:43:56 GMT

Hi Alex,

Great article, i am working on a local app for our company and i am having a bit of a problem implementing AppSearch codes, here is my xml, any comments?

<Property Id="TORTOISENOTINSTALLED">Could not find TortoiseSVN.</Property>

</Property>

<Custom Action="ISTORTOISEINSTALLED" After="FindRelatedProducts">TORTOISEINSTALLED<>""</Custom>

</InstallUISequence>

now when i got to HKLM\\SOFTWARE\\TortoiseSVN and change it to HKLM\\SOFTWARE\\TDDDDDDDDDDDDDDDDDDDortoiseSVN

TORTOISEINSTALLED seems to be returning ":1"

any help is greatly appreciated

Thanks,

Amir

re: From MSI to WiX, Part 3 - Launch Conditions and Application Search

aMIR — Tue, 25 Nov 2008 05:38:39 GMT

Never mind got it working

Thanks :)

re: From MSI to WiX, Part 3 - Launch Conditions and Application Search

ram — Mon, 19 Jan 2009 13:36:32 GMT

Hi Alex,

my application needs to have .netframework2.0 and MDAC2.8.

i'm using launch conditions to check for these components and installing using installUrl property.

But my problem is,

if my target machine don't have these two components, my installer starts installing .netframework2.0 and after installing framework2.0 it is not directly installing MDAC2.8.Again i need to click on installer to install the second component.

is there any way to install all the prerequisites on single click?

re: From MSI to WiX, Part 3 - Launch Conditions and Application Search

Ferdin — Fri, 27 Feb 2009 13:00:28 GMT

I am a newbie to Wix and i'm using .NET 2.0, Visual Studio 2005, Wix 2.0. I need to check in the client machine if .NET 2.0 or later versions are installed if not it should start the installation of .NET 2.0.

I tried many but nothing works it detects .NET 2.0 is not installed and winds up the installation.

Is there any ideas which you could suggest me?

Thanks in advance

Ferdin

re: From MSI to WiX, Part 3 - Launch Conditions and Application Search

Alex Shevchuk — Fri, 27 Feb 2009 19:40:32 GMT

Hi Ferdin,

You need a bootstrapper:

http://wix.mindcapers.com/wiki/Bootstrapper

Alex

re: From MSI to WiX, Part 3 - Launch Conditions and Application Search

padma — Wed, 18 Mar 2009 21:08:29 GMT

Is these any way launch condition shouldn’t evaluate at uninstall?

Thank you,

Padma.