title: MSBuild community tasks can not be loaded even when it is installed
body: <p>I had a WPF application that I did not touch for around a year and now I have a new PC.
  When I clone the application from git and tried to run it, I am getting this error:</p>
  
  <pre><code>Severity    Code    Description Project File    Line    Suppression State
  Error       The "MSBuild.Community.Tasks.AssemblyInfo" task could not be loaded from the assembly D:\MyData\SourceCodes\Library\MSBuildCommunityTasks\MSBuild.Community.Tasks.dll. Could not load file or assembly 'Microsoft.Build.Utilities, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. Confirm that the &lt;UsingTask&gt; declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.      
  </code></pre>
  
  <p>When I try to install Microsoft.Build.Utilities.Core from here:</p>
  
  <p><a href="https://www.nuget.org/packages/Microsoft.Build.Utilities.Core/" rel="nofollow noreferrer">https://www.nuget.org/packages/Microsoft.Build.Utilities.Core/</a> </p>
  
  <p>I am getting this error:</p>
  
  <pre><code>Install-Package : Could not install package 'Microsoft.Build.Utilities.Core 15.9.20'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.5', but the package does 
  not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
  At line:1 char:1
  + Install-Package Microsoft.Build.Utilities.Core -Version 15.9.20
  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo          : NotSpecified: (:) [Install-Package], Exception
      + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PackageManagement.PowerShellCmdlets.InstallPackageCommand
  </code></pre>
  
  <p>How can I fix this problem? </p>
  
  <p>I am using VS 2017, but the original project was compiled using VS 2013, is there any difference?</p>