Bogdan
6/20/2007 1:18:00 PM
As Phil suggested, you can create your own custom action (exe or dll) that
runs the existing exe. I use dll custom action because I need to interact
with msi. Exe custom action is somewhat easier because you do not need to
deal with msi at all and you can easily test it on its own. Your custom
action could be as simple as a single call to CreateProcess() or
ShellExecute().
Bogdan
"Tony Leung" <lianghf2000@hotmail.com> wrote in message
news:eCdHceosHHA.2268@TK2MSFTNGP05.phx.gbl...
> Thank you.
> But how can we run an existing exe on the target system?
>
> "Phil Wilson" <phil.wilson@wonderware.something.com> wrote in message
> news:%23GPiaC7pHHA.4544@TK2MSFTNGP02.phx.gbl...
>> That's correct - Visual Studio offers a subset of what's in MSI, and that
>> particular built-in custom action isn't available (run an existing exe on
>> the target system) but you can write your own custom action to run it.
>> --
>> Phil Wilson
>> [MVP Windows Installer]
>>
>> "Bogdan" <nouser@nodomain.com> wrote in message
>> news:%23FkMMhtpHHA.960@TK2MSFTNGP03.phx.gbl...
>>> I'm not sure if I got it right but according to the on-line docs Windows
>>> installer allows you to run exe on user's machine (i.e. an exe that is
>>> not included in a given setup project). I think that this is custom
>>> action type 50. I can't figure out how to add such exe to my setup
>>> project in VS. It seems that I can only add files that are included in
>>> the project.
>>>
>>> Any help will be appreciated.
>>> Thanks,
>>> Bogdan
>>>
>>>
>>>
>>
>>
>