aka.ms/aspire/diagnostics/aspire012 redirects to Bing

Open Beginner friendly
#22,336 1 comment 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
69/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
documentation

Research direction

Start by checking how Aspire diagnostic short links are registered and compare the ASPIRE012 link with the page being added in microsoft/aspire.dev#1880. Verify whether ASPIRE014 and ASPIRE015 also lack working destinations, using the linked docs issues as references. Done when the diagnostic links point to their documentation pages instead of Bing.

Written by the indexing model from the issue text.

Description

area-meta

Summary

The ASPIRE012 help link on Aspire 17.0 doesn't go to a diagnostic page:

curl -sI https://aka.ms/aspire/diagnostics/aspire012
HTTP/1.1 302
Location: https://www.bing.com?ref=aka&shorturl=aspire/diagnostics/aspire012

Search doesn't help either: aspire docs search ASPIRE012 with docs pointed at the vnext site (aka.ms/aspire/vnext) returns no results.

ASPIRE012 is the warning every legacy-SDK app sees after upgrading to 17.0, so this is likely the most-clicked diagnostic link in the release.

Ask

  • Register aka.ms/aspire/diagnostics/aspire012 and point it at the ASPIRE012 page being added in microsoft/aspire.dev#1880.
  • Check any other 17.0 diagnostic IDs (for example ASPIRE014/ASPIRE015 from microsoft/aspire.dev#2085 and microsoft/aspire.dev#2110) the same way.

Related umbrella: #13777, which predates ASPIRE012 and does not list it.

Found while upgrading maddymontaquila/aspirifridays to 17.0 staging (CLI 17.0.0+bcfa151c).

Dominant language
C#
Stars
6.4k
Forks
1k
Avg merge
2d 15h
Merged PRs (30d)
466

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 microsoft/aspire

All issues in microsoft/aspire

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.