Skip to content
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.

Sign up for GitHub

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

Jump to bottom

.NET coding convention settings for EditorConfig #226

Closed
1 of 2 tasks
AnthonyMastrean opened this issue Feb 20, 2019 · 2 comments
Closed
1 of 2 tasks

.NET coding convention settings for EditorConfig #226

AnthonyMastrean opened this issue Feb 20, 2019 · 2 comments
Labels
out-of-scope

Comments

@AnthonyMastrean
Copy link

AnthonyMastrean commented Feb 20, 2019 •
edited
Loading

  • I have a question that is specific to this extension; thus, inappropriate for the main EditorConfig issue tracker.
  • I tried running code --disable-extensions and the issue did NOT present itself.

Issue

Is there any chance that this extension could be extended to support the .NET coding conventions that Visual Studio 2017 supports? I'm not even sure if the extension is the right place for this request (as compared to some kind of new built in feature of Visual Studio Code or an extension to the OmniSharp service).
@AnthonyMastrean
Copy link
Author

AnthonyMastrean commented Feb 20, 2019 •
edited
Loading

Actually, this comment indicates that EditorConfig support will get into Visual Studio Code by way of OmniSharp.

@jednano
Copy link
Member

jednano commented May 28, 2019

Yeah this seems out of scope to this particular project. Would have to be a separate extension. Looks like they're already working on it.

@jednano jednano closed this as completed May 28, 2019
@SunsetTechuila SunsetTechuila closed this as not planned Won't fix, can't repro, duplicate, stale Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
out-of-scope
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@AnthonyMastrean @jednano @SunsetTechuila