Nobody knows whatever about the topic?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-start-with-Burn-tp7579664p7579721.html
Sent from the wix-users mailing list archive at Nabble.com.
--
It is called paternity leave. Over now.
On Mon, Aug 6, 2012 at 11:48 AM, Porterfield, Tom wrote:
> http://wixtoolset.org/releases for releases since then.
>
> -Original Message-
> From: Bruce Cran [mailto:br...@cran.org.uk]
> Sent: Monday, August 06, 2012 2:23 PM
> To: wix-users@lists.so
I'm pretty sure this is documented in the WiX.chm.
On Mon, Aug 6, 2012 at 3:31 PM, Allan Neill wrote:
> Hi,
>
> I just got the task to move our product from VS 2008 to 2010. We were
> using WiX version 3.0. I upgraded to Wix 3.5 and when I build I get the
> following errors:
>
> C:\delivery\Dev\
H, that actually ends up removing all directories, pretty much every
Directory tag, no matter what the contents or what children it has.
I also tried:
But got the same effect.
-Original Message-
From: james rowson [mailto:jamesnrow...@yahoo.co.uk]
Sent: Saturday, 4 August 2012
Hi,
I just got the task to move our product from VS 2008 to 2010. We were using WiX
version 3.0. I upgraded to Wix 3.5 and when I build I get the following errors:
C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(38,0):
error LGHT0094: Unresolved reference to symbol
'
http://wixtoolset.org/releases for releases since then.
-Original Message-
From: Bruce Cran [mailto:br...@cran.org.uk]
Sent: Monday, August 06, 2012 2:23 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] No recent checkins on codeplex site
I noticed there haven't been any check
I noticed there haven't been any checkins at
http://wix.codeplex.com/SourceControl/list/changesets recently - the
last one was 18th June. Is there some script that should have been
pushing changes that's stopped working?
--
Bruce Cran
--
Hey Bruce,
Thought I'd let you know that I solved this by removing the VC10 merge modules
from our WiX project. The VC90 ones weren't causing a problem, however it was
the other processes on the machine that had a hold on the shared files in
System32 that caused the problem.
Seems Windows Inst
8 matches
Mail list logo