Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#1395 Harvesting a VS Project requires ToolsVersion=3.5

v3.0
closed
Brian Rogers
heat (135)
2012-09-15
2008-10-31
jordanf
No

I'm getting an exception from Heat when I try to harvest a VS Project. The .csproj does not have a ToolsVersion attribute on the Project element. When I add ToolsVersion=3.5, everything works as expected.

I have 2.0 and 3.5 frameworks installed.

Discussion

  • Bob Arnson
    Bob Arnson
    2008-12-04

    Some coincidental research applies here: MSBuild v3.5\Microsoft.Common.Tasks points to a 3.5 implementation of GetFrameworkSdkPath; it's different than the 2.0 version in that it never logs a message about not being able to find the SDK. My guess is that Microsoft.Build.BuildEngine.Project.Build considers the high-importance message as a reason to return false, which is what triggers an exception in the project harvester.

     
  • This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 21 days (the time period specified by
    the administrator of this Tracker).