If you have found a bug in MSBuild (or anything else in Visual Studio) the best way to report it is via the product feedback center:

https://connect.microsoft.com/feedback/Search.aspx?SiteID=210

This allows you to track the progress of the issue, which you wouldn't be able to do if we opened the issue internally ourselves. Also, customer reported issues get higher priority, so it's more likely to be fixed.

Sometimes bugs are hard or impossible for us to reproduce, which makes it very hard for us to address them. Here's some tips on a good bug report:

1) Attach a solution or project that reproduces the problem, or steps for creating one from scratch. If at all possible, please narrow down the code and the solution to the simplest possible form that reproduces the problem. This should also avoid you needing to send us any of your company's intellectual property (we don't want any of that please).

2) Get diagnostic logs. Outside of Visual Studio, add the /v:diag switch to MSBuild, pipe it to a file, and attach to the bug. Inside of Visual Studio (if you get different behavior there), go to Tools>Options>Projects and Solutions>Build and Run, and change MSBuild verbosity to "Diagnostic". Then rebuild your project, and copy the output from the Output window - attach this to the bug as well.

Please also let us know what behavior you expected. Any other relevant information about the environment might be useful, such as whether you've tried it on more than one computer, whether it's always happened or just started, whether it happened on VS2003 (if applicable), and so on.

Suggestions can also be reported via the same web pages - we appreciate those too, big or small.

Thanks in advance - The MSBuild Team.

Feedback does not accept bug reports for Visual Studio 2005.