JosephLee wrote:
> I have the same problem. And now i have something even more serious. In my
> package, i have something out of the installer's control, just an service
> have registries self-registered. When I do an maintenance using the package,
> just like "Remove" action, but the UAC credentia
hi,
I have the same problem. And now i have something even more serious. In my
package, i have something out of the installer's control, just an service
have registries self-registered. When I do an maintenance using the package,
just like "Remove" action, but the UAC credentials won't prompt, an
Please keep /wix-users/ on the thread.
Deily, Don wrote:
I'm having the same problem as "Gareth at Serif": In Vista, my installer has properties
that cause "Ignoring disallowed property" messages.
My question to you is: How do I use your suggested grammar
"Property/@Secure="yes"" ? Is that h
Gareth at Serif wrote:
> I'm not sure what you require by way of an example.
Well, remember I don't have your packages or your logs or your apps.
Raymond Chen calls it "psychic debugging."
> Now, the two events will be obviously different because the first will
> trigger a UAC prompt as soon a
I'm not sure what you require by way of an example. In my observations...
- Make an MSI package of several features/components.
- Make a bootstrapper for your MSI with "setup" in the name.
- Install the package.
- Run the setup on Vista, select Repair and save the log file (automatically
created
Gareth at Serif wrote:
> Thanks for your info, but how do you make Component properties 'secure' so
> that the server side can use them? I may have used the wrong termiollogy
> there... I mean that the location of each component is listed as a "Property
> Change" on installs where I get the UAC pr
Hi Bob,
Thanks for your info, but how do you make Component properties 'secure' so
that the server side can use them? I may have used the wrong termiollogy
there... I mean that the location of each component is listed as a "Property
Change" on installs where I get the UAC prompt, but disallowed
Gareth at Serif wrote:
> there is no UAC prompt until much later on and the information being passed
> to the client side is greatly reduced and potentially detremental to the
> expected behaviour of later custom actions.
>
You can mark properties as Secure="yes" to get them passed to the serve
Hi Rob,
I've started to see some peculiar results due to priveledge issues on Vista
and found myself back in this thread. I find, as I think you have, that
once the app in question is installed, the elevation being passed to the
client side of the install differ greatly depending on how you chos
That's what I'm doing. My bootstrapper runs with asInvoker elevation
requirements. The UAC happens
when Windows Installer changes from client-side to server-side during the
install. I also find
that running an MSI directly doesn't show the UAC prompt until it switches to
the server-side.
I find that the msi file extension tells Vista that the process requires
elevation and you get the UAC prompt before the UI Sequene begins.
Therefore, by the time you get to your 'Install' button with the potential
to display your UAC Shield, the install doesn't require elevation (as it all
ready
I'm still not sure I get it. I don't see why MsiRunningElevated is set so
early on uninstall,
especially since it obviously isn't. It gives you a UAC prompt later on. As
for the link you sent
me, I didn't really see anything that explains what I'm seeing.
Rob
Stefan Pavlik wrote:
> Stefan
Stefan Pavlik wrote:
> But when you check the uninstallation log you will see that the
I meant:
But when you check the maintenance installation log you will see...
--
Stefan Pavlik | [EMAIL PROTECTED]
Whitestein Technologies s.r.o. | www.whitestein.com
Panenska 28 | 811 03 Bratislava | Slovak Re
Hi Rob,
I have the same experience with Repair and Remove buttons.
But I think it is due to MsiRunningElevated property.
If you check the logs you will see that during first installation
this property is set after you confirm the elevation prompt (from
the server side - 'MSI (S)' is in the beginn
14 matches
Mail list logo
