Bias Analysis
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows development tools (Visual Studio, Windows Classic Desktop templates), providing only PowerShell/NuGet Package Manager Console commands, and omitting Linux/macOS equivalents or cross-platform instructions. There are no examples or guidance for using Linux development environments, nor are alternative package installation methods (e.g., dotnet CLI) shown. The use of Windows-specific terminology and tooling is prevalent throughout the page.
Recommendations
- Add explicit instructions and examples for Linux/macOS users, including how to create and run projects using Visual Studio Code or JetBrains Rider.
- Include dotnet CLI commands for installing NuGet packages, alongside PowerShell examples.
- Mention cross-platform project templates and clarify how to create .NET Core console apps on Linux/macOS.
- Provide guidance for configuring Application Insights and storage connection strings in non-Windows environments.
- Avoid using Windows-specific folder paths and terminology (e.g., 'samples\webjobssdk\chaining')—use forward slashes or clarify for cross-platform use.
- Ensure all steps (local development, deployment, configuration) have Linux/macOS parity and are not dependent on Windows-only tools.
Create Pull Request