I am using Visual Studio with ASP.NET Core and run the website using just F5 or Ctrl+F5 (not using the command line directly). I would like to use the "dotnet watch" functionality to make sure all changes are picked up on the fly to avoid starting the server again. It seems that with the command line you would use "dotnet watch run" for this, but Visual Studio uses launchSettings.json and does it behind the scenes if I understand it correctly.
How can I wire up "dotnet watch" there?
Run .Run dotnet watch run in the WebApp folder. The console output indicates watch has started. Running dotnet watch run on a web app launches a browser that navigates to the app's URL once ready. dotnet watch does this by reading the app's console output and waiting for the ready message displayed by WebHost.
NET Core is installed on Windows is: Press Windows + R. Type cmd. On the command prompt, type dotnet --version.
At this point, if your NuGet dependencies are compatible with both your netcore and netframework targets you may be done! The big news here is that most of your NuGet dependencies are compatible with both. All of the most downloaded NuGet packages are either multi-targeted, or have packages for each target.
Open the Debug view by selecting the Debugging icon on the left side menu. Select the green arrow at the top of the pane, next to . NET Core Launch (console). Other ways to start the program in debugging mode are by pressing F5 or choosing Run > Start Debugging from the menu.
If you want to use ASP.NET 2.x or 3.x you need to change it a bit.
The watch tool is a global tool now and you don't need to add it as a reference any longer
The syntax is slightly different
"Watch": { "executablePath": "dotnet.exe", "workingDirectory": "$(ProjectDir)", "commandLineArgs": "watch run", "launchBrowser": true, "launchUrl": "http://localhost:5000/", "environmentVariables": { "ASPNETCORE_ENVIRONMENT": "Development" } }
In VisualStudio 2019
Otherwise add this to your launchSettings.json
:
{ "iisSettings": { ... }, "profiles": { ... , "Watch": { "commandName": "Executable", "executablePath": "dotnet.exe", "workingDirectory": "$(ProjectDir)", "commandLineArgs": "watch run" } } }
The automatically generated profile
with "commandName":"Project"
has all the other properties needed: launchBrowser
, applicationUrl
, environmentVariables
, dotnetRunMessages
and hotReloadProfile
. Any modifications should be made there.
Corresponding Blog-Post from Juan Cruz Fiant: https://dev.to/juxant/auto-refresh-with-dotnet-watch-for-asp-net-core-projects-20no
Open launchSettings.json and add this to profiles
.
"Watch": { "executablePath": "C:\\Program Files\\dotnet\\dotnet.exe", "commandLineArgs": "watch run", "launchBrowser": true, "launchUrl": "http://localhost:5000", "environmentVariables": { "ASPNETCORE_ENVIRONMENT": "Development" } }
Open project.json and add this to tools
.
"Microsoft.DotNet.Watcher.Tools": "1.0.0-preview2-final"
After restoring, we can Watch from within Visual Studio.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With