[enhancement]: Deprecate DotNetCoreCLI #21938
Description
Task name
DotNetCoreCLI
Describe your feature request here
Please deprecate DotNetCoreCLI. It is incompatible with Central Package Management (CPM) / Package Source Mapping:
- [BUG]: dotnet restore with source mapping and private feed does not work #20910
- Package Source Mapping: Difficulty using it on Azure DevOps CI because it ends up needing
feed-prefixes in the source mapping configuration. NuGet/Home#11406 - Stop using the setAuthForSourcesInTempNuGetConfig in all package downloading scenarios, such as nuget install, restore, because it completely breaks PackageSourceMapping #15542
- Issue with Package source mapping by adding prefix feed. When executing dotnet restore facing issue, where it is inputting 5times feed as prefix NuGet/Home#12328
It was declared outdated by @magleaso in 2021:
- Package Source Mapping: Difficulty using it on Azure DevOps CI because it ends up needing
feed-prefixes in the source mapping configuration. NuGet/Home#11406 (comment) - Stop using the setAuthForSourcesInTempNuGetConfig in all package downloading scenarios, such as nuget install, restore, because it completely breaks PackageSourceMapping #15542 (comment)
People keep loosing a lot of time trying to figure out how to configure DotNetCoreCLI while it simply does not work in these cases and is considered outdated by the maintainers.