Sunday, 14 June 2009

Outputting the Subversion revision into your web page

A few months ago when I stared using stackoverflow I noticed that they output the current Subversion revision number into their html source.

Stackoverflow revision number

This is both cool and useful and as I’m about to become a SVN Nazi and make sure that all new projects at work are placed under source control (only a few are at present) I wanted to know how to do it.

Getting the tools

Most of our projects are built using ASP.NET so I wanted to know how to get this working from within Visual Studio. Thankfully this didn’t take long, a few Google’s turned up MSBuild Community Tasks Project hosted over at who are the good folks behind Subversion and many many Subversion tools. I had a quick look over the list of tasks and spotted the “SvnVersion” task and thought that sounds about right. I downloaded and installed the Community Tasks.

I also downloaded the Visual Studio Web Deployment projects after having read ScottGu’s blog post regarding them. You can get the VS2008 version here or the VS2005 version here if you need it.

Getting the revision into your HTML

To get the revision number into my HTML I chose to add a Web Deployment project (right click on your website/web app in the solution explorer and “Add web deployment project” then right click on this new project and “Open project file”. What you’ll see now is the XML of the MSBuild file and towards the bottom of this file should be a comment with four target tags in it like this.

<!-- To modify your build process, add your task inside one of the targets below and uncomment it.
Other similar extension points exist, see Microsoft.WebDeployment.targets.
<Target Name="BeforeBuild">
<Target Name="BeforeMerge">
<Target Name="AfterMerge">
<Target Name="AfterBuild">

We’re going to use the AfterBuild target so to place the revision number in a little bit of HTML that’s going to live in a master page, so let’s set up the master page first.

My site is a .NET MVC application and I’m going to add the revision number to the Site.Master. To do this I added the following HTML to the footer of the master page.

<span id=”rev”>revision REVISION</span>

The SvnRevision task will get the revision number from our working copy and store it in a property name that we define.

We can then use another Community Task, FileUpdate, to update the master page after the build.

Here is the XML of the AfterBuild target looks, note also that before the target I have imported the Community Tasks that we downloaded and installed earlier.

<!-- Import the community build tasks-->
<Import Project="$(MSBuildExtensionsPath)\MSBuildCommunityTasks\MSBuild.Community.Tasks.Targets" />
<target name="AfterBuild">
<! -- Add the SvnVersion build task -->
<svnversion toolpath="$(ProgramFiles)\VisualSVN\bin" localpath="$(MSBuildProjectDirectory)">
<output propertyname="Revision" taskparameter="Revision" />
<fileupdate replacementtext="revision $(Revision)" regex="revision REVISION" files="$(Configuration)\Views\Shared\Site.Master" />

The FileUpdate finds the string defined in the regex attribute and replaces it with the string in the replacementText attribute. $(Revision) is MSBuild syntax for a property (like a variable in other languages) where “Revision” is the property name. The files attribute tells the fileUpdate action which file to work with when doing this replacemnet. In this example $(Configuration) is a property that the build engine creates which contains the name of the current build configuration (Debug or Release are the defaults).

So to see this in action, right click on the Web Deployment Project and click Build. Then navigate to the solution folder. Inside that folder should be another folder named the same as your Web Deployment Project and in there, a folder for what ever configuration you had selected in Visual Studio (Debug is the default). Open this folder then browse to the folder containing the master page and open the master page in your favourite text editor. Find the span from the earlier step and you should see that the uppercase “REVISION” has been replaced with the current revision of your working copy.

Friday, 5 June 2009

Installing EPiServer and VMWare ESXi

Wednesday this week our group IT manager Gordon brought us some new hardware to play with in the form of 3 HP DL308's (two G4's and one G3) which I think and hope we're going to consolidate our jumble sale of a server room onto for the most part with the use of VMWare's wonderful ESXi (version 3.5 because version 4 requires 64bit hardware and the VMWare compatibility list says the G3 and G4 are only compatible with 3.5).

I caught Matt just in time as he was about to install Windows 2003 on one of the G4's and got him to let me install ESXi on it. Which I did without hitch (except for when I couldn't get the networking to work, then I realised the Ethernet cable wasn't plugged in). Then it was a cinch to download the Infrastructure Client from the box and spin up a new VM and get Windows 2003 installed. Within an hour I'd got a new virtual development server up and running. Happy man.

Next up I downloaded and installed SQL Server 2005 Express, which didn't go quite to plan as the installer kept complaining that the SQL Native client installer package was missing. This was fixed by going into add/remove programs and uninstalling the (failed) Native Client install and starting the whole thing again.

Then came installing EPiServer CMS which was a completely painless task comprised of logging into EPiServer World and downloading the latest stable release (CMS 5 R2) and installing it, I then used the Deployment Centre utility to install the demo site for the team here to have a play with.

Job done!

Over the coming weeks I'm going to be posting a bunch more articles about my trials and tribulations with EPiServer which I'm looking forward to and hope will provide a nice chage from building brochure ware sites for purfume brands.

Thursday, 4 June 2009

More CMS's, this time for PHP

I recently had a requirement for a CMS to run on a Linux server. For 99% of my day-job I use ASP.NET but I am an old hand at PHP and I'm not overly familiar with the syntax of Ruby or Python so PHP was my language of choice.

I was after a small, easy to set up, flexible solution which wasn't going to take ages to install and configure and that also didn't require me to use a massive framework.

I friend recomended Pixie which is a free, open source offering from toggle and I've got to say that I was pleasantly supprised. Admittedly it's a million miles away from the object oriented nature of .NET that I'm so used to but it does have a plugin architecture and is easily skinnable.

I recomend giving it a try!