Endpoints Explorer only recognizes literal route strings

[johnholliday]

The Endpoints Explorer window only recognizes literal strings for routes. For example, the following declaration shows up in the Endpoints Explorer window:

public static class MyEndpoints {
  public static void MapMyEndpoints(this IEndpointRouteBuilder routes) {
    var group = routes.MapGroup("api/test");
    group.MapGet("/{id}", TestGetMethod);
}}

However, the following is invisible to the Endpoints Explorer window:

public static class MyEndpoints {
  private const string ApiBase = "api/Test";
  public static void MapMyEndpoints(this IEndpointRouteBuilder routes) {
    var group = routes.MapGroup(ApiBase);
    group.MapGet($"{ApiBase}/{id}", TestGetMethod);
}}

This can be a significant limitation, since it forces the declaration literal route strings that may be spread across many solution files, and other projects that may consume the API.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 26f1374f-556a-35fc-cc42-b8911746db80
• Version Independent ID: 26f1374f-556a-35fc-cc42-b8911746db80
• Content: Use .http files in Visual Studio 2022
• Content Source: aspnetcore/test/http-files.md
• Product: aspnet-core
• Technology: aspnetcore-test
• GitHub Login: @tdykstra
• Microsoft Alias: tdykstra

[Rick-Anderson]

That's not a documentation issue. You should open this issue at https://developercommunity.visualstudio.com/VisualStudio

[johnholliday]

I will do that. However, I think it is actually something that should be mentioned in the documentation. Otherwise people will likely waste a lot of time chasing a non-issue. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Rick Anderson ***@***.***> Sent: Saturday, September 9, 2023 3:01:48 PM To: dotnet/AspNetCore.Docs ***@***.***> Cc: John Holliday ***@***.***>; Author ***@***.***> Subject: Re: [dotnet/AspNetCore.Docs] Endpoints Explorer only recognizes literal route strings (Issue #30293) That's not a documentation issue. You should open this issue at https://developercommunity.visualstudio.com/VisualStudio — Reply to this email directly, view it on GitHub<#30293 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABIMPXAX5MLW2NDNALYKIADXZS4JZANCNFSM6AAAAAA4RSHHFM>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[guardrex]

We have no way to version such content, and we have no way to track the fix for it because it would be internal to the VS team. I agree with Rick. I think problems with VS features generally need to go to that team for resolution.

[guardrex]

btw @johnholliday ... I recommend the Report a Problem feature in VS. I don't think those community issues generate bug reports ... directly anyway ... guessing 😄.

https://learn.microsoft.com/en-us/visualstudio/ide/how-to-report-a-problem-with-visual-studio?view=vs-2022

[Rick-Anderson]

@johnholliday please post links here where you have reported the issue.