running sql scripts and custom install fields

[ricardobentes]

Hi!

I'm currently evaluating Install Aware Express and Developer, but before making a decision I have a few doubts.
If any of these features isn't possible in Express Edition please tell me wich Edition is it possible to accomplish. Also feel free to point me any documentation that I might have overlooked.

1 - Is it possible to configure the Monitor URL field at runtime, for example, having an ".ini" or .XML file with that information? I'm asking this because we are pondering to use different update servers depending on the client.

2 - Is it possible to include SQL scripts using the Express version? I tried including an insert statement and checked the box for canceling install if there's an error in the script but neither the install was canceled nor the sql table contained the new record. Is there any example / tutorial on this matter?

3 - Is it possible to configure in runtime (asking the user or via an ".ini" or ".xml" file) the database information?

4 - If I have 20 customers and I publish a new Update how do I filter witch customer is allowed to update? I saw a small example of this funcionality in the document installaware_web_updates.pdf but was wondering if there is a more detailed documentation / tutorial on this.

Thank you very much for any help that you may provide me.

Best Regards,
Ricardo Bentes

[mills]

1. The monitor URL value is determined at compile time. You can see this in the MSIcode. The web media blocks, which contain the URL definition, are defined by compiler directives. You can have multiple source paths for each media block.

2. You can specify SQL scripts with Express. However, I would recommend at least Developer, since this allows you to use messageboxes to display the results of the command, which would be my first question, "What was returned by the command you ran?"

3. This should be possible. It would help if you were a little more specific about what you'd like to do. You'll need Developer or better edition.

4. The next best resource is the actual updates script. It's completely modifiable. Generally, user-specific updates are not considered. This will definitely require some customization and therefore Developer edition or better. The first question that comes to mind is "How do you want to control the updates?" It should be possible. You could use user names as a determining factor. You could list the users that should receive the update in the description field of an update, then use the MSIcommand Get System Setting -> Logged on User Name to compare against that list.

[ricardobentes]

Thank you for your quick answer!

One more question if I may, is it possible to create automatic updates in .zip files instead of .exe?

Best regards,
Ricardo Bentes

[mills]

Do you want the zip to be installed to your program directory or do you want to avoid issuing an exe (perhaps due to server restrictions)?

[ricardobentes]

Do you want the zip to be installed to your program directory or do you want to avoid issuing an exe (perhaps due to server restrictions)?

I'd like to avoid issuing an .exe, exactly due to server restrictions.

About my 3rd question in the previous post, this is what I had in mind:
I'd like to know how may I configure at install-time, the database where the sql scripts will be executed. Either by a file in the same directory (an .ini or a .xml) or by asking these informations to the user when installing the software.

Thank you for you answers.

Best regards,
Ricardo Bentes

[mills]

Hi Ricardo,

When you include the runtimes for SQL Server, two scripts, check and setup, will be added to your project.

In the setup script, there's a line:

Code: Select all

 Set Variable SQL2008R2_COMMAND_LINE_X86 to /q /ACTION=Install /SECURITYMODE=SQL /SAPWD="Sq1S#rv$r" /INSTANCENAME="SQLEXPRESS" /FEATURES=SQLEngine,Replication,SDK /SQLSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE" /SQLSYSADMINACCOUNTS="$SQL_COMPUTER_NAME$\$SQL_USER_NAME$" /IAcceptSQLServerLicenseTerms=TRUE

For command line setup (options):
http://msdn.microsoft.com/en-us/library/ms144259.aspx

That essentially controls the SQL setup. You could build a GUI to configure those command line parameters based on user selections or you could store the setup in a file (other than the script), or just modify the script.

You can read from file using Read from Text File or Get INI File Settings commands.