Are you using RemoteInstall?

Nov 18, 2009 at 11:37 AM

I'd like to collect some field stories about using RemoteInstall. Can you please describe, in just a couple of lines, where and how you use RemoteInstall framework?

Oct 13, 2010 at 8:10 AM

We're using RemoteInstall to test the setup of our alarm management software LAS. A CruiseControl.NET CI server runs the test every day at 8:00 AM. We run such automated tasks for integration tests, acceptance tests and now the setup tests during the morning hours, since there is seldom any developer activity at those hours. :)

When we deployed RI, we also switched to using dotNetInstaller. Previously we'd been using Microsofts bootstrapper, but it had some downsides such as not being able to embed the msi file in the bootstrapper exe. Also, dotNetInstaller works flawlessly with RI, so there's another reason to use it.

Currently, RI is only doing a basic install/uninstall in a couple of virtual machines with different operating systems. Because the setup also starts a couple of Windows Services, a successful setup test tells us that all required application DLL files are there, that prerequisites have been installed and that database initialization works. We intend to also run some tests, like our integration and acceptance tests using RI. Currently we run them with NUnit from the build scripts like we do with unit tests. With RI we'll hopefully be able to run them in a more production-like environment.

Before using RI, I used a bunch of scripts coded with CS-Script that fired up a VM snapshot which in turn ran another set of scripts that downloaded the latest version of LAS, ran the installer, checked that the services were running and emailed us if it failed. RI's main advantage over that is the integration with CC.NET and the promising possibility of being able to execute tests on the VM.

And before the scripts, we had problems... :)