Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Please use framework reference to System.Net.Http in .net framework builds

See original GitHub issue

now .csproj file have for net452 and net 461

  <ItemGroup Condition=" '$(TargetFramework)' == 'net452' ">
    <PackageReference Include="System.Net.Http" Version="4.3.3" />
  </ItemGroup>

can you please use

  <ItemGroup Condition=" '$(TargetFramework)' == 'net452' ">
    <Reference Include="System.Net.Http" />
  </ItemGroup>

So resulting nuget package will have less package dependencies for .net framework.

@leastprivilege are you agree with this?

Issue Analytics

State:
Created 6 years ago
Comments:25 (13 by maintainers)

Top GitHub Comments

1reaction

leastprivilegecommented, Nov 28, 2017

That was the advice from the .NET team for the time being until they fix a bug they have in tooling.

1reaction

leastprivilegecommented, Nov 24, 2017

OK - whatever that means. It seems .NET is fucked 😉

Top Results From Across the Web

System.Net.Http 4.2 with .NET 4.7

Per suggestion and since I needed to use version 4.2, I have copied out the corresponding version to repository and added reference to...

Troubleshoot .NET Framework targeting errors

This article provides resolutions for MSBuild errors that might occur because of reference issues.

System.Net.Http is driving me insane. : r/csharp

NET 4.7.1, I've had a torrent of issues with System.Net.Http .dll references on our build server. ... Its a .net framework bug.

Ranorex always uses System.Net.Http.dll from the GAC ...

The primary reference "LTUtils" could not be resolved because it has an indirect dependency on the .NET Framework assembly "System.Net.Http, Version=4.1.1.2 ...

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...