About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
missing_linux_example
⚠️
windows_tools
Summary:
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based deployment and configuration patterns for ASP.NET apps in Azure App Service. All runtime version examples reference Windows file paths and tools (Kudu, CMD, PowerShell), with no mention of Linux equivalents or how to perform these tasks on Linux App Service plans. There are no Linux-specific examples or guidance, and Windows tools and patterns are presented as the default.
Recommendations:
- Add equivalent instructions and examples for Linux App Service plans, including how to check .NET runtime versions and access diagnostic tools on Linux.
- When referencing tools like Kudu, CMD, or PowerShell, clarify their availability (Windows-only) and provide alternatives for Linux (e.g., SSH, Bash).
- Include Linux file paths and commands where appropriate, or explicitly state when a feature is Windows-only.
- Structure sections to address both Windows and Linux scenarios, or clearly indicate which instructions apply to which OS.
- Add a table or section summarizing feature parity and differences between Windows and Linux App Service for ASP.NET apps.
Create pull request
Flagged Code Snippets
ls "D:\Program Files (x86)\Reference Assemblies\Microsoft\Framework"
A value of `v4.0` means the latest CLR 4 version (.NET Framework 4.x) is used. A value of `v2.0` means a CLR 2 version (.NET Framework 3.5) is used.
## Set .NET Framework runtime version
By default, App Service uses the latest supported .NET Framework version to run your ASP.NET app. To run your app using .NET Framework 3.5 instead, run the following command in the [Cloud Shell](https://shell.azure.com) (v2.0 signifies CLR 2):
ls "D:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework"
Redeploy your app with the updated *web.config*. You should now see the same detailed exception page.
## Access diagnostic logs
You can add diagnostic messages in your application code using [System.Diagnostics.Trace](/dotnet/api/system.diagnostics.trace). For example:
## Get detailed exceptions page
When your ASP.NET app generates an exception in the Visual Studio debugger, the browser displays a detailed exception page. A generic error message replaces that page in App Service. To display the detailed exception page in App Service, open the *web.config* file and add the `<customErrors mode="Off"/>` element under the `<system.web>` element. For example: