Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation demonstrates a clear Windows bias: examples and instructions consistently use Windows paths, PowerShell commands, and Windows-specific tooling (Visual Studio, MSBuild.exe, win-x64 packages). Linux equivalents (e.g., bash, Linux paths, linux-x64 packages) are mentioned only in passing, and there are no step-by-step instructions or code samples for Linux or macOS users. The workflow assumes a Windows environment, making it less accessible for developers on other platforms.
Recommendations
- Provide parallel step-by-step instructions for Linux and macOS, using bash/zsh commands and appropriate file paths (e.g., /home/user/msBuildDemo).
- Include examples using the Azure.Bicep.CommandLine.linux-x64 and Azure.Bicep.CommandLine.osx-x64 NuGet packages in project file samples.
- Show how to run MSBuild and dotnet CLI commands on Linux/macOS terminals, including installation notes for MSBuild on non-Windows platforms.
- Replace or supplement PowerShell commands with bash equivalents (e.g., mkdir, cd, rm -rf) for directory and file management.
- Clarify cross-platform compatibility in the prerequisites and throughout the guide, ensuring that Linux/macOS users are not left to infer the necessary changes.
- Add screenshots or terminal output examples from Linux/macOS environments.
- Explicitly mention any platform-specific caveats or requirements (e.g., setting BicepPath, executable permissions) for non-Windows systems.
Create Pull Request