You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When first running the Chocolatey VSCode extension, if LSP is enabled, we should attempt to download the LSP assembly from somewhere.
That somewhere, will be a NuGet v3 feed, which is configured in the User Settings of VSCode. The settings will also include a version number, which could can be set to a wildcard. Wildcard will attempt to install the latest version available on the feed. A specific version number will attempt to only install that version number.
It should be possible to use any NuGet V3 feed. i.e. first check the index.json file for the feed, and find the flatcontainer url for a package (chocolatey-language-server) and available versions.
For there, download the nupkg and extract as zip file, and place the LSP assembly somewhere.
When first running the Chocolatey VSCode extension, if LSP is enabled, we should attempt to download the LSP assembly from somewhere.
That somewhere, will be a NuGet v3 feed, which is configured in the User Settings of VSCode. The settings will also include a version number, which could can be set to a wildcard. Wildcard will attempt to install the latest version available on the feed. A specific version number will attempt to only install that version number.
It should be possible to use any NuGet V3 feed. i.e. first check the index.json file for the feed, and find the flatcontainer url for a package (chocolatey-language-server) and available versions.
For there, download the nupkg and extract as zip file, and place the LSP assembly somewhere.
No idea where that somewhere is just yet 😢
Example NuGet URL's...
Questions
The text was updated successfully, but these errors were encountered: