Deployment

[John Smith]

I am just learning about deployment (setup projects) in vb.net. Is there a
way to run an Executable during an Installation or at the end of an
installation?

I am trying to install a windows service through a deployment wizard just so
that I don't have to go through the trouble of running InstallUtil for every
server that I need to install it on. During installation I would like to
run an executable or batch file that would run the InstallUtil command.
Then a custom configuration utility would run to update my
ConfigurationSettings.ini file which the windows service relies on. Once
the ConfigurationSettings is saved it would start my service. Any
sites/samples/help would be appreciated.

Thanx in Advance,

atr2000

 

[Guest]

I am just learning about deployment (setup projects) in vb.net. Is there a
way to run an Executable during an Installation or at the end of an
installation?

I am trying to install a windows service through a deployment wizard just so
that I don't have to go through the trouble of running InstallUtil for every
server that I need to install it on. During installation I would like to
run an executable or batch file that would run the InstallUtil command.
Then a custom configuration utility would run to update my
ConfigurationSettings.ini file which the windows service relies on. Once
the ConfigurationSettings is saved it would start my service. Any
sites/samples/help would be appreciated.

Thanx in Advance,

atr2000

I've been trying to do that for some time now. One things that was
suggested is looking in the custom actions of the installer, but I couldn't
make head or tails of it. The route I'm taking is to look for the registry
entries that are needed for SysServices, then somehow making a call to net
start {servicename}, but haven't had much luck yet.

Jody

 

[EggHead]

Just add the exe to the custom actions.
I think the custom action runs after the installation.

Egghead

 

[stand__sure]

the advice is correct but given the wording of the original question, I
worry that there may be some confusion -- the exe-file that you add is the
Primary Output from the project -- not some other app.

 

[John Smith]

Yeah I realized my problem was that I needed to set the InstallerClass
within the Custom Actions to False.