Author: Mischa Taylor
Revision Date: 2011-12-28 03:24:52 UTC

Change to make services easier to debug. Before, if you tried to run
the service from the Visual Studio debugger or the command line, it
would print the following message:

  Windows Service Start Failure

  Cannot start service from the command line or a debugger. A Windows
Service
  must first be installed (using installutil.exe) and then started with
the
  ServerExplorer, Windows Services Administrative tool or the NET START
  command.

It's a pain to have to debug the service this way. A common pattern is
to change the wizard code generated by Visual Studio to support
launching the service interactively (without disturbing how the service
code behaves when run under the proper service context in production).

-------------- This line and the following will be ignored
--------------

modified:
  windows/xenserver/src/Rackspace.Cloud.Server.Agent.Service/Program.cs
  windows/xenserver/src/Rackspace.Cloud.Server.Agent.Service/Rackspace.Cloud.Server.Agent.Service.csproj
  windows/xenserver/src/Rackspace.Cloud.Server.Agent.UpdaterService/Program.cs
  windows/xenserver/src/Rackspace.Cloud.Server.Agent.UpdaterService/Rackspace.Cloud.Server.Agent.UpdaterService.csproj