Adding VS Code to global VS family#3722
Merged
Merged
Conversation
Collaborator
|
But you wouldn't use this one by default on VS Code correct? You are just wanting .vscode ignored for all Visual Studio projects? |
Contributor
Author
|
Yes, "Visual Studio" is overloaded. We understand that our developers rarely are one-tool customers. Especially in x-plat development teams you may have one team using .NET and Visual Studio but other team members using VS Code for front-end development. They are both working on the same repos, yet all sources to acquire .gitignore for "Visual Studio" are too myopic. We think of VS as a family of products and something that represents VS, should be inclusive of this. |
Collaborator
|
Fair enough. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Our customer research supports that we have lots of developers using multiple tools, primarily VS and Code together. Ensuring that we have one VS family that encapsulate them is convenient for the developers and saves them a step and has been requested.