Bias Analysis
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits Windows bias in several ways: Windows-specific tools and patterns (Visual Studio, MSI installer, Windows paths) are mentioned before or more prominently than cross-platform or Linux alternatives. Examples for publishing and building (ReadyToRun) use Windows runtime identifiers and do not show Linux equivalents. Command-line installation instructions include PowerShell and Windows CMD, but do not provide explicit bash or Linux shell examples. Visual Studio is referenced as the primary development environment, with less emphasis on Visual Studio Code or CLI workflows that are more common on Linux/macOS. There is also reliance on WindowsAzure.Storage and Windows-style paths in examples.
Recommendations
- Provide Linux/macOS equivalents for all Windows-specific instructions, such as ReadyToRun publishing with linux-x64 RuntimeIdentifier.
- Include bash/zsh shell examples alongside PowerShell and CMD for package installation and CLI usage.
- Explicitly mention and demonstrate development workflows using Visual Studio Code and Azure Functions Core Tools on Linux/macOS.
- Avoid using Windows paths (e.g., '..\bin\FunctionApp1.dll') in examples; use platform-agnostic or Linux-style paths where possible.
- Clarify that Azure Functions Core Tools and SDKs are cross-platform, and provide installation instructions for Linux (apt, yum, Homebrew) and macOS.
- Balance references to Visual Studio with equivalent instructions for Visual Studio Code and CLI-based workflows.
- Review dependency mentions (e.g., WindowsAzure.Storage) and clarify cross-platform compatibility or alternatives.
Create Pull Request