Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page exhibits a Windows bias by consistently presenting Windows-specific instructions, examples, and tooling first or exclusively. PowerShell is used as the default shell in all command-line examples, and directory paths use Windows conventions (e.g., C:\msBuildDemo). Linux and macOS equivalents are only briefly mentioned in package lists, with no corresponding shell or filesystem examples. The project file examples and build instructions focus on Windows tools (Visual Studio, PowerShell, MSBuild.exe), with no demonstration of Linux-native workflows (e.g., Bash, Linux paths, dotnet CLI usage on Linux). Clean-up instructions and environment variable configuration also use Windows syntax and paths.
Recommendations
- Provide parallel Linux/macOS examples for all command-line instructions, using Bash and POSIX paths (e.g., /home/user/msBuildDemo).
- Include instructions for using common Linux shells (e.g., Bash, zsh) and terminal applications.
- Show how to install prerequisites (e.g., .NET SDK, Bicep CLI) on Linux and macOS, including package manager commands.
- Demonstrate project creation and build steps using Linux-native tools and commands (e.g., dotnet CLI, MSBuild via mono if applicable).
- Add clean-up instructions using Linux commands (e.g., rm -rf ~/msBuildDemo).
- Ensure environment variable configuration examples are provided for Linux/macOS (e.g., export BicepPath=/usr/local/bin/bicep).
- Use cross-platform language in instructions and avoid assuming Windows as the default environment.
Create Pull Request