ke setting the executable's working directory to that folder.
It looks like you need a verbose log. Experimentally you can keep moving the
custom action down the sequence until it starts failing. Or try after
RemoveFolders to see if that's where it starts to fail.
Phil
-Original
in that area of the uninstall.
Phil
-----Original Message-
From: Brownfield, Cory [mailto:cbrownfi...@aeci.org]
Sent: Friday, May 10, 2013 7:37 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] When are elevated permissions dropped?
To illustrate a problem I'm having with a re
To illustrate a problem I'm having with a real project, I created a test script
that runs a custom action that requires elevated privileges during uninstalls.
If I configure it to run before "InstallFinalize" (deferred, no impersonation),
the uninstall fails to complete. The event log says "A
My team has decided to add only the top-level project reference to the WiX
project in each solution. We typically have simple builds where each solution
has one WiX project that builds a single MSI. So if we have a service
solution, we will be adding a single project reference to our WiX proje
36530.aspx
On Fri, Jan 21, 2011 at 12:20 PM, Brownfield, Cory
wrote:
> It *was* a vbscript.dll registration issue. I followed the
> instructions here
> http://blogs.msdn.com/b/astebner/archive/2007/06/07/3151752.aspx
> (following the 64-bit bits) to fix the problem. I have no idea h
build machine(s) (at
least during builds).
-Blair
-----Original Message-
From: Brownfield, Cory [mailto:cbrownfi...@aeci.org]
Sent: Tuesday, January 18, 2011 12:18 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] First build gives ICE errors; subsequent builds
don't
Setup:
Windows
Setup:
Windows 7 64-bit (fully patched)
Visual Studio 2010 Ultimate
WiX 3.5 build 2430 (latest weekly)
I've recently noticed a problem with all my WiX projects. Trying to
build after a change or after a clean, I get a set of ICE errors. So
rebuilding always gives me these errors and follow
I'm using WiX version 3.0.4617.0.
A component can have its GUID defined like this : Guid="*" if under a
standard directory. Here's a portion of the error message returned when
trying to install to a nonstandard location:
"Since this path is not rooted in one of the standard directories (like
Pro
8 matches
Mail list logo