Support for private repositories

[KristianHebert]

We use Azure Devops, with a private library for internal packages. NuGetMonitor has some trouble dealing with these.

In the main window, the "Available Versions" just says "Loading...", indefinately.

In the dependency tree, the packages from the private repo are just omitted.

Please keep up the good work, love the extension.

[tom-englert]

Private reops must be listed in your nuget.config file. If they are password protected, you must also provide the credentials in the nuget.config: https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-nuget-add-source

[KristianHebert]

It is in the nuget.config, and it works in the built-in Visual Studio NuGet Manager.

[tom-englert]

I'm not sure if clear-text password is supported

Visual Studio has its own internal authentication, not related to nuget.config

[KristianHebert]

I don't know why it's a clear text password. I just added the repo to visual studio options.

[tom-englert]

Just follow the instructions in the link

[tom-englert]

See also here
https://learn.microsoft.com/en-us/nuget/consume-packages/consuming-packages-authenticated-feeds#credentials-in-nugetconfig-files

[KristianHebert]

I cannot get it to work with the dotnet command, maybe it's because it's microsoft auth?

[tom-englert]

NuGetMonitor is using the official NuGet Client, so when this works from the command line, it should work here, too.
And maybe you have to restart VS for the changes to apply?

[KristianHebert]

I've been restarting VS many times in my efforts to make it work.
is there a log somewhere that could help me with understanding what is wrong?

[KristianHebert]

According to this: https://learn.microsoft.com/en-us/azure/devops/artifacts/nuget/nuget-exe?view=azure-devops, a relatively new nuget client is needed to connect to a devops library. Could that be the issue?

[KristianHebert]

It seems that it sometimes loads some of the packages.

I happen to know that the local repository is much slower than fx Nuget.org. Could that be the issue?

Also, note that it wants to "update" version 23.1.9 to version 1.2.10