I ended up creating a custom action that creates vbs script that I launch
(which launches the URL) in my MSI
var tempString = GetSessionProperty(session, "CustomActionData", false);
var parts = tempString.Split(new[] { '|' });
var installPath = parts[0];
var webPortNumber = parts[1];
const string UrlString = "http://localhost:";;
var path = @installPath + "LaunchWebSite.vbs";
const string Quote = "\"";
if (Directory.Exists(installPath))
{
// Create a file to write to.
using (var sw = File.CreateText(path))
{
sw.WriteLine("Option Explicit");
sw.WriteLine("Dim wshShell");
sw.WriteLine("Set wshShell = CreateObject( " + Quote +
"WScript.Shell" + Quote + " )");
sw.WriteLine("wshShell.Run Trim( " + Quote + UrlString
+ webPortNumber + Quote + " ), 0, False");
sw.WriteLine("Set wshShell = Nothing");
}
}
Then in the bootstrapper I added:
LaunchTarget="$(env.SystemDrive)\inetpub\wwwroot\<addyourwebsitepath>\LaunchWebSite.vbs"
-----Original Message-----
From: Tobias Erichsen [mailto:[email protected]]
Sent: March-05-14 10:45 AM
To: [email protected]
Subject: [WiX-users] Burn LaunchTarget - possible to specify HTTP-URL?
Hi,
I was wondering if I could specify an HTTP-URI as LaunchTarget in my burn
boostrapper, as the user-interface for an application of mine is a local
webserver...
Best regards,
Tobias
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
