Disable launching in IIS, since it appears to be broken on VS15.5 (th…

…ough works on 15.4)
SteveSanderson · Nov 6, 2017 · 0c60cce · 0c60cce
1 parent bacb732
commit 0c60cce
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 2 deletions.
diff --git a/template/MyApplication/Properties/launchSettings.json b/template/MyApplication/Properties/launchSettings.json
@@ -8,14 +8,19 @@
     }
   },
   "profiles": {
+    /*
+    If you're on VS 15.4 or earlier, you can enable the following.
+    For some reason, it doesn't work on VS 15.5 (not even if you replace LAUNCHER_PATH with an absolute path)
     "IIS Express": {
       "commandName": "IISExpress",
       "launchBrowser": true,
       "environmentVariables": {
-        "LAUNCHER_ARGS": "blazor serve",
-        "LAUNCHER_PATH": "dotnet"
+        "LAUNCHER_PATH": "dotnet",
+        "LAUNCHER_ARGS": "blazor serve"
       }
     },
+    */
+
     "MyApplication": {
       "commandName": "Executable",
       // If your dotnet executable is at a different location, or you're using Mac/Linux,

diff --git a/template/MyApplication/Properties/sw-launchSettings.json b/template/MyApplication/Properties/sw-launchSettings.json
@@ -1,5 +1,8 @@
 {
   "profiles": {
+    /*
+    If you're on VS 15.4 or earlier, you can enable the following.
+    For some reason, it doesn't work on VS 15.5 (not even if you replace LAUNCHER_PATH with an absolute path)
     "IIS Express": {
       "commandName": "IISExpress",
       "launchBrowser": true,
@@ -8,6 +11,8 @@
         "LAUNCHER_ARGS": "blazor serve"
       }
     },
+    */
+
     "MyApplication": {
       "commandName": "Executable",
       // If your dotnet executable is at a different location, or you're using Mac/Linux,