By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,740 Members | 854 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,740 IT Pros & Developers. It's quick & easy.

setup program

P: n/a

i need a refresher.

i've created setups in the past that don't have the following problem. i
need help remembering the proper settings to correct the problem.

the setup i have includes an installer class which hooks into the after
install event. setup itself installs a main application and a couple of
others that detect the installation and configuration of
applications/components that the main application will use...i.e. msde or
ado or ...etc., etc.... if they are not installed they will be and if they
aren't configured, they will be.

anyway the installer class's after install event shell's out to an exe that
does all of this. everything works fine but, the installer class shows up in
the root application install directory (installer.dll). in addition to this,
there is another file there called installer.State.

i'd like to keep the functionality that i currently enjoy but not leave such
residue (installer.dll and installer.State). how do i use the files in the
setup application whilst not leaving them on the hard drive after all is
said and done.

tia,

me
Nov 21 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hi,

You can use a merge module to install mdac

http://support.microsoft.com/default...;EN-US;q320788

In general take a look at custom actions to add the functions
you want.

http://msdn.microsoft.com/library/de...stomaction.asp

Ken
----------------------
"" <a@b.com> wrote in message news:lf*************@fe06.lga...
i need a refresher.

i've created setups in the past that don't have the following problem. i
need help remembering the proper settings to correct the problem.

the setup i have includes an installer class which hooks into the after
install event. setup itself installs a main application and a couple of
others that detect the installation and configuration of
applications/components that the main application will use...i.e. msde or
ado or ...etc., etc.... if they are not installed they will be and if they
aren't configured, they will be.

anyway the installer class's after install event shell's out to an exe that
does all of this. everything works fine but, the installer class shows up in
the root application install directory (installer.dll). in addition to this,
there is another file there called installer.State.

i'd like to keep the functionality that i currently enjoy but not leave such
residue (installer.dll and installer.State). how do i use the files in the
setup application whilst not leaving them on the hard drive after all is
said and done.

tia,

me

Nov 21 '05 #2

P: n/a

thanks for the head's up, ken.
"Ken Tucker [MVP]" <vb***@bellsouth.net> wrote in message
news:eQ**************@TK2MSFTNGP09.phx.gbl...
| Hi,
|
| You can use a merge module to install mdac
|
| http://support.microsoft.com/default...;EN-US;q320788
|
| In general take a look at custom actions to add the functions
| you want.
|
|
http://msdn.microsoft.com/library/de...stomaction.asp
|
| Ken
| ----------------------
| "" <a@b.com> wrote in message news:lf*************@fe06.lga...
| i need a refresher.
|
| i've created setups in the past that don't have the following problem. i
| need help remembering the proper settings to correct the problem.
|
| the setup i have includes an installer class which hooks into the after
| install event. setup itself installs a main application and a couple of
| others that detect the installation and configuration of
| applications/components that the main application will use...i.e. msde or
| ado or ...etc., etc.... if they are not installed they will be and if they
| aren't configured, they will be.
|
| anyway the installer class's after install event shell's out to an exe
that
| does all of this. everything works fine but, the installer class shows up
in
| the root application install directory (installer.dll). in addition to
this,
| there is another file there called installer.State.
|
| i'd like to keep the functionality that i currently enjoy but not leave
such
| residue (installer.dll and installer.State). how do i use the files in the
| setup application whilst not leaving them on the hard drive after all is
| said and done.
|
| tia,
|
| me
|
|
|
Nov 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.