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.

Sign up for GitHub

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

Jump to bottom

[Scenario] Add tutorial to show how to consume .NET Standard libraries with .NET Framework projects, for example #2712

Closed
BillWagner opened this issue Jul 23, 2017 · 2 comments
Closed

[Scenario] Add tutorial to show how to consume .NET Standard libraries with .NET Framework projects, for example #2712

BillWagner opened this issue Jul 23, 2017 · 2 comments
Labels
dotnet-framework/svc help wanted Good for community contributors to help [up-for-grabs] won't fix Issues that were closed as part of automated backlog grooming

Comments

@BillWagner
Copy link
Member

Developers that build libraries and applications that use the .NET Framework will take dependencies on libraries that are part of .NET Standard, or rely only on the .NET Standard.

This tutorial will show how to add those libraries as dependencies, what it adds in csproj files, and what it means for build processes.
@BillWagner BillWagner added this to the 2017 - Quarter 3 milestone Jul 23, 2017
@mairaw mairaw mentioned this issue Jul 23, 2017
Closed
37 tasks
@mairaw mairaw modified the milestones: 2017 - Quarter 4, 2017 - Quarter 3 Sep 5, 2017
@mairaw mairaw modified the milestones: 2017 - Quarter 4, Backlog Jan 8, 2018
@mairaw mairaw added P1 help wanted Good for community contributors to help [up-for-grabs] and removed P1 labels Jan 8, 2018
@JRAlexander JRAlexander mentioned this issue Feb 14, 2018
Closed
62 tasks
@sputier
Copy link
Contributor

sputier commented Mar 12, 2018

Alright, I'm in for this one !

@BillWagner BillWagner modified the milestones: Backlog, March 2020 Mar 2, 2020
@BillWagner BillWagner removed this from the March 2020 milestone Mar 31, 2020
@dotnet-bot dotnet-bot added the won't fix Issues that were closed as part of automated backlog grooming label Jan 25, 2021
@dotnet-bot
Copy link
Contributor

This issue has been closed as part of the issue backlog grooming process outlined in #22351.

That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dotnet-framework/svc help wanted Good for community contributors to help [up-for-grabs] won't fix Issues that were closed as part of automated backlog grooming
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@BillWagner @sputier @tdykstra @JRAlexander @dotnet-bot @mairaw @PRMerger12