Skip to content

Create a .NET Standard 1.1 version of System.Net.Http.Formatting.dll #42

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

Closed
wants to merge 2 commits into from

Conversation

dougbu
Copy link
Contributor

@dougbu dougbu commented Dec 6, 2016

  • Add netstandard support to appropriate packages #4
  • bring System.Net.Http in from .NET Standard Library
  • use .NET Standard version of Newtonsoft.Json
  • bring other dependencies in transitively
  • create initial test project, mostly a duplicate of existing "NetCore" one

nits:

  • write detailed information to m`sbuild.log
  • clean up trailing whitespace in a couple of test classes

- bring System.Net.Http in from .NET Standard Library
- use .NET Standard version of Newtonsoft.Json
- bring other dependencies in transitively
- create initial test project, mostly a duplicate of existing "NetCore" one

nits:
- write detailed information to msbuild.log
- clean up trailing whitespace in a couple of test classes
@dnfclas
Copy link

dnfclas commented Dec 6, 2016

Hi @dougbu, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!

The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.

TTYL, DNFBOT;

@dougbu
Copy link
Contributor Author

dougbu commented Dec 6, 2016

/to @pranavkm
/cc @Eilon

{
"supports": {},
"dependencies": {
"NETStandard.Library": "1.6.1",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if this was discussed separately, but should this be LTS targeting?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Eilon we hadn't discussed this point. Thoughts?

@dougbu dougbu force-pushed the dougbu/add.net.standard branch from a3d8b28 to abee335 Compare December 9, 2016 02:07
@@ -0,0 +1,14 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file is for dev only, right? Can we add a comment here stating that this is for dev, and to make all real changes to the csproj?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the real file for realz. The containing project is a Portable class class library targeting .NET Standard 1.1. packages.config can't be used in such projects. But the flow is almost the same: NuGet.exe reads this file, downloads packages, and writes information the build needs about resolved references into project.lock.json. Recent tooling (i.e. VS2015 *.targets files) gets that reference information and goes from there -- pretty much like any other .csproj project.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Eilon do you have an objection to this approach? Note that going the whole dotnet route would be comparatively old school and tie us to a specific CLI version.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, no, that's fine with me, as long as it works 😄

@dougbu
Copy link
Contributor Author

dougbu commented Dec 9, 2016

My thanks to @emgarten and @rrelyea for moving the "latest" download URL to NuGet.exe v3.5.0. Without that, the "writes information the build needs about resolved references into project.lock.json" bit I just mentioned was incomplete. Builds worked if .xproj projects had been built but failed on clean machines.

Thanks also to @srivatsn and @barrytang for getting me in touch w/ @emgarten and @rrelyea.

@dougbu
Copy link
Contributor Author

dougbu commented Dec 13, 2016

f830808

@dougbu dougbu closed this Dec 13, 2016
@dougbu dougbu deleted the dougbu/add.net.standard branch December 13, 2016 01:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants