setup program

[]

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

 

[Ken Tucker [MVP]]

Hi,

You can use a merge module to install mdac

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q320788

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

http://msdn.microsoft.com/library/d...html/vxwlkwalkthroughcreatingcustomaction.asp

Ken
----------------------
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

 

[]

thanks for the head's up, ken.


| Hi,
|
| You can use a merge module to install mdac
|
| http://support.microsoft.com/default.aspx?scid=kb;EN-US;q320788
|
| In general take a look at custom actions to add the functions
| you want.
|
|
http://msdn.microsoft.com/library/d...html/vxwlkwalkthroughcreatingcustomaction.asp
|
| Ken
| ----------------------
| 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
|
|
|