Skip to content

Commit 3403c27

Browse files
author
gregvanl
committed
Make headers H2
1 parent b028f85 commit 3403c27

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

docs/ide/codespaces/supported-features-codespaces.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Visual Studio provides a rich development experience when connecting to a codesp
2323
> [!NOTE]
2424
> The features described below are for Visual Studio and not the two other GitHub Codespaces clients, Visual Studio Code and the in-browser editor.
2525
26-
### Edit and navigation
26+
## Edit and navigation
2727

2828
You should notice little difference editing source code in a codespace as you get smart language features like IntelliSense, code navigation, diagnostics, and suggestions.
2929

@@ -41,12 +41,12 @@ Not yet available:
4141
* Code navigation* - Most commands supported, specifically Go To Base and Find in files with path specification not yet supported.
4242
* Quick Info* - colorization in quick info is not supported.
4343
* HTML, CSS, Razor editors* - Diagnostics, intellisense completion, quick info, smart indent. Currently no support for semantic colorization, navigation commands, etc.
44-
* JavaScript editor* - Script blocks (for example, JavaScript content in HTML files, CSHTML files, and similar) and semantic highlighting are not yet supported. Known issues with lightbulb features and linting.
44+
* JavaScript editor* - Script blocks (for example, JavaScript content in HTML and CSHTML files) and semantic highlighting are not yet supported. Known issues with lightbulb features and linting.
4545
* CodeLens
4646
* Code snippets
4747
* IntelliCode
4848

49-
### Application types and configuration
49+
## Application types and configuration
5050

5151
Most application types and project configurations are supported, but you will need to edit your project code directly without the help of visual designers. For more configuration guidance, see [How to customize a codespace](customize-codespaces.md).
5252

@@ -71,9 +71,9 @@ Not yet available:
7171
* Intranet resources (private network) - Currently, codespaces won't be able to connect to any resource that requires a VPN.
7272
* Extensions - No extensions are supported when using Codespaces with Visual Studio.
7373

74-
### Debugging
74+
## Debugging
7575

76-
Essential inner loop debugging workflow is supported including setting breakpoints, basic stepping into code, inspecting variables, and the local, autos, and watch windows. Some additional windows, customizations, and visualizers are not supported.
76+
Essential inner loop debugging is supported including setting breakpoints, basic stepping into code, inspecting variables, and the local, autos, and watch windows. Some additional windows, customizations, and visualizers are not supported.
7777

7878
* Breakpoints*
7979
* Basic stepping
@@ -92,12 +92,12 @@ Not yet available:
9292
* Threading features - Freeze/thaw threads, Rename thread, and show threads in source are not supported.
9393
* Additional stepping features - Automatic Step over properties and operators (.NET Core) and Step into Specific are not supported.
9494

95-
### Features
95+
## Features
9696

9797
Since you are working with the Visual Studio client connected to a remote environment, you get the same accessibility features as when working locally.
9898

9999
* Source Control - Full Git support through the new [Git window](https://devblogs.microsoft.com/visualstudio/improved-git-experience-in-visual-studio-2019/).
100-
* Accessibility - There is one known issue with assistive technology not being able to access the appcasting of a debugged app. Besides this, we don't believe there are any other compatibility issues that don't already exist in the local Visual Studio experience. Please let us know if you detect bugs by filing an issue on [developer community](https://developercommunity.visualstudio.com/).
100+
* Accessibility - There is one known issue with assistive technology not being able to access the appcasting of a debugged app. Besides this limitation, we don't believe there are any other compatibility issues that don't already exist in the local Visual Studio experience. Please let us know if you detect bugs by filing an issue on [developer community](https://developercommunity.visualstudio.com/).
101101
* Publishing - Publish to Azure through GitHub Actions is supported.
102102
* Connected services - App Insights, KeyVault, Storage, SQL, Redis, Cosmos, openAPI, and gRPC are partially supported.
103103
* Test Explorer* - Mostly supported.

0 commit comments

Comments
 (0)