Add-Migration allocation_units angular angular6 azure Background Call build-tools core C# dell docker docker image donet ef dotnet dotnet ef @eaDir ef EntityFramework error find firewall index kill light codes linux Luci mssql msvs_version MySql network ng build node-gyp node-sass openvpn OpenWRT partitions size PK powershell Primary Key size sp_who2 sql SSH synology t-sql tables Thread ThreadPool Threads tips ubuntu Update-Database vpn windows-build-tools wpf xev xmodev

If You get error like this: No executable found matching command "dotnet-watch" This is solution.

1. Check if You have csproj inside directory of command execution

2. Check if there is a reference to the "watcher" tool in the project file (csproj)

<ItemGroup>
    <DotNetCliToolReference Include="Microsoft.DotNet.Watcher.Tools" Version="2.0.0"/>
</ItemGroup>

and then execute

dotnet restore

I think the most Gentleman's approach to call background method is Threadpool.

public void TheGentlemansApproach()
{
    // straight onto the threadpool - what could be better?
    ThreadPool.QueueUserWorkItem(_ => BackgroundMethod("The Gentleman's Approach"));
}