Document Details
Quickstart Dotnetcore
This page contains Windows bias
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
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Visual Studio (Windows-only) is presented as the primary IDE for .NET Framework, and many screenshots and step-by-step instructions focus on Windows tools and UI. PowerShell is given a dedicated section, but Linux-specific PowerShell examples are commented out and not visible to users. In the PowerShell section, users are explicitly told to use Azure CLI for Linux, but no Linux PowerShell deployment steps are shown. File path examples (e.g., 'cd bin\Release\net8.0\publish') use Windows-style backslashes, and compressing/deploying steps are shown only for Windows. While cross-platform tools (Azure CLI, VS Code) are included, Windows patterns and tools are often mentioned first or exclusively, and Linux parity is not always achieved.
Recommendations
- For every PowerShell deployment example, provide an equivalent Bash/Linux shell example, especially for steps like zipping and deploying files.
- Uncomment and fully document the Linux PowerShell deployment steps, or remove PowerShell as a recommended tool for Linux if not supported.
- When showing file paths or commands, provide both Windows and Linux syntax (e.g., use both '\' and '/').
- Ensure that all screenshots and UI instructions that are Windows-specific are clearly labeled, and provide parallel instructions for macOS/Linux where possible.
- In all sections, avoid language that implies Windows is the default or preferred platform; present cross-platform options equally and in parallel.
- Expand the Azure CLI and VS Code sections to include more Linux/macOS-specific tips and troubleshooting.
- Where possible, add explicit Linux/macOS instructions for tasks like compressing files (e.g., using 'zip' command) and deploying to App Service.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-12 00:00 | #243 | cancelled |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
 Clean
|
| 2026-01-06 18:15 | #225 | cancelled |
Clean
|
| 2025-09-10 00:00 | #107 | completed |
Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Biased
|
| 2025-07-13 21:37 | #48 | completed |
Biased
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|
Flagged Code Snippets
Connect-AzAccount
cd bin\Release\net8.0\publish Compress-Archive -Path * -DestinationPath deploy.zip
Publish-AzWebApp -ResourceGroupName myResourceGroup -Name <app-name> -ArchivePath (Get-Item .\deploy.zip).FullName -Force
Connect-AzAccount
cd bin\Release\net8.0\publish Compress-Archive -Path * -DestinationPath deploy.zip