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 TargetFrameworkMoniker & TargetPlatformMoniker to infer the frameworks instead of using individual TFI, TFV, TPI, TPV properties #9895

Closed
nkolev92 opened this issue Aug 10, 2020 · 1 comment · Fixed by NuGet/NuGet.Client#3578
Assignees
Labels
Functionality:SDK The NuGet client packages published to nuget.org Partner:CLI-SDK Priority:1 High priority issues that must be resolved in the current sprint. Type:DCR Design Change Request

Comments

@nkolev92
Copy link
Member

nkolev92 commented Aug 10, 2020

NuGet should use TargetFrameworkMoniker & TargetPlatformMoniker to infer the frameworks instead of using the individual TFI, TFV, TPI, TPV properties

@nkolev92
Copy link
Member Author

This is in review...fixing estimate.

@dominoFire dominoFire changed the title NuGet should use TargetFrameworkMoniker & TargetPlatformMoniker to infer the frameworks instead of using the individual TFI, TFV, TPI, TPV properties Use TargetFrameworkMoniker & TargetPlatformMoniker to infer the frameworks instead of using individual TFI, TFV, TPI, TPV properties Nov 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Functionality:SDK The NuGet client packages published to nuget.org Partner:CLI-SDK Priority:1 High priority issues that must be resolved in the current sprint. Type:DCR Design Change Request
Projects
None yet
2 participants