[WiX-users] Admin install + saving variables

I've built my WiX project using mondo and adding in a custom dialog and admin UI sequence. My custom dialog collects 2 paths 2 files on the users system. A database and text file on the users network. These files are required by the application and stored in the registry. A version of the

[WiX-users] Command line parameters

I have 2 public properties in my MSI file. Each property is set a default value as well has a registrysearch to find a value.. e.g. Property Id=MDBFULLPATH Value=C:\Program Files\eProject\database\eProject - empty.mdb RegistrySearch Id=MDBPathRegistry Type=raw Root=HKLM

Re: [WiX-users] Command line parameters

You could use 3 different properties. One for the command line, one for the registrysearch, and one for the default. Then have two set property custom actions conditioned on whether or not the command line property is set or if the registrysearch property is set. If they are, then you would set

Re: [WiX-users] Admin install + saving variables

In article [EMAIL PROTECTED], RussGreen [EMAIL PROTECTED] writes: A version of the custom dialog is also in my adminUI. What I want to do is to be able to run and admin install and input the paths to these 2 files (this works) but then when I run the MSI created during the admin install

Re: [WiX-users] Command line parameters

In article [EMAIL PROTECTED], RussGreen [EMAIL PROTECTED] writes: What I want to be able to do is pass in a value for this property from the command line but that only works when RegistrySearch is commented out. As Peter Marcu suggested, use a different property for the value retrieved

Re: [WiX-users] Command line parameters

Ah so simple -- View this message in context: http://www.nabble.com/Command-line-parameters-tf4666532.html#a13332073 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk

Re: [WiX-users] For a commerical install - Wix 3.0 Vs Wix 2.0

WiX 3.0 is fairly stable at this point. Very few new features are being added and it is being used by some fairly large and complex installs already. It is also is more feature rich than 2.0, as well as having many bugs fixes that didn't make it into 2.0. As long as you are willing to update

[WiX-users] Wix CA

I am using WIX 2.0. I am trying to call an executable as part of my install. The EXE file is one of the installed files. But after the install , the EXE is never getting executed. Any pointers ?? My code snippet looks like InstallExecuteSequence Custom Action='LaunchFile'

Re: [WiX-users] Wix CA

Thanks for the quick help.. I tried this approach of using FileKey and doesn't work. Do I need the second step even if I am using execommand ?? Whats missing here InstallExecuteSequence Custom Action='LaunchFile' After='InstallFinalize'NOT Installed/Custom /InstallExecuteSequence

Re: [WiX-users] Wix CA

What's missing is: CustomAction Id=LaunchFile BinaryKey=wixca DllEntry=CAQuietExec

[WiX-users] FileSearch not working for minor version?

Hi, I am having trouble with detecting if a file is installed, I am using the following code, however it seems that WIX sets the property even if MinVersion is 7.10.3191.0 Property Id=KB907417INSTALLED DirectorySearch Id=OfficeFolder Path=[XLSPROGPATH] Depth=1

[WiX-users] Problem in WIX

I need help in the following scenarios in wix. 1. How to use two binary file in a single custom Action in WIX? 2. How to pass a binary file as a input parameter to a vbscript custom Action which will be invoked by another binary file? 3. How to delete unwanted files after the

Re: [WiX-users] Wix CA

Still My catsign.exe is not executed. I tried (SourceFile=c:\windows\system32\catsign.exe ) also InstallExecuteSequence Custom Action='Launchfile' After='InstallFinalize'NOT Installed/Custom /InstallExecuteSequence CustomAction Id =Launchfile Return=check FileKey=catsign.exe ExeCommand= /