PDA

View Full Version : add custom action before user interfaces show up



NewsArchive
12-07-2001, 01:00 AM
I am doing a standard installation using Developer 7.0.

I am trying to add a custom action to the sequence-execute, and I would like
that action to execute before any interfaces show up. I I add my action
after ISStartUp, then the welcome, license agreement, choose destination
location, start copying files show up before my action gets executed. If I
add my custom action before ISStartUp, then my action does not get executed
at all.

I would like to understand the sequence of action and how do they integrate
with the userinterfaces in the standard installation.

I appreciate any help

Thanks a lot

Jorge L. Fiallega

NewsArchive
12-07-2001, 01:00 AM
Jorge:

What do you mean by "a standard installation", do you mean by "standard
project type"?
For a standard project, you don't need a custom action under this situation!

Forget about the InstallUISequence, it is almost useless for standard
project. You can simply override the OnFirstUIBefore event, add whataver
code you want to add before the SdWelcome call.

Don't use custom action.

For a basic MSI installation (Pure MSI based), add the action before Welcome
dialog should work (Between ISStartup and Welcome dialog). The action has to
be in InstallUISequence.

Fei

"Jorge L. Fiallega" <jorge.fiallega@insurance.sungard.com> wrote in message
news:3c10f82c$1@news.installshield.com...
> I am doing a standard installation using Developer 7.0.
>
> I am trying to add a custom action to the sequence-execute, and I would
like
> that action to execute before any interfaces show up. I I add my action
> after ISStartUp, then the welcome, license agreement, choose destination
> location, start copying files show up before my action gets executed. If I
> add my custom action before ISStartUp, then my action does not get
executed
> at all.
>
> I would like to understand the sequence of action and how do they
integrate
> with the userinterfaces in the standard installation.
>
> I appreciate any help
>
> Thanks a lot
>
> Jorge L. Fiallega
>
>
>

NewsArchive
12-07-2001, 01:00 AM
Sorry, you are correct, I meant a standard project type.

I am trying to take advantage of the nested installation custom action,
which I want it to happen prior to the welcome message.

So if I am using a standar porject I can not take advantage of the nested
installation custom type (I believe Type 23)? I wanted to transition from
professional 6.3 to developer 7.0 and I feel that if I keep programming
using OnFirstUIBefore, and so on why should I update to Developer 7.0?

Thanks for your response Fei.

Thanks

Jorge L. Fiallega

"mingbiaofei" <mf@installshield.com> wrote in message
news:<3c10f99d$1@news.installshield.com>...
> Jorge:
>
> What do you mean by "a standard installation", do you mean by "standard
> project type"?
> For a standard project, you don't need a custom action under this
situation!
>
> Forget about the InstallUISequence, it is almost useless for standard
> project. You can simply override the OnFirstUIBefore event, add whataver
> code you want to add before the SdWelcome call.
>
> Don't use custom action.
>
> For a basic MSI installation (Pure MSI based), add the action before
Welcome
> dialog should work (Between ISStartup and Welcome dialog). The action has
to
> be in InstallUISequence.
>
> Fei
>
> "Jorge L. Fiallega" <jorge.fiallega@insurance.sungard.com> wrote in
message
> news:3c10f82c$1@news.installshield.com...
> > I am doing a standard installation using Developer 7.0.
> >
> > I am trying to add a custom action to the sequence-execute, and I would
> like
> > that action to execute before any interfaces show up. I I add my action
> > after ISStartUp, then the welcome, license agreement, choose destination
> > location, start copying files show up before my action gets executed. If
I
> > add my custom action before ISStartUp, then my action does not get
> executed
> > at all.
> >
> > I would like to understand the sequence of action and how do they
> integrate
> > with the userinterfaces in the standard installation.
> >
> > I appreciate any help
> >
> > Thanks a lot
> >
> > Jorge L. Fiallega
> >
> >
> >
>
>

"mingbiaofei" <mf@installshield.com> wrote in message
news:3c10f99d$1@news.installshield.com...
> Jorge:
>
> What do you mean by "a standard installation", do you mean by "standard
> project type"?
> For a standard project, you don't need a custom action under this
situation!
>
> Forget about the InstallUISequence, it is almost useless for standard
> project. You can simply override the OnFirstUIBefore event, add whataver
> code you want to add before the SdWelcome call.
>
> Don't use custom action.
>
> For a basic MSI installation (Pure MSI based), add the action before
Welcome
> dialog should work (Between ISStartup and Welcome dialog). The action has
to
> be in InstallUISequence.
>
> Fei
>
> "Jorge L. Fiallega" <jorge.fiallega@insurance.sungard.com> wrote in
message
> news:3c10f82c$1@news.installshield.com...
> > I am doing a standard installation using Developer 7.0.
> >
> > I am trying to add a custom action to the sequence-execute, and I would
> like
> > that action to execute before any interfaces show up. I I add my action
> > after ISStartUp, then the welcome, license agreement, choose destination
> > location, start copying files show up before my action gets executed. If
I
> > add my custom action before ISStartUp, then my action does not get
> executed
> > at all.
> >
> > I would like to understand the sequence of action and how do they
> integrate
> > with the userinterfaces in the standard installation.
> >
> > I appreciate any help
> >
> > Thanks a lot
> >
> > Jorge L. Fiallega
> >
> >
> >
>
>

