Just in case anyone needs it, here is the MSDN article that I used to determine the information that I posted: http://msdn.microsoft.com/en-us/library/vstudio/bb383985.aspx ... View more

I initially used the suggestion from Kyle about manually updating the ToolsVersion value to "4.0" in the isproj file to fix a build issue (TFS 2012). However, as Kyle pointed out "but you may have to [change the ToolsVersion constantly] ... until a patch" is available. After fixing this 3 days in a row for our release builds, I needed to find a more permanent solution. The following work-around worked for me; hopefully it will work for others too: - Notes: A.) Tested using TFS2012 on 64-bit Win2008R2 machine; I think that this will work for TFS2010 too, but don't have one to test it on. B.) All of my projects can use the ToolsVersion 4.0 so this is safe for me; that might not be the case for your solution - your mileage might vary (YMMV) - Make sure that your project file has ToolsVersion="3.5" at the top - Make sure that your latest build failed for the ToolsVersion 3.5 issue - Open your TFS Build Definition - Go to Process tab - Expand #3 Advanced - Go to the MSBuild Arguments - Put in the following (can also be abbreviated /tv, but I like using the full word to avoid any confusion): /toolsversion:4.0 - Queue up a new build - This time it should succeed (or at least get beyond the ToolsVersion 3.5 error message) ... View more