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
⚠️
powershell_heavy
⚠️
windows_tools
Summary:
The documentation demonstrates a moderate Windows bias. Windows command prompt and PowerShell instructions are presented before macOS and Linux equivalents. The example project is based on ASP.NET Core, and the build script uses MSBuild, which is more common on Windows (though cross-platform). Visual Studio Code is mentioned as cross-platform, but the workflow and examples are more familiar to Windows users. There is no explicit omission of Linux/macOS steps, but the ordering and tool choices favor Windows.
Recommendations:
- Present Linux/macOS and Windows instructions in parallel or in a neutral order (alphabetically or grouped by shell type).
- Include explicit notes about cross-platform compatibility of MSBuild and .NET CLI, and provide alternative scripts if needed for non-Windows environments.
- Add more context or examples for Linux/macOS users, such as using bash scripts or alternative editors.
- Highlight that the Azure CLI and .NET CLI are fully cross-platform, and provide troubleshooting tips for common Linux/macOS issues.
- Consider using generic environment variable setting instructions first, then provide OS-specific tabs if needed.
Create pull request
Flagged Code Snippets
setx ConnectionString "<connection-string-of-your-app-configuration-store>"
<Target Name="Export file" AfterTargets="Build">
<Message Text="Export the configurations to a temp file. " />
<Exec WorkingDirectory="$(MSBuildProjectDirectory)" Condition="$(ConnectionString) != ''" Command="az appconfig kv export -d file --path $(OutDir)\azureappconfig.json --format json --separator : --connection-string $(ConnectionString)" />
</Target>
$Env:ConnectionString = "<connection-string-of-your-app-configuration-store>"