--On Thursday, August 22, 2013 4:59 PM -0400 Bob Arnson
wrote:
> On 18-Aug-13 18:24, Kenneth Porter wrote:
>> Burn v3.6.2816.0, Windows v6.1 (Build 7601: Service Pack 1)
> That's a beta build of WiX v3.6. Try upgrading to the RTM version or
> v3.7 RTM.
I just pulled
--On Monday, August 19, 2013 10:50 AM -0700 Kenneth Porter
wrote:
> Aha. I ran MSBuild in .\tools and it ran both 32 and 64 bit versions of
> sn to exclude everything from verification, and now the non-elevated
> build seems to be proceeding to completion.
I tried this on a seco
--On Monday, August 19, 2013 10:25 AM -0700 Blair Murri
wrote:
> wix-devs mailing list has more history regarding building the toolset.
Thanks. Just signed up for that.
> src\tools needs to be built once elevated before you build the toolset.
> You don't need to use OFFICIAL_WIX_BUILD if you w
I want to debug the problem I'm having with ExePackage/@DetectCondition so
I cloned the current git trunk and attempted to run MSBuild on it. I'm new
to assembly signing but I think I have my head around the principles from
reading a bunch of blogs about it, including the need to use the 64 bit
--On Monday, August 19, 2013 8:01 AM -0700 Phill Hogland
wrote:
> It seems like you would want to use DetectCondition to determine if the
> package already exists and InstallCondition to determine when you want to
> launch the exe.
If the prerequisite package is not installed, I want to run its
--On Monday, August 19, 2013 7:42 AM + Neil Sleightholm
wrote:
> Just to be clear if DetectCondition is true it means the package is
> already installed. In your case "ub5Present" has a value of
> 'C:\Windows\system32\' does that mean it isn't installed?
Empirically, it appears that utils:C
--On Sunday, August 18, 2013 10:05 PM + Neil Sleightholm
wrote:
> Probably worth checking the logs to see that the values you are checking
> are.
With no package installed:
[0688:0740][2013-08-16T09:39:59]: Setting string variable 'ub5Present' to
value ''
[0688:0740][2013-08-16T09:39:59]:
--On Sunday, August 18, 2013 1:45 PM + Neil Sleightholm
wrote:
> I think you should use DetectCondition='ub5Present' as the value won't be
> set unless the component is found.
I tried that and now the condition is always true. The installer is run
even when it's already installed, and goes
The following bundle installation never runs even when the package is
detected absent (ub5present is set to ""). What's wrong with my syntax? It
seems that the DetectCondition value always evaluates to true.
...
-
What do I need to remove to repair a damaged OS package database? Ie. if
uninstall from Add/Remove programs fails, what do I do manually to manually
remove the package from the database? (I can manually delete the package
itself, of course.)
Is it sufficient to remove the package's cache direct
--On Wednesday, April 18, 2012 3:19 PM +0200 Dirk Räder
wrote:
> Although I'm not a lawyer, as far as I am concerned, WiX makes use of
> CPL-licensed components only during compilation / build time.
Custom actions might use WiX code, so you may end up bundling WiX scripts
or executables that g
What does it mean for a file to be versioned?
I'm getting the following error, using 3.6:
Product.wxs(42,0): error LGHT0367: The Component/@Guid attribute's value
'*' is not valid for this component because it does not meet the criteria
for having an automatically generated guid. Components wit
I'm looking for example packaging for a C++ DLL and its import library and
headers. I'm providing a sample program and some documentation. It seems
like this would be a common kind of package so an example illustrating how
to structure it would be great.
--On Friday, April 13, 2012 10:12 AM -0700 Kenneth Porter
wrote:
> I ran the wix36.exe from the Codeplex website and see the package
> installed on Vista 64 Ultimate under C:\Program Files (x86). But I don't
> see the WiX project option in the VS2010 New Project dialog. Did I mi
I ran the wix36.exe from the Codeplex website and see the package installed
on Vista 64 Ultimate under C:\Program Files (x86). But I don't see the WiX
project option in the VS2010 New Project dialog. Did I miss a step? I have
VS2010 installed to G:\msvs10 (on an external USB drive that I keep al
15 matches
Mail list logo
