[WiX-users] Custom action without having to install .net

I have created a custom action using C# .Net 4.0 that is supposed to get the property passed to it and create a file eg: msiexec /i somemsi.msi /l*v out.txt IPADDRESS="127.0.0.1" I have created both MSI that does the work. But as this MSI is to be deployed to customers, I have following questions

Re: [WiX-users] Problems with debugging the BootstrapperCore source files

Hi, Could anyone please help me on the above mentioned problem ? Thanks, Balaji -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problems-with-debugging-the-BootstrapperCore-source-files-tp7599236p7599266.html Sent from the wix-users mailing list

Re: [WiX-users] keep service accont info on reinstall

In general, you should implement the 'remember property' pattern to recover data that you will need for repair or uninstall. However for finding the account that a service is using you could do a Registry

Re: [WiX-users] burn bootstrapper access -lang as a property or variab le

I currently use an mba which has my bundle strings in the C# mba project. I use the wxl files for my localized msi packages, for localized shortcut descriptions, etc. My bundles rely on default behavior of Burn to use the -lang switch if it exists otherwise select the correct local based on the s

Re: [WiX-users] burn bootstrapper access -lang as a property or variab le

I have been attempting to use the localization files to do this type of thing, but no matter what I try, the variables don't use the localized values. (Again, the UI shows the localized values, but the variables i.e. LanguageID or !(loc.LanguageID) always use the not localized values). Is this a

[WiX-users] keep service accont info on reinstall

Hi All.I have a wix project which installs a window service and allows the user to select an account to assign to the service using the AsiUI_DirectoryObjectPicker. when I make changes I change the Product Id value and send out the MSI is there a way to lookup the current account set to run our

Re: [WiX-users] Lux Multi-value Unit Test

For those interested, the solution was to implement code in the Ca's Mutation, which avoids the call to schedule the deferred action, to also add code that parses the CData Property and replaces MAGIC_MULTISZ_DELIM with a more suitable 7-bit ASCII character (which is appropriate for the data set be

Re: [WiX-users] burn bootstrapper access -lang as a property or variab le

Jacob makes good points, but I used the information that in the previous links. When using the WixStdBA, since as you found "the bootstrapper is correctly switching to the localized 1046\thm.wxl and 1046\license.rtf" you can take advantage of that fact by: 1) define a Variable element which is ove

Re: [WiX-users] MSI Feature and Condition element in MSI Repair using Custom Bootstrapper Application

When repairing a MSI only features and components that were installed in first place are being reinstallde. You can read more about it in the documentation of REINSTALL property. You can try using COMPADDLOCAL

Re: [WiX-users] burn bootstrapper access -lang as a property or variab le

I assume you are using WixStdBA and not your own BA? If so, looking at the Wix4 source the lang command line parsing is done from within WixStdBA and not the engine. Sadly, it's not creating a variable (thought it would seem to be a valid feature request). Inside of WixStandardBootstrapperAppl

Re: [WiX-users] burn bootstrapper access -lang as a property or variab le

I'm afraid the provided link hasn't helped me solve my problem. I am trying to get the bootstrapper and the MSI to both be translated into the same language. When the user enters the -lang 1046 as a command line parameter for the bootstrapper, the bootstrapper is correctly switching to the local

Re: [WiX-users] Visual studio 2008 and wix 3.9

True. Look here . -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Visual-studio-2008-and-wix-3-9-tp7599248p7599254.html Sent from the wix-users mailing list archiv

Re: [WiX-users] burn bootstrapper access -lang as a property or variable

Maybe this thread is helpful. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/burn-bootstrapper-access-lang-as-a-property-

Re: [WiX-users] Modify Installed MSI Features using Custom Bootstrapper Application

Sounds like this question . -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Modi

Re: [WiX-users] MSI Feature and Condition element in MSI Repair using Custom Bootstrapper Application

I think the issue is that Component conditions are only evaluate when initially installed. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/template/NamlServlet.jtp?macro=reply&node=7599244 https://msdn.microsoft.com/en-us/library/aa372462%28v=vs.85%29.aspx When using Burn to drive M

Re: [WiX-users] Using a WiX Selection Tree control, when I select Feature 1, I want Feature 2 to be selected automatically

Maybe I am missing something, but wouldn't it be simpler to use Components and Component Groups to do this. The Features are simply user selectable containers. Components (Groups) may be assigned to multiple Features. If two features contain a component, and either feature is selected, the compo

Re: [WiX-users] Using a WiX Selection Tree control, when I select Feature 1, I want Feature 2 to be selected automatically

Agreed. Laid out that way, INSTALLLEVEL and the rest of the machinery will work correctly. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |jocoo...@jackhenry.com

[WiX-users] Visual studio 2008 and wix 3.9

Hello, Wix 3.9 doesn't support Visual Studio 2008 anymore? -- Best regards, Sergey Yukhno Visutech System Ltd. tel.: +375 17 211 02 84 fax: +375 17 200 42 48 38 Nemiga St., Minsk, 220004 Republic of Belarus www.visutechsystem.by ---

Re: [WiX-users] WiX Bundle - Hide Text on Options page, based on Pre-processer variable

Hi Sean, Many thanks for your help ... worked a treat !! Cheers, Chris. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-Bundle-Hide-Text-on-Options-page-based-on-Pre-processer-variable-tp7599226p7599246.html Sent from the wix-users mailing l

Re: [WiX-users] User cancels bootstrapper install after .NET reqirement installed - app shows up in ARP

I encountered the same issue and ended up writing a method in my custom BA to manually remove the BA uninstall registry items on Close if no product feature was installed. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/User-cancels-bootstrapper-i