Commit graph

5 commits

Author SHA1 Message Date
xtqqczze ba639a6440 vscode: Enable EditorConfig support in OmniSharp (#11627) 2020-01-24 12:22:27 -08:00
Travis Plunk a872b8d5be
Add compliance to Coordinated build (#8798)
Add compliance to Coordinated build
  - Also switch to mac internal pool for release build
  - Also turn some duplicate tasks into templates
  - Also fix issue with vscode configuration which causes yaml files not to be recogized as yaml
2019-01-30 14:10:52 -08:00
Christoph Bergmeister [MVP] 2f2b5d07fb Recommend Azure DevOps extension inside VS-Code for better YAML editing. (#8403)
This enhances the editing experience for YAML inside VS-Code (syntax highlighting and autocompletion).
For more details, see https://marketplace.visualstudio.com/items?itemName=ms-azure-devops.azure-pipelines
2018-12-07 10:55:52 -08:00
Chris f5b9942b0d Add PowerShell VSCode style settings (#5529) 2017-11-28 09:09:32 -08:00
Keith Hill cef7762d18 Add standard set of vscode workspace setting files (#5457)
* Add standard set of vscode workspace setting files

Add an extensions.json file that will prompt folks to install extensions that are recommended for this workspace (c++, c#, powershell, cmake (editing syntax) and markdown linter.

Add settings.json to start to configure C# syntax, PoweShell trim trailing whitespace and configure the markdown lint extension.

Update launch.json to provide ability to debug PowerShell scripts.

* Clean up grammar

* Instruct VSCode to ensure a final newline.

If this is not wanted for certain file types, we can restrict this option to only specified file types.
2017-11-15 11:18:37 +04:00