NuGet in VS Code/C# Dev Kit MVP Proposal #13208
Conversation
…ing functionality
|
|
||
| Once a package is selected from the list, the user will then be prompted to select the version number that they would like to install. | ||
|
|
||
|  |
There was a problem hiding this comment.
Should this prefer the highest stable version? Imagine a user prefers to install stable versions but a package's 10 highest versions are all pre-release, this would be a frustrating experience.
There was a problem hiding this comment.
Great callout, yes this will depend on the settings a user provides similar to Visual Studio checking the include pre-release checkbox. It will prefer highest stable by default.
|
I don't know why you people keep focusing on the bloody command palette... if a developer is skilled enough to use the palette he's probably is comfortable enough to use the raw terminal. Focus on the "I want to use my mouse and all I know is that the package has 'SqlServer' somewhere on its name" kind of developer... focus on the "I want to update all the packages on my solution and I don't care or know which is the latest version"... |
|
@Leonardo-Ferreira Please review the .NET Foundation's code of conduct: https://dotnetfoundation.org/about/policies/code-of-conduct In particular, the following behaviors are recommended to foster a positive environment:
|
We understand your frustration @Leonardo-Ferreira. For the sake of time, we are moving forward with a command palette experience and will be working iteratively with developer feedback to build a robust and rich NuGet experience into Visual Studio Code. You can see the related issue to understand where we imagine our work can take us. microsoft/vscode-dotnettools#62 We are building experiences for many different cohorts of C#/F#/etc/.NET developers. Please continue to provide your feedback on these experiences, but all we ask is that you choose words of mutual respect. Frustration is completely fine, but let the frustration be objective towards the proposal, not the people behind the proposal(ad hominem). |
|
I think this is ready to merge! |
|
I'm not sure where to link this |
This proposal introduces a Visual Studio Code NuGet package management experience including command palette flows and integration with C# Dev Kit. It covers the initial experiences for adding, removing, and updating a NuGet package. This document covers the minimum viable product (MVP) for a NuGet command palette experience, and leaves room for growth and expansion on these initial concepts, both in enhancing these 3 features, or in the addition of more NuGet command palette features.
Rendered Spec
Please 👍 or 👎 this comment to help us with the direction of this feature & leave as much feedback/questions/concerns as you'd like on this issue itself and we will get back to you shortly.
Thank You 🎉
Related: microsoft/vscode-dotnettools#62