Remove frameworkAssembly reference to System.Net.Http
See original GitHub issueIt should be sufficient to have a dependency on the System.Net.Http
nupkg.
The frameworkAssembly
reference breaks downstream packages that target net461
but have other dependencies that target netstandardx.x
and depend on System.Net.Http
via NuGet because the assembly versions in the GAC (for both 4.5.x and 4.6.x) differ from the latest published via NuGet.
Issue Analytics
- State:
- Created 7 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Found conflicts between System.Net.Http
Remove any references to System.Net.Http that are not managed by NuGet (for projects using PackageReference, you should see the NuGet symbol ...
Read more >System.Net.Http is driving me insane. : r/csharp
I'm very confused by the Visual Studio build system. There are references to assemblies in the .csproj, the packages config, and the web.config ......
Read more >Problem with System.Net.Http after upgrade to 6.3.7 and ...
The type 'HttpResponseMessage' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Net.Http ...
Read more >Troubleshoot .NET Framework targeting errors
This article provides resolutions for MSBuild errors that might occur because of reference issues.
Read more >how to solve confilct issue of system.net.http on .net 4.6.1
hello I am developing asp.net web using .net framework 4.6.1 but i stuck ... Net.Http.dll Project file item includes which caused reference ......
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 Free
Top 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
OK - thanks for researching that. Since project.json and the other combinations seem to work - we can leave it as it is.
I moved to the new csproj
Could you try the dev branch - and if this fixes your scenarios?
Just call the build.ps1 in the root - it will produce a nuget