Workaround for new limitation in dotnet tooling (seems executablePath…

… now has to be absolute)
SteveSanderson · Nov 6, 2017 · bacb732 · bacb732
1 parent 594307c
commit bacb732
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 2 deletions.
diff --git a/template/MyApplication/Properties/launchSettings.json b/template/MyApplication/Properties/launchSettings.json
@@ -18,7 +18,9 @@
     },
     "MyApplication": {
       "commandName": "Executable",
-      "executablePath": "dotnet",
+      // If your dotnet executable is at a different location, or you're using Mac/Linux,
+      // you'll need to update the path to 'dotnet' here
+      "executablePath": "%ProgramW6432%\\dotnet\\dotnet.exe",
       "commandLineArgs": "blazor serve"
     }
   }

diff --git a/template/MyApplication/Properties/sw-launchSettings.json b/template/MyApplication/Properties/sw-launchSettings.json
@@ -10,7 +10,9 @@
     },
     "MyApplication": {
       "commandName": "Executable",
-      "executablePath": "dotnet",
+      // If your dotnet executable is at a different location, or you're using Mac/Linux,
+      // you'll need to update the path to 'dotnet' here
+      "executablePath": "%ProgramW6432%\\dotnet\\dotnet.exe",
       "commandLineArgs": "blazor serve"
     }
   }