Even with WIXUI_INSTALLDIR you can set the default to a per-user location,
and launching the app after installation generally also does not generally
require admin privs so that also does not prevent perUser. In that pure
perUser package, they would get an error if they tried to navigate to and
ins
Thanks thats certainly clarified it. My install is a 'WIXUI_INSTALLDIR' type so
from what I read here:
http://www.indigorose.com/webhelp/msifact/Concepts/Per-Machine_vs._Per-User_Installations.htm
that rules out perUser install. I also use a custom action to launch my app
after install and Vis
I ran the logo test on a clean system, so this is the only app that's been
installed/uninstalled after the OS and the tester. Is there any way that
windows could think it was still being referenced by another application?
Actually, I just thought of something else strange-in the notes for the
Is it as simple as the possibility that those Dlls might also have been
installed for use by another app?
Phil Wilson
-Original Message-
From: Chris Bardon [mailto:cbar...@computer-talk.com]
Sent: Friday, September 11, 2009 1:14 PM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-us
I'll just add (and risk stating the obvious) that if a limited user could
actually perform an install that changed areas on the system that are
restricted to administrators, then that would be one heck of a security hole.
Administrator credentials have to be supplied somewhere, whether it's an
I've been running a couple of tests with the Windows 7 logo kit, and one
warning that's coming up in the report looks like this:
Test case: Remove all non-shared files and folders.: PASS WITH WARNINGS
WARNING: This application failed to remove the following files during uninstall:
File
C:\Window
Per-machine is exactly that: all users on that machine. Anything that
affects more than the current user is supposed to require admin privileges
to accomplish (that is why opening the clock/calendar in the task bar on XP
requires admin privileges) as a basic tenant of machine stability (and
reducin
It's all about where you're deploying to and what CAs you're running.
If you're operating outside of the user's profile then you'll get a
UAC prompt if it's enabled.
2009/9/11 warne warne :
>
>
>
> Hi there,
>
> My setup is a perMachine (ALLUSERS=1) install which I set in the 'Package'
> element
Hi there,
My setup is a perMachine (ALLUSERS=1) install which I set in the 'Package'
element and thats fine.
Just wondering then, is there any way to get round vista's UAC for users
without admin rights ie 'Standard Users' ? They get the old "You do not have
sufficient priviliges etc" mes
If you have a bootstrapper that is marked in Vista as "requiresElevation"
the entire MSI will be elevated since the MSI APIs will be called from that
elevated context. There are several negative issues that can result from
that (you may discover that the reason you need elevation causes repair or
e
Hey Jon,
That is good to hear! I will mention to watch out with the time to do
costing for components with that many files. I imagine that a full install
of the MSI is taking over 15 minutes if you have more that 3000 files.
Additionaly, the only way you will be able to handle patching is to do so
In a "managed" or "elevated" install with a standard user, the UI sequence
runs with user privs. But if you elevate the user process then the whole
package runs elevated.
For example, you could have a setup.exe that is manifested to require elevation
before invoking the MSI. The user could t
Hi there
Please find below a link to a survey related to my PhD research work to
evaluate OSS usability improvement from OSS User's point of view.
It shall not not take more than 5 minutes of your precious time.
Your identity is neither required nor recorded. The participation is highly
valued
Rob Mensching just made the reply below and I don't want to hi-jack that
conversation, but I would like an explanation of that that statement.
Do we have control over what part of the install is elevated and if so,
how?
--
Roy Cha
That will only work if the target file is not in a per-machine directory
or you ran your entire MSI elevated (icky, icky, icky).
Adr!an Serafin wrote:
> Hi!
>
> Thank's for the response :) I need my own CA for some other things to ;)
> Besides I found solution. If anyone needs it:
>
> Overridabl
Thanks for your help Brian.
I have raised this on as a bug on sourceforge. I can get by without the -cg
switch which means I now have an automated build process which incorporates
Heat to generate the fragment, rather than our developers having to manually
update the fragments (we have 1000's
Hello,
Q_1 Your example for checking IIS:
Key='SYSTEM\CurrentControlSet\Services\W3SVC\Parameters'
My issue for checking db2 installation:
Key=? here come the path where db2 is installed on the machine?
Q_2 Your example: IIS6SPLEVEL >= "#6"
Which value come for DB2?
Ranganatha H C wrote:
>
>
17 matches
Mail list logo
