Skip to content

Documentation link for diagnostic ID NU1510 does not forward correctly. #14856

@InternalLoss

Description

@InternalLoss

NuGet Product Used

dotnet.exe

Product Version

.NET SDK 10.0.201, MSBuild version: 18.3.0-release-26153-122+4d3023de6

Worked before?

No response

Impact

It bothers me. A fix would be nice

Repro Steps & Context

Version Used: .NET 10.0.201

Steps to Reproduce:

  1. Build a .NET 10.0 SDK targeting application that has an unnecessary reference, such as the one in example.
  2. Click on the hyperlink for NU1510 (I personally use Cmd-click in iTerm2 on macOS.)
  3. Observe the redirect fail, and instead redirect to Bing.

Example CSPROJ (based on the output of dotnet new console):

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net10.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.CSharp" Version="4.7.0" />
  </ItemGroup>
</Project>

Diagnostic Id: NU1510

If this is a report about a bug in an analyzer, please include the diagnostic ID and message if possible (e.g. "IDE0030: Use coalesce expression").

Expected Behavior: Link for code redirects me to appropriate page, such as https://learn.microsoft.com/en-gb/dotnet/core/compatibility/sdk/10.0/nu1510-pruned-references

Actual Behavior: I am redirected to Bing.com

Verbose Logs

❯ dotnet build --verbosity diag
Restore succeeded with 1 warning(s) in 0.2s
    Determining projects to restore...
    /Users/billy/Downloads/temp/temp.csproj : warning NU1510: PackageReference Microsoft.CSharp will not be pruned. Consider removing this package from your dependencies, as it is likely unnecessary.
    All projects are up-to-date for restore.
  temp net10.0 succeeded with 1 warning(s) (0.1s) → bin/Debug/net10.0/temp.dll
    /Users/billy/Downloads/temp/temp.csproj : warning NU1510: PackageReference Microsoft.CSharp will not be pruned. Consider removing this package from your dependencies, as it is likely unnecessary.

Build succeeded with 2 warning(s) in 0.6s

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions