Which way to go?
Posted 25 May 2005 - 13:27
I've just started using installshield 11 as my company has decided that a professional install is the way forward!
Basically I need to check for running programs, install vb6 exes (moving to .net in the near future), get logon details for multiple SQL servers, generate registry keys and odbc connections and then run SQL scripts against existing databases based upon the logon details (and conditions) gathered.
Basically I need to know if MSI is the way forward?
Posted 25 May 2005 - 13:36
"InstallScript MSI" is a combination of the two technologies and should be avoided bacause it causes a couple of problems.
Posted 25 May 2005 - 13:41
What sort of things are limited when using developing an MSI? (compared to installscript)
Posted 27 May 2005 - 10:44
|I take it that using MSI I can call an external DLL or VB exe to execute SQL scripts on a Server|
You can call VBScript, JScript, DLLs, or EXEs as custom actions. In general you need to create these yourself. For SQL scripts however InstallShield alsready includes a set of custom actions and a special view in the IDE to configure SQL connections and scripts.
|What sort of things are limited when using developing an MSI? (compared to installscript)|
One thing that InstallScript can do much better than MSI is installing multiple instances of your application on the same computer (if that's a requirement for you).
Using a customized user interface (i.e. using controls or behaviours that MSI doesn't support) is easier in script.
Posted 14 June 2005 - 11:00