Skip to content

Commit 61375e3

Browse files
Host name updates , in progress.
1 parent 3e28502 commit 61375e3

4 files changed

+10
-4
lines changed

articles/app-service/app-service-web-nodejs-best-practices-and-troubleshoot-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -161,7 +161,7 @@ http.createServer(function (req, res) {
161161
}).listen(process.env.PORT);
162162
```
163163

164-
Go to the Debug Console site `https://yoursite.scm.azurewebsites.net/DebugConsole`
164+
To go to the Debug Console site for your app, select **Development Tools** > **Advanced Tools**, then select **Go**. In Kudu, select **Debug console** for **CMD** or **PowerShell**.
165165

166166
Go into your site/wwwroot directory. You see a command prompt as shown in the following example:
167167

articles/app-service/app-service-web-tutorial-dotnet-sqldatabase.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -379,7 +379,9 @@ Each action starts with a `Trace.WriteLine()` method. This code is added to show
379379
> [!TIP]
380380
> You can experiment with different trace levels to see what types of messages are displayed for each level. For example, the **Information** level includes all logs created by `Trace.TraceInformation()`, `Trace.TraceWarning()`, and `Trace.TraceError()`, but not logs created by `Trace.WriteLine()`.
381381
382-
1. In your browser, navigate to your app again at *http://<your app name>.azurewebsites.net*, then try clicking around the to-do list application in Azure. The trace messages are now streamed to the **Output** window in Visual Studio.
382+
1. In a different browser window, go to the Azure portal and open your app's **Overview** page. Under **Default domain**, select the link to open your app.
383+
384+
1. Then try clicking around the to-do list application in Azure. The trace messages are now streamed to the **Output** window in Visual Studio.
383385
384386
```console
385387
Application: 2017-04-06T23:30:41 PID[8132] Verbose GET /Todos/Index

articles/app-service/configure-language-dotnet-framework.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ This guide provides key concepts and instructions for ASP.NET developers. If you
2121

2222
## Show supported .NET Framework runtime versions
2323

24-
In App Service, the Windows instances already have all the supported .NET Framework versions installed. To show the .NET Framework runtime and SDK versions available to you, navigate to `https://<app-name>.scm.azurewebsites.net/DebugConsole` and run the appropriate command in the browser-based console:
24+
In App Service, the Windows instances already have all the supported .NET Framework versions installed. To show the .NET Framework runtime and SDK versions available to you, go to your app in the Azure portal. Select **Development Tools** > **Advanced Tools**. Select **Go**. In Kudu, select **Debug console** for **CMD** or **PowerShell**. Run the appropriate command in the browser-based console:
2525

2626
For CLR 4 runtime versions (.NET Framework 4 and above):
2727

articles/app-service/configure-language-dotnetcore.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,11 @@ This guide provides key concepts and instructions for ASP.NET Core developers. I
2323

2424
## Show supported .NET Core runtime versions
2525

26-
In App Service, the Windows instances already have all the supported .NET Core versions installed. To see the .NET Core runtime and SDK versions that are available to you, go to `https://<app-name>.scm.azurewebsites.net/DebugConsole` and run the following command in the browser-based console:
26+
In App Service, the Windows instances already have all the supported .NET Core versions installed. To see the .NET Core runtime and SDK versions that are available to you, go to your Kudu site.
27+
28+
Go to your app in the Azure portal and then select **Development Tools** > **Advanced Tools**. Select **Go**. In Kudu, select **Debug console** for **CMD** or **PowerShell**.
29+
30+
Run the following command in the browser-based console:
2731

2832
```azurecli-interactive
2933
dotnet --info

0 commit comments

Comments
 (0)