Dec 7, 2015 at 5:25 PM
have you implemented this new variable in your BA?
Dec 7, 2015 at 6:45 PM
Yes in the 3.10 version.
Dec 7, 2015 at 7:29 PM
Does not seem to be working, I am using it as follows:

<Variable Name="LaunchWorkingFolder" Value="[InstallFolder]\Capture OEM\" />
Dec 7, 2015 at 10:38 PM
Can you confirm you are using v3.10.5758.27000
Dec 8, 2015 at 12:32 PM

I am using Burn v3.10.1.2213, Windows v10.0 (Build 10240: Service Pack 0)

I can’t find 3.10.5758.27000

Dec 8, 2015 at 12:48 PM
Dec 8, 2015 at 1:02 PM

Sorry I thought you were asking about the Wix version.

Yes I have your latest beta version, just downloaded when I updated wix.

Dec 8, 2015 at 1:05 PM
Have you checked that this feature works with the native WiX 3.10 code?
Dec 8, 2015 at 1:06 PM

Not yet but I will, thought I would check with you first to see if you have tested it yet

Dec 8, 2015 at 1:36 PM

Just looking through the source:

case "LaunchWorkingFolder":

launchWorkingDir = this.Core.GetAttributeValue(sourceLineNumbers, attrib, false);


Should the variable stay LaunchWorkingFolder

In the BA I see the call ShelExec:

hr = ShelExec(sczLaunchTarget, sczArguments, L"open", sczLaunchFolder, nCmdShow, m_hWnd, NULL);

It looks like this gets the bundle variable:


then it sets it to:

hr = BalGetStringVariable(WIXSTDBA_VARIABLE_LAUNCH_WORK_FOLDER, &sczLaunchFolder);

Dec 8, 2015 at 3:33 PM
That code all looks ok and matches the WiX 3.10 code. What message do you get in the logs? What makes you think it isn't working?
Dec 8, 2015 at 4:52 PM

I open an application that loads a CHM file, when I load the app from the Launch button the help file does not load.

When I start the app from the shortcut on the desktop then everything works correctly.

I can duplicate this effect if I remove the “start in” directory for the shortcut.