RemoveDepsFileConflicts errors when using .NET Core 2.0
See original GitHub issueNot sure if this is the right place but I get this when building a .NET Core 2.0 test in VS 2017
3>C:\Users\dfowler\.nuget\packages\microsoft.packaging.tools\1.0.0-beta-25121-01\build\Microsoft.Packaging.Tools.targets(89,5): error MSB4018: The "RemoveDepsFileConflicts" task failed unexpectedly.
3>C:\Users\dfowler\.nuget\packages\microsoft.packaging.tools\1.0.0-beta-25121-01\build\Microsoft.Packaging.Tools.targets(89,5): error MSB4018: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Extensions.DependencyModel, Version=1.0.1.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. The system cannot find the file specified.
3>C:\Users\dfowler\.nuget\packages\microsoft.packaging.tools\1.0.0-beta-25121-01\build\Microsoft.Packaging.Tools.targets(89,5): error MSB4018: File name: 'Microsoft.Extensions.DependencyModel, Version=1.0.1.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'
3>C:\Users\dfowler\.nuget\packages\microsoft.packaging.tools\1.0.0-beta-25121-01\build\Microsoft.Packaging.Tools.targets(89,5): error MSB4018: at Microsoft.DotNet.Build.Tasks.RemoveDepsFileConflicts.Execute()
3>C:\Users\dfowler\.nuget\packages\microsoft.packaging.tools\1.0.0-beta-25121-01\build\Microsoft.Packaging.Tools.targets(89,5): error MSB4018: at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
3>C:\Users\dfowler\.nuget\packages\microsoft.packaging.tools\1.0.0-beta-25121-01\build\Microsoft.Packaging.Tools.targets(89,5): error MSB4018: at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()
3>C:\Users\dfowler\.nuget\packages\microsoft.packaging.tools\1.0.0-beta-25121-01\build\Microsoft.Packaging.Tools.targets(89,5): error MSB4018:
3>C:\Users\dfowler\.nuget\packages\microsoft.packaging.tools\1.0.0-beta-25121-01\build\Microsoft.Packaging.Tools.targets(89,5): error MSB4018: WRN: Assembly binding logging is turned OFF.
3>C:\Users\dfowler\.nuget\packages\microsoft.packaging.tools\1.0.0-beta-25121-01\build\Microsoft.Packaging.Tools.targets(89,5): error MSB4018: To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
3>C:\Users\dfowler\.nuget\packages\microsoft.packaging.tools\1.0.0-beta-25121-01\build\Microsoft.Packaging.Tools.targets(89,5): error MSB4018: Note: There is some performance penalty associated with assembly bind failure logging.
3>C:\Users\dfowler\.nuget\packages\microsoft.packaging.tools\1.0.0-beta-25121-01\build\Microsoft.Packaging.Tools.targets(89,5): error MSB4018: To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
3>C:\Users\dfowler\.nuget\packages\microsoft.packaging.tools\1.0.0-beta-25121-01\build\Microsoft.Packaging.Tools.targets(89,5): error MSB4018:
3>Done building project "Microsoft.AspNetCore.Server.KestrelTests.csproj" -- FAILED.
========== Build: 2 succeeded or up-to-date, 1 failed, 0 skipped ==========
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (13 by maintainers)
Top Results From Across the Web
NETSDK1045: The current .NET SDK does not support ...
This error occurs when the build tools can't find the version of the .NET SDK that's needed to build a project. This is...
Read more >The current .NET SDK does not support targeting . ...
I just had this with 15.8.3 after uninstalling some .NET Core 1.x preview SDKs, my application would not compile and showed the error....
Read more >Please stop lying about .NET Standard 2.0 support!
In this post I have a bit of a rant about Microsoft's NuGet packages lying about supporting .NET Standard 2.0 when they kinda...
Read more >.NET Core 2.0 Changes - 4 Key Things to Know
Review of the top .NET Core 2.0 changes and important recent v1.1 changes. Including .NET Standard 2.0, Razor Pages, OS support, and more!...
Read more >Global Error Handling in ASP.NET Core Web API
NET Core. In this article, we are going to handle errors by using a try-catch block first and then rewrite our code by...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ericstj made a fix for this in dotnet/standard yesterday. It made its way to dotnet/core-setup this morning. Once a new build of core-setup is out, using the new Microsoft.NETCore.App version should no longer run into this issue.
Just copy the Microsoft.Extensions.DependencyModel.dll from the SDK folder into microsoft.packaging.tools.
EG: