How To Work With Database Installer

Installation

Please run setup.exe file and follow on-screen instructions to install Database Installer component. If you wish to use evaluation version leave “License Key” field blank. You will be able to upgrade to licensed version later.

Using Database Installer in Visual Studio

In order to use Database Installer successfully, please follow the steps below:

1. Add a reference to HiveStudios.DeploymentTools.DBInstaller.dll to your project or add the component to Visual Studio toolbox. You can do that if you right click on the toolbox and select Choose Items. When “Choose Toolbox Items” dialog appears, click Browse and navigate to installation folder. Select HiveStudios.DeploymentTools.DBInstaller.dll and click OK.
2. Add new Installer component to your project and open it in design mode. Make sure it has RunInstallerAttribute applied on class declaration and set to true.
3. Drag Database Installer from the toolbox to the designer.
4. Select the component on the form and set its properties.

You can use drop down menu or designer verbs to

• Upgrade from trial to full version
• Get support on www.hive-studios.com
• Bulk add script files to install or uninstall script lists

Properties

Using Database Installer in Code

Configuring Custom Actions and Passing Parameters to Installer

Database Installer supports four properties that can be set by installer during installation or uninstallation of your package

Using installutil.exe

1. Run Visual Studio Command Promt
2. Navigate to the folder that contains your binaries
3. Run installutil.exe

Installutil YourBinaries.dll /SERVER=myservername /UID=habahaba /PWD=s3cr3tpazz

If you want to use Windows Integrated security to authenticate agains SQL Server use INTEGRATEDSECURITY parameter

Installutil YourBinaries.exe /SERVER=myservername /INTEGRATEDSECURITY=true

Using Windows Installer

Please see detailed walktrough on MSDN (http://msdn2.microsoft.com/en-us/library/9cdb5eda(VS.80).aspx)

Unit Testing Database Installer

Unit testing is a procedure used to validate that individual units of source code are working properly. Unit testing installers might be tricky. The basic approach is to simulate activity of Windows Installer and Installutil in your code.

1. Add unit test project to your application if you do not have one.
2. Add reference to project that contains code you want to test. Add reference to System.Configuration.Installer .NET library
3. Add folder(s) to the test project  and fill it with your scripts
4. Open LocalTestRun.testrunconfig, go to Deply Items tab and add scripts to the deployments. It is important to note that MSTest will copy these files to the specific location where all test are executed.
5. LocalTestRun.testrunconfig file using XML or text editor and add outputDirectory to each DeploymentItem that represent your scripts

   <DeploymentItem filename="TestProject1\Scripts\DropDatabase.sql" outputDirectory="Scripts"  />

   
   
6. Create new TestMethod that will test your installation code
7. In the Test method, create one instance of the installer you want to test, one instance of InstallContext and one collection that implements ICollection interface.
   

   DatabaseInstaller parent = new DatabaseInstaller();

   InstallContext context = new InstallContext();

   IDictionary state = new Hashtable();
   

8. Add parameters to the context installer

   context.Parameters.Add("SERVER", Environment.MachineName);

   context.Parameters.Add("INTEGRATEDSECURITY", "true");

9. Fill InstallScriptList and UnInstallScripts, set any other properties and run installer
   

   parent.InstallScriptList.Add(new InstallScript(@"CreateDatabase.sql"));

   parent.InstallScriptList.Add(new InstallScript(@"CreateDatabaseObjects.sql"));

   parent.UninstallScriptList.Add(new InstallScript(@"DropDatabase.sql"));

    

   parent.Install(state);

   parent.Commit(state);

   parent.Uninstall(state);

   
   
10. You can add additional code after calls to Install(), Commit() and Uninstall() to check are scripts performs as expected
11. On the end, test method should look similar to this:
    

    [TestMethod]

    public void TestMethod1()

    {

     

        MainInstaller installer = new MainInstaller();

        InstallContext context = new InstallContext();

        IDictionary state = new Hashtable();

     

     

        context.Parameters.Add("SERVER", Environment.MachineName);

        context.Parameters.Add("INTEGRATEDSECURITY", "true");

     

        try

        {

            parent.InstallScriptList.Add(new InstallScript(@"CreateDatabase.sql"));

            parent.InstallScriptList.Add(new InstallScript(@"CreateDatabaseObjects.sql"));

    newue;">new InstallScript(@"DropDatabase.sql"));

            parent.Install(state);

            parent.Commit(state);

            parent.Uninstall(state);

     

        }

        catch (InstallException ex)

        {

            parent.Rollback(state);

            Assert.Fail(ex.ToString());

        }

        catch (Exception ex)

        {

            parent.Rollback(state);

            Assert.Fail(ex.ToString());

        }

     

    }