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

Add support for Tizen TargetFrameworkMoniker #2144

Closed
baronfel opened this issue Feb 16, 2017 · 11 comments
Closed

Add support for Tizen TargetFrameworkMoniker #2144

baronfel opened this issue Feb 16, 2017 · 11 comments

Comments

@baronfel
Copy link
Contributor

Description

If NuGet/Home#4175 goes in, then we'll need to update our list to match.

@ghuntley
Copy link
Contributor

tizen30 was merged into NuGet v4.1 over at NuGet/NuGet.Client#1083

@forki
Copy link
Member

forki commented Jun 28, 2017

up-for-grabs

@fsoikin
Copy link
Contributor

fsoikin commented Jul 6, 2017

NuGet also has netstandard1.7 listed (which is supported by tizen4.0, hence the question).
Should that be added to Paket as well, or was it intentionally left out?

@forki
Copy link
Member

forki commented Jul 6, 2017

Please send a pull request. No intention AFAIK

@matthid
Copy link
Member

matthid commented Jul 6, 2017

It is nothing official. 1.7 will be 2.0 afaik. I don't think we should support it. Reason is compat changes in 2.0, so simply adding 1.7 will probably not do the correct thing. Maybe it could be implemented as an alias for 2.0? But I'd prefer to just skip it if possible...

@fsoikin
Copy link
Contributor

fsoikin commented Jul 6, 2017

@matthid do you mean to say that there will never be any actual packages for 1.7?

@forki
Copy link
Member

forki commented Jul 6, 2017

What does inofficial mean when nuget supports it?

fsoikin added a commit to fsoikin/Paket that referenced this issue Jul 6, 2017
fsoikin added a commit to fsoikin/Paket that referenced this issue Jul 6, 2017
fsoikin added a commit to fsoikin/Paket that referenced this issue Jul 6, 2017
@matthid
Copy link
Member

matthid commented Jul 6, 2017

dotnet/standard#160

@matthid
Copy link
Member

matthid commented Jul 6, 2017

It's a temporary place holder until netstandard 2.0 is ready in the toolchain (specifically nuget)

@matthid
Copy link
Member

matthid commented Jul 6, 2017

I guess that means they use it internally for some technical reason?

@fsoikin
Copy link
Contributor

fsoikin commented Jul 6, 2017

I see. Would there be any real harm if Paket supported it?

The way I think about it, if there are no actual packages with that version, then it's a no-op, but if there are any packages, then the lack of Paket support would mean that such packages will fail to install.

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

No branches or pull requests

5 participants