Re: Custom Actions during setup



Hi Matt,

As you said you're manually launch the SQLExpress package if
necessary,correct? However, based on your previous threads ,you are using
the VS 2005 setup project's bootstrapper/prerequisites feature to do the
SQL Express deployment and this should occur before your own application
start installation. Also, for those SQL Express instance detect, I've
posted information on the conditional install detection for bootstrapper
package in the previous thread, have you had a look at that or do you have
any other concerns that make you unable to use that approach?

Anyway, when using bootstrapper package to deploy prerequisites, after the
prerequisites be installed, the setup process of it should end and then
your main application's installation start. If you want to any further
configuration on the created SQL Express instance, you can use a custom
Action in your main application's setup program. This strength of this is
that those initalization code logic does not need to be added into your
main application's code logic.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.

.



Relevant Pages

  • Security Update for Microsoft Data Access Components (KB832483)
    ... : An error occurred while setup was trying to ... verify the version of Microsoft Data Access Components ... package returned FALSE, or there was a fatal error while ... installation. ...
    (microsoft.public.windowsupdate)
  • Security Update for Microsoft Data Access Components (KB832483)
    ... : An error occurred while setup was trying to ... verify the version of Microsoft Data Access Components ... package returned FALSE, or there was a fatal error while ... installation. ...
    (microsoft.public.windowsupdate)
  • Re: WinUp not recognizing 832483
    ... : Creating worker thread to handle installation of files. ... : Executing PreInstallActions for package. ... : An error occurred while setup was trying to verify the version ... of Microsoft Data Access Components current installed on the machine. ...
    (microsoft.public.windowsupdate)
  • Re: Custom Actions during setup
    ... bootstrapper's "install location", it does be a global setting for all the ... packages you'll included in the setup program. ... it still depend on each individual bootstrapper package. ...
    (microsoft.public.vsnet.setup)
  • Re: using package and deployment program wont run
    ... thought i would use the package and deployment wizard to create the setup ... As I can tell, you're basically saying that your compiled EXE runs fine on your dev PC, but not on any PC it's installed on via a PDW-created Setup? ... The program is obviously installed "correctly" as far as dependency files go or else it wouldn't run at all, so I think you can rule out an improper installation. ...
    (microsoft.public.vb.winapi)

Loading