But what actually is the difference in the outcome between not setting
InstallScope and setting it to perMachine? Actually (at least on my Vista
laptop) it seems what I am getting is always an elevated perMachine install.
So why setting it?
> -Original Message-
> From: Blair [mailto:os...@
Blair,
once more, thank you for this interesting insights!
So in short: perMachine will work everywhere the same, but perUser will work
differently for Windows 7 to all the rest - on Windows 7 the MSI5 will
automatically provide "privately mapped" locations, while on all other
platforms the .msi
> -Original Message-
> From: Wilson, Phil [mailto:phil.wil...@wonderware.com]
> Sent: Donnerstag, 5. November 2009 23:33
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Per User / Per Machine
>
> InstallPrivileges is to do with whether Windows can sh
Guten Tag Markus Karg,
am Freitag, 6. November 2009 um 10:05 schrieben Sie:
> As a result, it is up to the *.msi author* to decide
> *where* the software will go. I don't think that administrators will love
> the idea that each .msi has some other, fancy location (they had been so
> glad about the
Hi Blair,
It is great! I tried the MsiCuu2.exe to remove the broken installation. And my
dll works.
However, this dll will decide to start the custom action or not:
if (needToStart)
{
value = ::MsiDoActionW(hInstaller,"StartMyCA");//"StartMyService"
}
But I have more custom
Hi wix-users,
I developed one setup msi. And I want it to be upgradable. The
requirement is:
1. Version 1 install to PathA. (New Install)
2. Version 2 install to PathB. (New Install)
3. Version 3 install to PathA. (Upgrade)
The setup meets the requairment. However, when I perform the above
a
6 matches
Mail list logo
