LibMan Not Retrieving Packages

[FAA-MichaelC]

Description

Trying to follow the linked article which includes adding the client-side library for SignalR. Using VS 17.13.3. When I enter the settings using Add Client-Side Library, no files are retrieved. Discovered that using @microsoft/signalr@latest doesn't work. Typing @microsoft/signalr brings up a version list to select from; I selected the latest version. Clicked on 'Choose specific files:' but nothing shows up in the window to select the files needed. So at this point not sure if the problem is with VS or the instructions are out of date.

As a work-around I tried using npm to get the signalr library, but the version of the files aren't compatible with the article.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/tutorials/signalr?view=aspnetcore-9.0&tabs=visual-studio

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/tutorials/signalr.md

Document ID

5e3fbe1d-c97f-9940-4f0c-067d4b2112b1

Platform Id

08ef2218-4b14-eab1-104b-0460e8ba5780

Article author

@bradygaster

Metadata

• ID: 0dd2991d-c22d-ad0f-80b6-bd1b503db8f3
• PlatformId: 08ef2218-4b14-eab1-104b-0460e8ba5780
• Service: aspnet-core
• Sub-service: tutorials

Related Issues

---

Associated WorkItem - 423881

[wadepickett]

Thanks @FAA-MichaelC for relating your experience. We appreciate you taking the time to do so.
I just tested using the latest supported version of Visual Studio. One targeting .NET 8 and one targeting .NET 9.
Following the instruction in the tutorial, both installed the client-side libraries correctly and compiled.
The only thing I can think of is that you might have missed the step for selecting unpkg as the provider, or perhaps there was trouble accessing that service at that moment.

The resulting path to the installed files would be:
{Your Project}\wwwroot\lib\microsoft\signalr\dist\browser\signalr.js
{Your Project}\lib\microsoft\signalr\dist\browser\signalr.min.js

I do see the tutorial needs an update for .NET 9 (It is currently at .NET 8). for which the step indicating the target .NET version to select would be updated to .NET 9, but no other steps would be affected. I will create a tracking issue a get the update taken care of.

I will close this issue since I am unable to recreate it, but if you have more insight on how to recreate the issue, please feel free to re-open. Thanks again.

[wadepickett]

Update: I see a duplicate issue of this on at #35156. Given someone else was experiencing the same problem at about the same time, I suspect the service may have been temporarily having trouble. As I detail above however, it tests out fine at right now.