Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

New .NET 11 WinForms design-time analyzer help links redirect to an incorrect webpage

Open Beginner friendly
#15,274 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
66/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp

Research direction

The issue names diagnostics WFO3000 and WFO3002 from the new WinForms design-time analyzer, so start by finding where their DiagnosticDescriptor help link URIs are defined in the analyzer source. Check the URI each descriptor sets, since the report says it currently opens a Bing search instead of the WinForms analyzer docs. Done means both links resolve to the correct documentation page, which you can confirm by checking the URI values, or by building and opening the link from the Error List.

Written by the indexing model from the issue text.

Description

:books: documentation untriaged
.NET version

.NET 11 SDK: 11.0.100-rtm.26477.103

Did it work in .NET Framework?

Not tested/verified

Did it work in any of the earlier releases of .NET Core or .NET 5+?

New .NET 11 WinForms design-time analyzer

Issue description

The help links for the new .NET 11 WinForms design-time analyzer diagnostics redirect to an incorrect webpage.

This issue can be reproduced with both errors and warnings.
For example:

  • WFO3000: The diagnostic code itself provides a clickable help link.
  • WFO3002: A help link is displayed in the diagnostic description.

Clicking these links redirects to Bing instead of the corresponding WinForms analyzer documentation.

https://github.com/user-attachments/assets/c94bedb0-01eb-48bc-a3b0-f423c09a85c6

Steps to reproduce
  1. Create a WinForms project targeting .NET 11.
  2. Trigger a new WinForms design-time analyzer diagnostic, such as WFO3000 or WFO3002.
  3. Open Error List in Visual Studio.
  4. Click the help link associated with the diagnostic:
  • For WFO3000, click the diagnostic code.
  • For WFO3002, click the help link shown in the description.
  1. Observe the webpage opened in the browser.
Dominant language
C#
Stars
4.9k
Forks
1.1k
Avg merge
12h 52m
Merged PRs (30d)
80

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/winforms

All issues in dotnet/winforms

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.