Join GitHub today
dotnet-watch, dotnet-ef, and dotnet-user-secrets will move into the .NET Core CLI in 2.1.300 #290
Starting in .NET Core CLI 2.1.300-preview2, the following tools were added as bundled, top-level commands. These tools previously shipped as NuGet packages.
Upgrading from stable releases of .NET Core CLI (e.g. 2.1.5)
Using these tools as a DotNetCliToolReference will no longer work. If your .csproj file has the following lines, they can be removed.
<ItemGroup> <DotNetCliToolReference Include="Microsoft.DotNet.Watcher.Tools" Version="(all versions)" /> <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="(all versions)" /> <DotNetCliToolReference Include="Microsoft.Extensions.SecretManager.Tools" Version="(all versions)" /> <DotNetCliToolReference Include="Microsoft.Extensions.Caching.SqlConfig.Tools" Version="(all versions)" /> </ItemGroup>
Upgrading from .NET Core CLI 2.1.300-preview1
For early-adopters who tried the 2.1.300-preview1 release, you will no longer need to run
If you had installed these tools in 2.1.300-preview1, you can uninstall them manually by deleting corresponding files from
For discussion use aspnet/DotNetTools#399
Cool, but installing them (which feels intuitive but isn't needed) shouldn't crash. What's a friendly message to solve this?