-
Notifications
You must be signed in to change notification settings - Fork 138
Find-Package fails to find existing NuGet package #678
Comments
Thanks for opening this issue, can you please share the versions of packagemangement and powershellget you are using? |
+1 please fix |
My apologies for the late reply. I must have missed the notification with your comment. If it is of any help I can provide the packagemangement and powershellget versions, but I'd need instructions on how to do it? Might be worth following up with @schrufygroovy as well as it seems they're still able to reproduce it. |
In my case I am dealing with a private azure devops nuget feed. With package source:
He is able to find the package and package information and download the json from nuget feed, but the information is somehow missing some
As workaround one can configure old v2 azure devops nuget feed
|
@schrufygroovy @simone-cw can you try this scenario out with PowerShellGetV3? https://www.powershellgallery.com/packages/PowerShellGet/3.0.17-beta17 You can register a repository with the private azure devops V3 feed, and use the |
When I run the following command:
Find-Package -Name Microsoft.Web.Xdt -ProviderName NuGet
I get this error:
Find-Package: No match was found for the specified search criteria and package name 'Microsoft.Web.Xdt'. Try Get-PackageSource to see all available registered package sources.
The Microsoft.Web.Xdt can be found on the NuGet site, which indicates an issue with the Find-Package command
After enabling the debug log with $DebugPreference = "Continue", the command logs the following stacktrace
It seems that the error goes away if I add a wilcard at the start of the package name
Find-Package -Name "*Microsoft.Web.Xdt" -ProviderName NuGet
However, this is not a good solution as it might return additional non-relevant packages.
The text was updated successfully, but these errors were encountered: