Re: [WiX-users] using TARGETDIR from command line or default to C:\ProgramFiles\AppName

Dave is right, I overlooked that part. In your case, "Root" is what holds the path to installation, always a good idea to have it all in uppercase. So, make your external app pass this to msiexec /i ROOT= C:\ProgramFiles\AppName -Original Message- From: David Connet [mailto:d...@agilityre

Re: [WiX-users] using TARGETDIR from command line or default to C:\ProgramFiles\AppName

TARGETDIR is not what you use to set the install location. You want to replace your Id 'Root' with something like INSTALLDIR. That's the variable you set on the command line. Additionally, you need to set Feature/@ConfigurableDirectory to INSTALLDIR. And to deal with repair/upgrades, you need t

Re: [WiX-users] using TARGETDIR from command line or default to C:\ProgramFiles\AppName

Thanks Pavan. But if I have this in my Product.wxs: No matter what I pass in the external app, WiX defaults to ProgramFiles\appName folder. The only way I can have the external app control it is, if I dont have the above code in my Product.wxs. I was wondering if I can swi

Re: [WiX-users] using TARGETDIR from command line or default to C:\ProgramFiles\AppName

Your external app is controlling your WIX installer and not the other way around. So, no matter what you do in WIX, the Target is controlled by that external app. --Pavan -Original Message- From: Prashanth Srinivasan [mailto:pra...@gmail.com] Sent: Friday, May 16, 2014 12:54 PM To: wix-

[WiX-users] using TARGETDIR from command line or default to C:\ProgramFiles\AppName

I have an MSI, which will be delivered through an external application. The external app has the ability to set install directory which will be translated to msiexec /i TARGETDIR="C:\abc". This works perfectly fine. The issue I have is that, when the user wants the install to occur in the default

Re: [WiX-users] Starting a service from an MSI

Try taking out the Account="NT AUTHORITY\LocalService" I have a per-machine installer and my service works . It by default runs as local system account. -Original Message- From: Brian Enderle [mailto:bria...@gmail.com] Sent: Friday, May 16, 2014 11:44 AM To: WiX Users Subject: [WiX-use

Re: [WiX-users] HeatDirectory MSBuild task dying with BadImageFormatException

Bah, turns out I needed to explicitly point to the msbuild in: C:\Windows\Microsoft.NET\Framework\v4.0.30319\ No other instance of MSBUILD.EXE works with this particular assembly. Why would the other WiX assemblies work out ok? Perhaps some bad .config value or compiler options for heat.exe?

[WiX-users] HeatDirectory MSBuild task dying with BadImageFormatException

Hey everyone, Ok, I've added a BeforeBuild target in my wixproj to run heat on a directory using the HeatDirectory task. I see in my logs that msbuild is successfully calling lit, candle, etc. successfully but I get the following error from heat :( Thoughts? I get this whether I run msbuild

[WiX-users] Starting a service from an MSI

I have an MSI that installs everything correctly (when I don't try to start the service). When I try to start the service it fails with the message "...Failed to start. Verify that you have sufficient privileges to start system services" Is it possible to start a service from an MSI? Here is m

Re: [WiX-users] Displaying custom error messages if deferred CA fails [P]

In general the MsiSetExternalUI related stuff is available with a NET interop layer that wraps MsiExternalUIRecord. For example, you can arrange to handle FilesInuse events (search for ExecuteFilesInUseEventArgs) and display the dialog. Or search for BootstrapperApplication.ExecuteMsiMessage. The

[WiX-users] Upgrading a package previously intsalled via a burn bundle with a msi.

Hey folks, Hello, was wondering if I could get some thoughts on this... I've been asked to provide a bundled exe created in burn and a MSI for our product... The idea being that clients will generally use the exe which will install the our msi and VSTO. The standalone MSI I've been asked to pr

Re: [WiX-users] Documentation for creating a Managed Bootstrapper Application for WiX Burn

>>WiX Extended Bootstrapper Application by Neil Sleightholm https://wixextba.codeplex.com/ This site is not really related to creating a mba. It is about how to extend the WixStdBA in wix 3.7 by creating a BAFunctions.dll. Most of this functionality is integrated into Wix 3.8 (and later), but

Re: [WiX-users] Documentation for creating a Managed Bootstrapper Application for WiX Burn

"Custom WiX Managed Bootstrapper Application" by bryanpjohnston http://bryanpjohnston.com/2012/09/28/custom-wix-managed-bootstrapper-application/ On Sat, Apr 12, 2014 at 10:36 PM, Alasdair King wrote: > So I've found the following sources of documentation and information. Are > there any more

Re: [WiX-users] Managed bootstrapper on a PC without .NET framework 4.0

Ok, just solved this. On Windows 7 without SP1, there is Net FW 3.5. In my BootstrapperCore.Config file, it was: ** *I removed .* This causes bootstrapper to launch .Net FW 4.0 installation (Packed with as payload). It updated the machine with .Net FW 4 and then launch

Re: [WiX-users] Managed bootstrapper on a PC without .NET framework 4.0

Sky, I faced same problem. At the end, we discovered that on Win 7 with no SP, we are getting this error. When we installed Net Framework 4 (dotNetFx40_Full_x86_x64.exe) on same windows, it started working fine. So finally we got to know that on Windows 7 + Service Pack 1, it may work fine. How

Re: [WiX-users] unsubscribe

Dit mailadres is niet meer in gebruik. Mail kan je voortaan sturen naar basti...@careercontrol.nl. -- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+

Re: [WiX-users] unsubscribe

The "Project.app" file is one feature in the msi, there is also an IIS website and SQL database - all components of a SharePoint app. Some of the data collected or passed in needs placed in web.config and the app.manifest (xml) inside the zip. This file needs uploaded to a catalog somewhere so is b