Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Requirement for CLI tool authors to list Microsoft.NETCore.Platforms in nuspec

See original GitHub issue

According to current design spec, global CLI tool authors must define the <dependencies> section in spec as follows:

      <dependencies>
        <dependency id="Microsoft.NETCore.Platforms" version="2.0.1" />
      </dependencies>

Is this really necessary? From my initial tests, portable .NET Core app tools restore just fine without this in the nuspec.

IIUC this is only required for rid-specific tools, not portable ones. RID-restores require it because dotnet-install-tool is implemented as a dotnet-restore. Could dotnet-install-tool add Microsoft.NETCore.Platforms to the generated csproj it uses to call dotnet-restore?

cc @wli3 @livarcocc

cref https://github.com/aspnet/DotNetTools/issues/383

Issue Analytics

State:
Created 6 years ago
Comments:19 (9 by maintainers)

Top GitHub Comments

1reaction

KathleenDollardcommented, Feb 13, 2018

This is the plan.

There is a plan for RID specific packages in the future: Will, if you can maintain notes on what we plan on that it would be great, probably a separate issue, which will also call out that they are not supported in this first version.

For clarity, the user is not expected to be aware of the temp project, so no action will be needed on this issue by either consumer or producer (we removed the need for the producer to include Microsoft.NETCore.Platforms)

0reactions

wli3commented, Feb 15, 2018

@KathleenDollard created https://github.com/dotnet/cli/issues/8617 for 2.1.3xx https://github.com/dotnet/cli/issues/8618 is for future.

I am closing this issue in favor of 8617