Hi!
Since I don't use elevation within my systray application, I don't have
any problem with tray shut-down on uninstall. However, AFAIK on Vista, a
process with lower-level privilege cannot:
a) Perform a window handle validation of higher process privilege.
b) Use the SendMessage or PostMessage
Вашему вниманию предлагаем базы данных:
Внешнеэкономическая деятельность России и Украины 1999- 2007 год.
Юридические лица и предприятия Москвы и РФ (полная информация) по 2007г 2000
руб. Банковские проводки (данные РКЦ ЦБ) 2003-2005год 6000 руб. Пенсионный
фонд (данные о работод
I think the issue with ProcessMessage from within a DoAction call is that the
ProcessMessage will be executed on the UI thread. The InstallExecuteSequence
runs in a different process. I think with MSI 2.0 and before, the call could
result in a deadlock.
BTW my logging using the ROT is rathe
I once played with something similar using .NET remoting to allow EXE CA's to
communicate with the MSI handle. Eitherway, it's giving me horrible
flashbacks to how InstallScript use to have DCOM/ROT problems. It seems
incredibly complicated for something that *should* be simple if the MSI tea
I have often wanted to log in UI sequence when a DoAction control event is
fired. Basically you need to queue up some logging messages in memory and the
dump them out when the dialog sequence is finished.
One way this can be done is to run an async custom action before the frist
dialog is la
Use a conditional expression based on the feature ( or component ) action
state. ( &FEATURE=xxx ) as shown here:
http://msdn2.microsoft.com/en-us/library/aa368012.aspx
Fox Cutter <[EMAIL PROTECTED]> wrote:
I'm working on an install that has a set of custom actions working on
files that
I'm working on an install that has a set of custom actions working on
files that are only installed for one given feature, if the feature is
not installed the custom action still tries to run and I get an error.
Is there any way to limit a custom action to only run as part of a
feature?
--Fox Cutt
It's documented by the DoAction ControlEvent.
http://msdn2.microsoft.com/en-us/library/aa368322(VS.85).aspx
"Note that custom actions launched by a DoAction ControlEvent can send a
message with the Message Method, but cannot send a message with
MsiProcessMessage. On systems prior to
::MsiProcessMessage() doesn't work when your action gets called from a button
click. I don't know where or even if that is documented.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of dB.
Sent: Tuesday, April 15, 2008 17:23
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] W
I have a custom action that I am running within the UI sequence
(immediate, user clicks on a button, custom action runs). Logging isn't
working from it! I can log without any problems when the same custom
action runs deferred.
It's not the first time I see this. Any ideas? The code is
straight
Dale,
Normally, you should stay away from scripting custom actions if what you want
can be done without using custom action. Have you tried escaping curly braces?
[\{]
and
[\}]
Alex
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dale Quigg
Sent:
>> If you look very carefully, you see that a set of braces around the
>> "else" portion of the command have been stripped.
>> I don't understand why most of the braces come though fine, but
>> these few don't.
> From: Alexander Shevchuk [EMAIL PROTECTED]
>
> Formatted data type
> http://msdn2.m
I get the popup on both 2.0 and 3.0 that I need Visual Studio Standard
edition or higher, but I'm on VS 2008 Pro edition. I'm also on Vista 64...
is that the issue? Thanks...
-
This SF.net email is sponsored by the 2008 JavaO
Cool Chris, thanks! :) That would be exactly what I needed.
A
Amy Rosewater
Sr. Development Programmer/Analyst
SPECTRUM Human Resource Systems Corporation
707 Seventeenth Street, Suite 3800
Denver, CO 80202-3438
(303) 592-3403 Phone
(800) 334-5660 Toll Free
(303) 592-3233 Fax
[EMA
You want to read the MSI SDK help topic "Installing Multiple instances with
Instance Transforms"
In there you'll find:
The easiest way to initiate a maintenance installation, and reinstall an
instance, is to reference the product code of the instance. If you initiate the
maintenance
I have an install with embedded transforms that are created through the
InstanceTransforms element and child Instance elements.
Original Product
I am able to install a second instance of my application by typing the
following command:
msiexec /i myinstaller.msi TRA
I see the same thing with WiX 2.0.5325.0. I don't use the Permanent
attribute, but the changes are never removed.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Darryl
Hnatiuk
Sent: Tuesday, April 15, 2008 11:04 AM
To: wix-users@lists.sourceforg
Hello all,
We are currently using WiX version 3.0.4014.0 and have been tring to get the
XmlFile action working, and for the most part have everything working fine.
However, one setting we've been having trouble with is the "Permanent"
setting. From the WiX documentation, my understanding is that t
Pehaps this is more of a Windows Installer question than WiX but I authored
my installer using WIX 3 so I am posting here.
I have an patched installation where only some of the features are
installed. When I remove the patch through add/remove programs or a call to
msiexec, the default features g
Hi,
Is it possible to create a new (text) file during the
install?
In my case I want to create an xml file (configuration
file like) which contains a few elements with values from some WiX
defines, e.g. if the following could be expressed:
$(var.CompanyName)
or
Formatted data type
(http://msdn2.microsoft.com/en-us/library/aa368609(VS.85).aspx):
"If a substring is enclosed in curly braces ({ }) and it contains one or more
property names enclosed in square brackets ([ ]) then, if all the property
names are valid, the text (with the resolved substitution
trying to figure out what was wrong (see my previous mode: basically my
attempt to upgrade with an .msi never actually copied any files or wrote
registries or ran the app concluding the setup... basically didn't work)
so i went back to the SOURCE : gabor deak janos's tutorial (albeit that's
wix
Can anyone give an insight on killing a systray process launched using a CA
which has been made
"deferred" and no-impersonate to get it running with UAC enabled on Vista??
--
View this message in context:
http://www.nabble.com/How-to-kill-a-process-launched-with-elevated-privileges--tp16700351p
I am facing some issues when i make a call to systray.exe elevated
automatically as follows:
1
1
NOT
Installed
I get the exe launched successfully with UAC on[By changing the custom
action to "deferred" and "no-impersonate"].But when i try to kill the
process during uninst
i've built an .msi that is supposed to be able to upgrade older versions.
i'm pretty sure my handling of the update code, the product version and
package id, and the upgrade tag as i should.
my problem is that if i run the msi with the
msiexec /i mysetup.msi REINSTALL=ALL REINSTALLMODE=omus
comma
25 matches
Mail list logo
