-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSPROJ package autocomplete not working #44
Comments
Hmm, sorry about that; it seems the newest SDKs for .NET Core have changed a bit in ways the extension wasn't expecting and this is causing problems for some people (I thought I'd fixed this problem but perhaps not for everyone). If you look in the output window under "MSBuild Project Tools", do you see any output there? |
Where exactly should I be looking for "MSBuild Project Tools"? And could it be because I have two MSBuild in my path? |
I wouldn't think so, the extension doesn't use |
Some other steps to gather information for troubleshooting: |
Thats the output from VSCode |
Ok, it sounds like it can't connect to one or more package feeds specified in |
Ok so fixed it. Apparently I installed Xenko game engine and xenko pushed some of its feed into the sources. I commented them out and autocomplete is back on track. What a pain from Xenko. Thank you though. Nuget feed was the problem. |
No worries - glad it was easy to fix :) I'll add some logging so that next time it will explicitly log the set of package sources that it's using. |
Funnily enough it cant find SixLabors.ImageSharp or any package with x.x.x-betaXXXX version. Just letting you know |
Hi - there is a command called "toggle prerelease" that will make them show up or hide them. Does that not work for you? |
Not for packages with 'betaXXXX' format in their version. Works fine for 0.X.X versioned packages. FbxSharp is on v0.9.0 SixLabors.ImageSharp is on 1.0.0-beta0005 |
Can you open the VS Code settings editor, then open the raw settings.json file, and then post all the |
|
Thanks! I'll try this out when I get home :) |
I have seen this problem a few months ago too. I didn't know there was a repo I would've reported this then. I love the extension. I hate to come forward issues like this. But I'd love to keep using this as the only solution to multiple features. I have made quite a bit of enhanced csproj build systems that targets multi-OS+multi-framework, using this amazing extension (and that's awesome!). I'd love to see this become a beast. |
No worries - thanks for reporting it! The only way this extension gets better is through users like you :) I'll let you know as soon as I've worked out what the problem is. |
Ok, so I've looked into this, and it appears to be a bug in the NuGet client library. The client is supposed to do an HTTP GET from https://api-v2v3search-1.nuget.org/autocomplete?q=SixLabors&prerelease=true, but is instead using https://api-v2v3search-1.nuget.org/autocomplete?q=SixLabors&includePrerelease=true I'll log an issue with the NuGet folks to see if we can get this resolved. |
Created NuGet/Home#7540. |
I've opened a new issue for the pre-release version problem, so I'm closing this one :) |
Autocomplete for packages not working
The text was updated successfully, but these errors were encountered: