NuGet package no longer aligned with the 'Getting Started' guide.

[NeoXtreem]

Version 1.5 of the NuGet package no longer has the PowerShell script that adds the .build folder; yet the 'Getting Started' guide still says to reference this folder if using NuGet to get MSBuildTasks. Is there an alternative method to use MSBuildTasks via NuGet? If so, the documentation should be updated. Otherwise, reinstate the PowerShell script.

[adaneam]

Facing the same issue. Any updates on this?

[lcornejo]

Looks like something like this will get you going

<PropertyGroup> <MSBuildCommunityTasksPath>$(USERPROFILE)\.nuget\packages\msbuildtasks\1.5.0.235\tools</MSBuildCommunityTasksPath> </PropertyGroup>

obviously change this to your current version, as it implies above I found my tasks target file here: C:\Users\{username}\.nuget\packages\msbuildtasks\1.5.0.235\tools

[karelkral]

The problem is using NuGet as Package reference. I this case there is no installation folder relative to solution, only a local folder mentioned by lcornejo. I solved this by copying task files to path in solution dir (in example .build) and modified paths is .csproj pointing to this dir.

[CADbloke]

my csproj ended up with this...

<PropertyGroup>
    <MSBuildCommunityTasksPath>$(SolutionDir)\packages\MSBuildTasks.1.5.0.235\tools</MSBuildCommunityTasksPath>
  </PropertyGroup>  
  <Import Project="$(MSBuildCommunityTasksPath)\MSBuild.Community.Tasks.Targets" />