Skip to content
This repository has been archived by the owner on Sep 13, 2022. It is now read-only.

Add reference to ValueTuple package to NetStandard2.0 meta-package #22

Closed
jcouv opened this issue Sep 16, 2016 · 6 comments
Closed

Add reference to ValueTuple package to NetStandard2.0 meta-package #22

jcouv opened this issue Sep 16, 2016 · 6 comments
Assignees
Labels
netstandard-api This tracks requests for standardizing APIs.

Comments

@jcouv
Copy link
Member

jcouv commented Sep 16, 2016

Although the ValueTuple and related types won't be part of the 2.0 standard, the meta-package which supports the experience in VisualStudio will reference some additional types for convenience.

@weshaggard @ericstj @tarekgh @terrajobst for information and triage.

@jcouv
Copy link
Member Author

jcouv commented Sep 21, 2016

Assigned to Wes for triage

@weshaggard
Copy link
Member

@jcouv this is on the radar and I will use this issue to track including it once we get the packaging all setup.

@jcouv
Copy link
Member Author

jcouv commented Jan 9, 2017

@weshaggard Just a friendly ping on this. I don't remember which release this is supposed to be included in and what deadlines apply.

@weshaggard
Copy link
Member

This will be part of .NET Standard 2.0 which will be released with .NET Core 2.0 time frame. It will still get done.

@weshaggard weshaggard added the netstandard-api This tracks requests for standardizing APIs. label Jan 9, 2017
@weshaggard
Copy link
Member

Another thing to point out is that we will need to wait to do this until we can update the ValueType package itself to build against netstandard2.0.

cc @ericstj

@terrajobst
Copy link
Member

terrajobst commented Mar 24, 2017

Same answer as for #220: we'll put in netstandard.dll and put the implementation for .NET Framework into a new package that provides support for .NET Standard on .NET Framework 4.6.1.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
netstandard-api This tracks requests for standardizing APIs.
Projects
None yet
Development

No branches or pull requests

3 participants