Thursday, February 1, 2007

debugging tips for msbuild scripts

(I'll add to this as they come to me)

  1. If you're changing an imported build script then Visual Studio 2005 seems to cache the imported script - so if your changing common msbuild files then debug them using the command line (it's also faster).
  2. Number 1 Gottcha: If it doesn't work it's becuase the files didn't exist at the start of the build and you need to use CreateItem not ItemGroup.
  3. Autogenerate your AssemblyInfo files when the project is built and don't have them in source control (helps cruise).
Visual Studio 2005 Tips
  1. When Visual Studio tells you an error has occured and it must close, you can move this error box to the side and continue coding. Restart VS at your lesure.

No comments: