No, you've hit it. The straight forward workaround is to add
true to your project file.
Fixing the root issue is something I'll do first thing in the WiX v3.8
branch. Unfortunately, that work around will be necessary when using WiX
v3.7 in VS2008.
On Mon, Dec 31, 2012 at 6:52 AM, Maillet, Ed wr
Hi Jim,
It is a bug in 3.6 that I logged. I am not sure if it will be fixed in 3.7
Cheers and Happy New Year,
Steve
-Original Message-
From: J Rao [mailto:jr...@live.com]
Sent: December-26-12 2:59 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] No progress in msi progressba
3.5 SP1 is installed. I turned on the fusion log and found the entry below. Not
quite sure what to make of it.
Running the candle.exe command-line that VS2008 produces directly works with
entries indicating v4.0.30319 is being used.
So this *feels* like, VS2008 is using CLR2 and candle.exe wants
FWIW, you might want to leave open the possibility of InstallShield *AND*
WiX. I find that the two compliment each other nicely in agile /
democratization scenarios.
I'm always available for a telephone chat for anyone who'd like to know
what I mean by this.
--
Wix is open source. If you need a feature urgently, you're welcome to take
the source code and implement a solution yourself :) Otherwise it's a case of
hoping someone on the WiX team (or some other contributor) takes it on.
-Original Message-
From: Kannan24 [mailto:skan...@syncfusion.com]
Hi Peter,
I was created the feature request on 10th July, but no progress still. Could
you please follow up this feature, since we have close to release.
Thanks,
Kannan
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-MsiPackage-and-DisplayIn
6 matches
Mail list logo
