On Sun, 26 Sep 2010 17:44:51 -0400
Bob Arnson wrote:
> InstallScope doesn't support per-user, elevated packages. Just omit
> InstallPrivileges (defaults to elevated) and don't set ALLUSERS.
Thanks, that's one combination I hadn't thought of trying. When I
removed both InstallScope and InstallPr
On 26-Sep-10 17:28, Bruce Cran wrote:
> I had hoped that would work, but it doesn't seem to. The combination of
> InstallPrivileges="elevated" and InstallScope="perUser" doesn't result
> in any elevation prompt (and the "Install" button in the MSI doesn't
> have a UAC shield).
InstallScope doesn
On Sun, 26 Sep 2010 16:13:59 -0400
Bob Arnson wrote:
> You need to set Package/@InstallPrivileges to elevated (or leave it
> off). Otherwise, WiX marks the package for "real" per-user operation,
> which won't ask for elevation and can't write to Program Files.
>
I had hoped that would work, b
On 24-Sep-10 15:55, Bruce Cran wrote:
> which is written using WiX 3.5 but I just get a permission denied error
> if I try and do a perUser installation which installs to
> ProgramFilesFolder - as I know I should do! As far as I know I can't
You need to set Package/@InstallPrivileges to elevate
Hi,
I'm trying to do a major upgrade of a product which was installed
per-user but which installed files into ProgramFilesFolder. The
previous installer was authored using the Visual Studio Deployment
project and defaulted to a perUser installation (with the option of
installing perMachine) - but
5 matches
Mail list logo
