Visual Studio vs. CCNET as Service

Ok I’m going completely mad with CCNET and Visual Studio 2005. We’ve got CCNET running from the command line – but wanted to migrate to running it as a service so that it would always be run after a machine restart. The service has the login credentials of the user that runs the command line version today. So in theory they’re the same people.

The ccnet config file:

<cruisecontrol>
 <project name="EndManager" webURL="http://localhost/EndManager">
  <intervalTrigger name="continuous" seconds="30"/>
  <sourcecontrol type="vss">
   <project>$/EndorsementManager_Net</project>
   <workingDirectory>C:\GLOBEXDOTNETVSS\ENDORSEMENTMANAGER_NET</workingDirectory>
   <timeout units="seconds">600</timeout>
   <ssdir>\\vss2\share2\GlobexDotNet</ssdir>
  </sourcecontrol>
  <tasks>
   <devenv solutionfile="C:\GLOBEXDOTNETVSS\ENDORSEMENTMANAGER_NET\Source\EndorsementMgr.sln" configuration="debug" />
   <nunit path="C:\Program Files\NUnit 2.4.8\bin\nunit-console.exe">
    <assemblies>
     <assembly>C:\GLOBEXDOTNETVSS\ENDORSEMENTMANAGER_NET\Source\EndmBaLayer\EndmBaComponentUnitTest\bin\Debug\EndmBaComponentUnitTest.dll</assembly>
    </assemblies>
   </nunit>  
  </tasks>
 </project>
</cruisecontrol>

This contains the much maligned devenv task which we use because its easier than writing an msbuild script for all of the assemblies. The devenv task trys to do the following on the command line:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.com "C:\GLOBEXDOTNETVSS\ENDORSEMENTMANAGER_NET\Source\EndorsementMgr.sln" /rebuild "debug"

Net result – I get the following wonderfully descriptive error: “the application data folder for visual studio could not be created” What’s up? Is this an environment variable problem? Shouldn’t having the login credentials of the user mean that we get their environment variables?

Any ideas?

If you enjoyed this post, subscribe now to get free updates.