D
Dica
i've got an app that needs to install a named instance of SQL Express. VS
2005 allows me to specify required components for my setup project, but
named instances of SQL Express isn't supported. so, my main setup MSI needs
to execute the SQL Express MSI (a concurrent installation). technically,
this is possible, but this is frowned upon by MS for various reasons. so,
how do i go about pulling this off? i'd be okay if my first setup MSI exits,
but then i need something to call the SQL Express MSI. as far as i can see,
there's nothing like an "onExit" event i can use from my setup MSI to call
and execute the SQL MSI.
what's the best way to pull this off? does installShield offer better
solutions for situations like this?
tks for any advice.
2005 allows me to specify required components for my setup project, but
named instances of SQL Express isn't supported. so, my main setup MSI needs
to execute the SQL Express MSI (a concurrent installation). technically,
this is possible, but this is frowned upon by MS for various reasons. so,
how do i go about pulling this off? i'd be okay if my first setup MSI exits,
but then i need something to call the SQL Express MSI. as far as i can see,
there's nothing like an "onExit" event i can use from my setup MSI to call
and execute the SQL MSI.
what's the best way to pull this off? does installShield offer better
solutions for situations like this?
tks for any advice.