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

Support consumer projects in .NET Framework (packages.config style) format #2

Closed
felix-b opened this issue May 9, 2019 · 1 comment
Closed

Support consumer projects in .NET Framework (packages.config style) format #2

felix-b opened this issue May 9, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@felix-b
Copy link
Member

felix-b commented May 9, 2019 •
edited
Loading

Currently, consumer projects (.csproj) must be SDK-style (those that start with <Project Sdk="..."> and reference packages through <PackageReference>). This means that .NET Core and NETStandard consumer projects are covered.

The classic .NET Framework projects (packages.config style) should be supported as well.

There are differences between the two styles:

  • SDK-style: packages are used directly from user-level cache (~/.nuget/packages)
  • packages.config style: packages are placed under packages subfolder in solution. This style closely resembles node_modules and allows scoping the link to specific solution.
@felix-b felix-b added the enhancement New feature or request label May 9, 2019
@felix-b felix-b changed the title Support projects in .NET Framework format Support consumer projects in .NET Framework (packages.config style) format May 28, 2019
@felix-b
Copy link
Member Author

felix-b commented Aug 20, 2019

Resolved by #21 and #22

@felix-b felix-b closed this as completed Aug 20, 2019
This was referenced Aug 20, 2019
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@felix-b