Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools (Visual Studio, MSI installer paths, Windows environment variable locations) are mentioned first or exclusively in several sections. Command-line examples are provided for Windows (cmd, PowerShell), but Linux/macOS equivalents (bash, zsh) are missing or relegated to links. ReadyToRun publishing is shown only for Windows targets, with no Linux/macOS example. Environment variable access references Windows-centric variables and paths. While Azure Functions Core Tools is cross-platform, installation and usage instructions focus on Windows methods first.
Recommendations
- Add explicit Linux/macOS examples for command-line operations, such as installing packages and running Core Tools.
- Include ReadyToRun publishing examples for Linux (e.g., <RuntimeIdentifier>linux-x64</RuntimeIdentifier>) and macOS.
- Show environment variable access and local.settings.json usage in Linux/macOS contexts, including relevant file paths.
- Balance Visual Studio/Windows tool references with Visual Studio Code and CLI workflows, and mention cross-platform editors and tools upfront.
- Provide bash/zsh equivalents for PowerShell/cmd commands, especially for package installation and project setup.
- Clarify that all major workflows are supported on Linux/macOS, and link to platform-specific guides where available.
Create Pull Request