Guidance for creating packages with more than one PackageType? #12014
Unanswered
brandom-msft
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In our current setup, we publish our project as a "dotnet tool". Recently we've had a customer ask that we publish it as a "Dependency" as well, so they can take a standard dependency on it in their project setup.
The NuGet docs specify that one or more types are supported so I updated our package, but now installation via dotnet tool fails.
Error output:
This issue from a few years back mentions that multiple package types are intentionally disallowed for packages of type
DotnetTool
.Is this still the case? If so, can you share any guidance/documentation for how to best provide multiple package types for a given project?
Beta Was this translation helpful? Give feedback.
All reactions