Document Details

Functions Dotnet Class Library
Home / Scan #41 / Functions Dotnet Class Library
Sad Tux - Windows bias detected
This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
GitHub View on GitHub 📚 View on Microsoft Learn

Bias Analysis

Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific tools and paths are mentioned before or instead of cross-platform or Linux equivalents (e.g., use of Windows environment variables, Windows installer for Core Tools, and Windows-specific runtime identifiers in ReadyToRun examples). Command-line installation examples are provided for Windows (cmd, PowerShell) but not for Bash or other Unix shells. There is a lack of explicit Linux/macOS examples or guidance, and some tool references (like Visual Studio) are Windows-centric.
Recommendations
  • Provide parallel Linux/macOS examples for all command-line instructions, including Bash/zsh equivalents for package installation and usage.
  • When discussing tool installation (e.g., Azure Functions Core Tools), include Linux/macOS installation methods (such as apt, yum, Homebrew) alongside Windows MSI and npm.
  • In ReadyToRun and deployment examples, show both Windows and Linux RuntimeIdentifiers (e.g., 'win-x86' and 'linux-x64') and explain how to choose the appropriate one.
  • Avoid referencing Windows-specific paths (like %USERPROFILE%\AppData\...) without also providing the Linux/macOS equivalents (e.g., ~/.local/share/...).
  • When listing development environments, clarify cross-platform support for Visual Studio Code and the CLI, and provide links or notes for Linux/macOS users.
  • Ensure that all environment variable usage and configuration file instructions are clear for both Windows and Linux/macOS shells.
  • Add explicit notes or sections for Linux/macOS users where behavior or setup differs from Windows.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2025-07-12 23:44 #41 cancelled Biased Biased
2025-07-12 00:58 #8 cancelled Clean Clean
2025-07-10 05:06 #7 processing Clean Clean
2025-07-09 23:22 #6 cancelled Clean Clean

Flagged Code Snippets

{
  "generatedBy": "Microsoft.NET.Sdk.Functions-1.0.0.0",
  "configurationSource": "attributes",
  "bindings": [
    {
      "type": "queueTrigger",
      "queueName": "%input-queue-name%",
      "name": "myQueueItem"
    }
  ],
  "disabled": false,
  "scriptFile": "..\\bin\\FunctionApp1.dll",
  "entryPoint": "FunctionApp1.QueueTrigger.Run"
}

<PropertyGroup>
  <TargetFramework>net8.0</TargetFramework>
  <AzureFunctionsVersion>v4</AzureFunctionsVersion>
  <PublishReadyToRun>true</PublishReadyToRun>
  <RuntimeIdentifier>win-x86</RuntimeIdentifier>
</PropertyGroup>

Install-Package Microsoft.Azure.WebJobs.Logging.ApplicationInsights -Version <VERSION>