How To: Debug a custom MSBuild task using Visual Studio

re: How To: Debug a custom MSBuild task using Visual Studio

otter — Wed, 17 May 2006 00:38:13 GMT

thank you, this work for me, would be great if this info made it into the documentation, perhaps as a remark on creating a custom task.

[MsBuild] Writing and Debugging Custom Tasks

Johan Danforth's WebLog — Fri, 23 Feb 2007 00:26:22 GMT

Writing a custom task for MSBuild is very simple, here's the bare minimum code you would need to

[MsBuild] Writing and Debugging Custom Tasks

Johan's Blog — Fri, 23 Feb 2007 11:27:24 GMT

Writing a custom task for MSBuild is very simple, here's the bare minimum code you would need to

re: How To: Debug a custom MSBuild task using Visual Studio

Jantje — Wed, 22 Aug 2007 16:48:57 GMT

This doesn't work, you need to set the working directory instead of the Command line arguments..

itworks » Blog Archive » How To: Debug a custom MSBuild task using Visual Studio

Wed, 07 Nov 2007 18:32:55 GMT

PingBack from http://smccall.ebzzo.com/2007/11/07/how-to-debug-a-custom-msbuild-task-using-visual-studio/

MSBuild Links

Code Junkie — Sat, 12 Apr 2008 04:01:41 GMT

For sometime now I have been working on custom MSBuild task. The following links were very useful in

Microsoft news and tips » MSBuild Links

Microsoft news and tips » MSBuild Links — Sat, 12 Apr 2008 19:24:43 GMT

PingBack from http://microsoftnews.askpcdoc.com/?p=1627

re: How To: Debug a custom MSBuild task using Visual Studio

Eric Steuart — Tue, 15 Jul 2008 19:57:58 GMT

This was very helpful. Jantje's comment about the working directory is partially true. The working directory can make a huge difference in your output, but the command line is also needed so that MSBuild can know what to build. I suggest making the working directory the same as it would be if you were building the project from Visual Studio. This is NOT always the same as the location of the project file.

re: How To: Debug a custom MSBuild task using Visual Studio

ratkiley — Wed, 04 Feb 2009 00:02:52 GMT

I was not able to get MSBuild 3.5 to work with the above instructions. I think it is because of a change to MSBuild and how it passes parameters in v 3.5. See this link for more info:

http://blogs.msdn.com/aaronhallberg/archive/2007/05/03/tfsbuild-rsp-and-logging-verbosity-in-orcas.aspx

I was able to get it to work after:

1) Queue-ing a new build the usual way by right-clicking on the build definition in the Team Explorer in VS 2008.

2) After the build completes, open up the BuildType\ folder (where the TFSBuild.proj file is located). The BuildType\ folder should be located in the same folder as the Sources\ and Binaries\ folders are located by default. Then, open up the auto-generated TFSBuild.rsp file and copy all of the /p: parameters out of it.

3) Paste all of the /p: parameters into the command line parameters field in the project field mentioned in the original blog post, followed by the full path to the TFSBuild.proj file (located in the BuildType\ folder).

4) Set the break point in your custom task, and "Start Debugging" from Visual Studio /(press F5).

re: How To: Debug a custom MSBuild task using Visual Studio

ratkiley — Wed, 04 Feb 2009 00:04:30 GMT

Oh... and the path the the msbuild.exe in the .NET 3.5 framework folder needs to be specified for the command line. It should be something like this:

C:\WINDOWS\microsoft.net\Framework\v3.5\MSBuild.exe