Open Source .NET Development [Electronic resources] نسخه متنی

Hippo.NET

Hippo.NET> (http://hipponet.sourceforge.net) integrates Draco.NET Continuous Integration, Microsoft BuildIt, and Microsoft Visual SourceSafe (VSS). This product obviously targets the Visual Studio.NET users. A clear advantage of using BuildIt is the automatic understanding of Visual Studio.NET project and solution files. The biggest drawback is the support of the single VSS SCM.

Installing

The installation is fairly easy and well documented. Download a zip file distribution and install the Hippo.Server by using the SDK's InstallUtil.exe tool.

NOTE

This is based upon Hippo.NET version 1.2.0.

Configuring

Before running Hippo.NET, you have to configure the projects.xml file included in the Server directory of the zip file distribution. Listing 7.1 shows an example projects.xml file.

Listing 7.1. Hippo.NET's Project File

<?xml version="1.0" encoding="utf-8"?>
<ArrayOfProjectConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http:
//www.w3.org/2001/XMLSchema-instance">
<ProjectConfiguration>
<ProjectName>TestProject</ProjectName>
<

SourceSafeINI>C:\Program Files\Microsoft Visual Studio\Common\VSS\srcsafe.ini<
/SourceSafeINI>

<SourceSafeProject>$/TestApp2.root</SourceSafeProject>

<SourceSafeUsername>Admin</SourceSafeUsername>

<SourceSafePassword></SourceSafePassword>

<WorkingFolder>C:\Temp\VSS\TestApp2.root\</WorkingFolder>

<BuildCommand>nant.exe</BuildCommand>
<BuildCommandArguments>-buildfile:TestApp2\project.build</BuildCommandArguments>
</ProjectConfiguration>
</ArrayOfProjectConfiguration>

The SourceSafeIni file node is the path to the SCM repository. The SCM project, username, and password are also required nodes. WorkingFolder is the path to get and build the code. BuildCommand nodes are for the path and arguments to the build tool used (in this case, NAnt).

Running

The client (shown in Figure 7-2) and server service communicate using .NET. Remoting the .NET configuration files should be using the same host and TCP port.

While the UI is very nice, checking a Hippo.NET build would require using the client application. This is not very conducive to large development teams.