NewsArchive
12-07-2001, 01:00 AM
Jorge:

The nested install supported by MSI (23 or whataver) is very very limited.
We do support that and you can use it. What type of child installation you
have? If it is a standard project also created with 7.0, then you can use
"DoInstall", otherwise, use "LaunchAndWait" to call the setup.exe (or
msiexec.exe, depending on your sub project type) directly.

You can do this ANYWHERE you want. For MSI's native support of nested
install, the child project loses its UI and is messed into the main
installation. And the fact is that, you can NOT do that before the welcome
message. (A nested installation shares the same user interface and logging
settings as the main installation : MSI Help). Maybe I am wrong.

Good luck.
Fei

"Jorge L. Fiallega" <jorge.fiallega@insurance.sungard.com> wrote in message
news:3c11125d@news.installshield.com...
> Sorry, you are correct, I meant a standard project type.
>
> I am trying to take advantage of the nested installation custom action,
> which I want it to happen prior to the welcome message.
>
> So if I am using a standar porject I can not take advantage of the nested
> installation custom type (I believe Type 23)? I wanted to transition from
> professional 6.3 to developer 7.0 and I feel that if I keep programming
> using OnFirstUIBefore, and so on why should I update to Developer 7.0?
>
> Thanks for your response Fei.
>
> Thanks
>
> Jorge L. Fiallega
>
> "mingbiaofei" <mf@installshield.com> wrote in message
> news:<3c10f99d$1@news.installshield.com>...
> > Jorge:
> >
> > What do you mean by "a standard installation", do you mean by "standard
> > project type"?
> > For a standard project, you don't need a custom action under this
> situation!
> >
> > Forget about the InstallUISequence, it is almost useless for standard
> > project. You can simply override the OnFirstUIBefore event, add whataver
> > code you want to add before the SdWelcome call.
> >
> > Don't use custom action.
> >
> > For a basic MSI installation (Pure MSI based), add the action before
> Welcome
> > dialog should work (Between ISStartup and Welcome dialog). The action
has
> to
> > be in InstallUISequence.
> >
> > Fei
> >
> > "Jorge L. Fiallega" <jorge.fiallega@insurance.sungard.com> wrote in
> message
> > news:3c10f82c$1@news.installshield.com...
> > > I am doing a standard installation using Developer 7.0.
> > >
> > > I am trying to add a custom action to the sequence-execute, and I
would
> > like
> > > that action to execute before any interfaces show up. I I add my
action
> > > after ISStartUp, then the welcome, license agreement, choose
destination
> > > location, start copying files show up before my action gets executed.
If
> I
> > > add my custom action before ISStartUp, then my action does not get
> > executed
> > > at all.
> > >
> > > I would like to understand the sequence of action and how do they
> > integrate
> > > with the userinterfaces in the standard installation.
> > >
> > > I appreciate any help
> > >
> > > Thanks a lot
> > >
> > > Jorge L. Fiallega
> > >
> > >
> > >
> >
> >
>
> "mingbiaofei" <mf@installshield.com> wrote in message
> news:3c10f99d$1@news.installshield.com...
> > Jorge:
> >
> > What do you mean by "a standard installation", do you mean by "standard
> > project type"?
> > For a standard project, you don't need a custom action under this
> situation!
> >
> > Forget about the InstallUISequence, it is almost useless for standard
> > project. You can simply override the OnFirstUIBefore event, add whataver
> > code you want to add before the SdWelcome call.
> >
> > Don't use custom action.
> >
> > For a basic MSI installation (Pure MSI based), add the action before
> Welcome
> > dialog should work (Between ISStartup and Welcome dialog). The action
has
> to
> > be in InstallUISequence.
> >
> > Fei
> >
> > "Jorge L. Fiallega" <jorge.fiallega@insurance.sungard.com> wrote in
> message
> > news:3c10f82c$1@news.installshield.com...
> > > I am doing a standard installation using Developer 7.0.
> > >
> > > I am trying to add a custom action to the sequence-execute, and I
would
> > like
> > > that action to execute before any interfaces show up. I I add my
action
> > > after ISStartUp, then the welcome, license agreement, choose
destination
> > > location, start copying files show up before my action gets executed.
If
> I
> > > add my custom action before ISStartUp, then my action does not get
> > executed
> > > at all.
> > >
> > > I would like to understand the sequence of action and how do they
> > integrate
> > > with the userinterfaces in the standard installation.
> > >
> > > I appreciate any help
> > >
> > > Thanks a lot
> > >
> > > Jorge L. Fiallega
> > >
> > >
> > >
> >
> >
>
>

Lion_cl
07-26-2006, 09:00 AM
please, help me!

I need to run MSDE installation (SqlRun01.msi) from my MSI project if user select it in my own dialog. i have write some script to show dialog and returning selection ("MSDE" or "Existing SQL Server"). But i need to install MSDE when user select it before SQL Scripts runs.

I will look forward to any response!

Thanks,
Lion_cl.