December 31, 2011
The previous post discussed about setting up the unattended service. Now that our shiny new service is ready for delivery, we need to package it inside a Windows Installer MSI.
There are two major alternatives to install a .NET service. The classic one being fully controlled by MSI in Win32 level; the other is overriding methods of System.Configuration.Install leaving it to the CLR via InstallUtil. Or you can combine both methods.
This post is about how to install a .NET service using WiX.
Packaging the service in WiX
Prerequisites: Visual Studio (2005/2008/2010 or higher), WiX toolset
In Visual Studio, create a new...
December 30, 2011
In many productions environments, Windows Services required to run under a privileged domain account. NET services consume the Installer Class foundation to control its installation flow. In most cases, your .NET service ends up packaged in MSI installer which automates the actions InstallUtil does in command line.
But what if you want to install a user account service automatically without bothering the user (other than the service account user\password entries) with post installation actions? Commonly MSI authors will use the ServiceInstall Table which allows runtime entry of username (‘StartName’ column) and password among other properties. However, in case the...
December 23, 2011
AIT's WordToTFS is a helpful tool, integrated as Word add-in for importing\exporting work items between TFS and Word.
On my first attempt to connect to TFS from Word, an error was raised:Missing Fields: "There are one or more mapping fields specified that are not available on the server. This might result in problems while publishing work items."
This message raised in case of mismatch between the TFS Work Item Template fields discovered upon connection to the add-in's fields of its current template.
The solution is simply switching to the correct template:
In WordToTFS tab, disconnect from the TFS.
From the Template group, select the...