更多讨论参考:https://stackoverflow.com/questions/52833741/your-project-does-not-reference-netframework-version-v4-6-2-framework-add-a :
I experienced similar issue,but with?v4.7.2
. Namely,I kept getting build log message like this:
error : Your project does not reference ".NETFramework,Version=v4.7.2" framework. Add a reference to ".NETFramework,Version=v4.7.2" in the "TargetFrameworks" property of your project file and then re-run NuGet restore.
Despite the fact that it looked similar,none of the above proposed steps worked for me. I kept seeing this message after each build. Nothing seemed to be able to help.
In fact,the problem was related to that,due to migration,I had to put?two projects in one folder?of code. One of them was targeted at?.Net Core,another at?.Net Framework,both referenced same .Net Standard libraries. Apparently,they share the same?obj
?folder where Core projects put?project.assets.json
?file. Actually,exactly this file interferres with the Framework project preventing its normal build. Seems even if you performed?Migrate from packages.config to PackageReference...?which was recommended as one of possible solution.
You can try to fix the issue by putting the following snippet into your Framework project file:
<Project>
...
<PropertyGroup>
<BaSEOutputPath>$(MSBuildProjectDirectory)/out/$(MSBuildProjectName)/bin</BaSEOutputPath>
<BaseIntermediateOutputPath>$(MSBuildProjectDirectory)/out/$(MSBuildProjectName)/obj</BaseIntermediateOutputPath>
</PropertyGroup>
...
</Project>
It immediately worked for me,it was only later when I attentively read why we need it and why it works. I unexpectedly found it in?part 2?of?Migrating a Sample WPF App to .NET Core 3?under?Making sure the .NET Framework project still builds?section.?BaSEOutputPath
?and?BaseIntermediateOutputPath
?msbuild variables can be found there,not sure if they are documented well anywhere.