There would be only one elevation prompt in Burn and (by default) it happens
when you hit the Install button. If you write your own BA, then you can
force the elevation prompt earlier (but not later ) if you want.
This is great because the UI shows up quickly and the elevation prompt
happens when y
There are many kb articles about this - explore MS Help and Support and you'll
see this kind of thing:
http://support.microsoft.com/kb/292582
http://support.microsoft.com/kb/894510
The most common cause is a corrupt registry entry for one the standard folder
locations.
Phil Wilson
-
Maybe my memory is off but I think when you get a UAC prompt if you don't click
yes in 30 seconds-ish it comes back as don't elevate and then your install will
fail. My point is if they click yes and start installing .NET and let's say
that takes 5-10 minutes then it comes back and asks to elev
Eeesh, that's a ton of prereqs! Indeed, in your case 20 UAC prompts would
be unacceptable. I do wonder how you wound up with a 30 second timeout?
(What if installing on a slower computer and the prereq takes more time to
load?)
Our product's only chained prereq is .NET Framework 2.0, so we just
My typical bootstrapper installs between 10 and 20 prereqs. I can't imagine
each of those packages prompting for elevation. If you don't answer in 30
seconds or so it'll fail and the whole chain is broken. I don't see how I
can't
elevate up front. I also do matching LaunchConditions in
Familiarize yourself with
http://msdn.microsoft.com/en-us/library/ms724072(VS.85).aspx
If you don't want your entry to go in the 32-bit entry then you have to
specify Win64="yes" on your component, but this makes / requires your MSI to
be supporting 64-bit.
32-bit apps don't need to worry about W
I thought about this but decided against it for some of the security reasons
you outline; I did not think it appropriate for the UAC prompt to appear
immediately upon running the bootstrapper. The UAC prompt really should not
be presented until the user clicks the "Install" button in the UI to
act
Perhaps you are right about the legacy="true" aspect and the need to
manually scan for new hardware after an upgrade if the device was plugged
in. At any rate, for the moment - I already added a custom action that
follows MSKB http://support.microsoft.com/kb/259697 and placed it after
MsiProcessDr
Adding some more context, hopefully someone has encountered this error and has
some insight.
I am only getting this error "Error 1324. The folder path '?' contains an
invalid character." when I am adding a file (Assembly) to the GAC on the
machine.
The following is the WiX code:
How does it handle the case where a user could select per user or per
machine?
Does it cache and install or does it install then cache and update sourcelists?
( or any other interesting questions that didn't occur to me to ask. )
Christopher Painter, Author of Deployment Engineering Blog
Ha
When I installed this version of wix on my machine, visual studio fails to
load my solution any more. VS prompts me to convert my solution. Is there
any property change made in wix 3.5.2325.0, that I should include in my wix
projects built on wix 3.5.1923?
thanks for your help,
sangeeta
--
View
Burn uses LocalAppDataFolder and picks the correct one (per-machine or
per-user) depending if the package is per-machine or per-user.
On Tue, Nov 30, 2010 at 5:09 PM, Christopher Painter <
chr...@deploymentengineering.com> wrote:
> Yes. Althought I believe it's better to use PackageCode rather t
Hi,
I'm doing an upgrade of a product. The WIX in the original installer
(1.0) for one relevant component looked like this:
In the WIX for the new installer (1.1), I've removed the Sample
directory and the file - I don't want them installed for a fresh 1.1
install. However, during
Thanks. This build has fixed the problem.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/UninstallCertificates-action-fails-to-remove-certificate-from-iis-tp5788876p5792274.html
Sent from the wix-users mailing list archive at Nabble.com.
http://msdn.microsoft.com/en-us/library/aa384232.aspx
Your MSI is built for x86 platforms. Build it for x64 if you don't want
it to do that on x64 platforms.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design
I am using a 64-bit Windows 7 machine. I am installing our software with
the following script for the registry:
On the 64 bit machine the registry value is coming back as:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\My Company
I'm using WiX 3.6 (actually 3.6.112.0) with VS2010. It is great!
WiX team has done a very good job of integrating WiX into VS.
Bob
From: Saurabh Ashok Chandra Sharma (Accenture) [v-sau...@microsoft.com]
Sent: Tuesday, November 30, 2010 1:53 AM
To: wix-us
http://msdn.microsoft.com/en-us/library/aa367748.aspx
Set it yourself if Windows Installer is getting it wrong. I've not seen
it happen for my packages as yet but I think it happens with very large
packages more often & our largest install is <1 GB.
Palbinder Sandher
Software Deployment & IT Adm
I had the same problem. First of all you must know, that installed features
has different state, even if they marked "Install from local source". You
need to add a new rule to condition, what will check state of the installed
freature. To check state of installig feature use & symbol, to check sta
19 matches
Mail list logo
