Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use System.Net.Http from NET Framework rather than NuGet #319

Merged

Conversation

simendsjo
Copy link
Contributor

The System.Net.Http package on NuGet was put there as an OOB update where
Microsoft also tried to add extra functionality for NET Framework developers.

This experiment didn't work, but Microsoft didn't want to pull the package from
NuGet as people would get strange errors.

Microsoft has written a post-mortem on GitHub, ref
https://github.com/dotnet/corefx/issues/17522#issuecomment-338418610

NOTE: I also had to remove NETStandard.Library from NET Framework as that
depends on System.Net.Http from NuGet.

@simendsjo
Copy link
Contributor Author

Ping? As many others, we've had various strange issues related to System.Net.Http because of Microsofts error. Took us a while to investigate it more in depth to find out Neo4jClient was the culprit. It would be nice to get this merged.

The System.Net.Http package on NuGet was put there as an OOB update where
Microsoft also tried to add extra functionality for NET Framework developers.

This experiment didn't work, but Microsoft didn't want to pull the package from
NuGet as people would get strange errors.

Microsoft has written a post-mortem on GitHub, ref
https://github.com/dotnet/corefx/issues/17522#issuecomment-338418610

NOTE: I also had to remove NETStandard.Library from NET Framework as that
      depends on System.Net.Http from NuGet.
@simendsjo simendsjo force-pushed the System.Net.Http-from-NETFramework branch from 3666985 to d568e35 Compare January 11, 2019 08:31
@simendsjo
Copy link
Contributor Author

Ping -- this is probably a problem for everyone on NET Framework, but the issues it causes is difficult to pin back to the broken Microsoft package.

@cskardon
Copy link
Member

Sorry @simendsjo for some reason I'm not getting notified of these, let me look at it and I'll try to get it in today

@cskardon cskardon merged commit 87c58d6 into DotNet4Neo4j:master Jan 17, 2019
@cskardon
Copy link
Member

It's building... :o

Thanks for this and the other one! Sorry for the delay!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants