Skip to content
This repository has been archived by the owner on Jul 12, 2022. It is now read-only.

Updating skips DotNetCliToolReference #348

Closed
skolima opened this issue Jul 24, 2018 · 4 comments
Closed

Updating skips DotNetCliToolReference #348

skolima opened this issue Jul 24, 2018 · 4 comments
Labels

Comments

@skolima
Copy link
Collaborator

skolima commented Jul 24, 2018

Example: xunit released new version 2.4. NuKeeper generates PackageReference updates, but no DotNetCliToolReference is created.

Sample from the project file:
<DotNetCliToolReference Include="dotnet-xunit" Version="2.3.1" />

Problem with adding support for this: neither dotnet nor NuGet nor Visual Studio support maintaining those entries. There's been some discussion, looks like dotnet tool is supposed to eventually handle them (when non-global mode is added), but currently those require manually editing the project file.

Related issues:
https://github.com/dotnet/cli/issues/917
NuGet/Home#4901

@skolima
Copy link
Collaborator Author

skolima commented Jul 26, 2018

That particular tool has also been dropped from the dotnet new xunit template:
dotnet/templating@3a44d4a#diff-a01e88d21e4fe2067a57eeec4d28dc53

@skolima
Copy link
Collaborator Author

skolima commented Aug 7, 2018

The asp.net tools are also deprecated and being removed (e.g. aspnet/Tooling#1075 )

@stale
Copy link

stale bot commented May 10, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label May 10, 2020
@skolima
Copy link
Collaborator Author

skolima commented May 10, 2020

Not supported at all in SDK > 2.2; not recommended in general.

dotnet/announcements#107

@skolima skolima closed this as completed May 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant