You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Bump xamlTools to 18.3.11128.18 (PR: [#8669](https://github.com/dotnet/vscode-csharp/pull/8740))
14
+
* Update target framework in Razor integration test (PR: [#8729](https://github.com/dotnet/vscode-csharp/pull/8729))
15
+
* Use global.json with rollforward instead of pipeline versions (PR: [#8722](https://github.com/dotnet/vscode-csharp/pull/8722))
16
+
* Update RoslynCopilot url to 18.3.72-alpha (PR: [#8726](https://github.com/dotnet/vscode-csharp/pull/8726))
17
+
* Add group ids to configuration groups (PR: [#8720](https://github.com/dotnet/vscode-csharp/pull/8720))
18
+
*[WIP] Update job execution order for bump-main-version (PR: [#8717](https://github.com/dotnet/vscode-csharp/pull/8717))
19
+
* Update CHANGELOG for version 2.97.x (PR: [#8716](https://github.com/dotnet/vscode-csharp/pull/8716))
20
+
* Bump Roslyn to 5.3.0-2.25553.6 (PR: [#8743](https://github.com/dotnet/vscode-csharp/pull/8743))
21
+
* Support LSP includeDeclaration field in find all references (PR: [#80965](https://github.com/dotnet/roslyn/pull/80965))
22
+
* Add support for lineFoldingOnly folding ranges (PR: [#80955](https://github.com/dotnet/roslyn/pull/80955))
23
+
* Expand `#error version` output to include compiler assembly path and use full commit SHA everywhere (PR: [#80894](https://github.com/dotnet/roslyn/pull/80894))
24
+
* Fix culture-sensitive StringBuilder.Append and ToString calls across codebase and add banned symbols (PR: [#80800](https://github.com/dotnet/roslyn/pull/80800))
25
+
* Add support for autocompleting raw string quotes (PR: [#80871](https://github.com/dotnet/roslyn/pull/80871))
26
+
* Don't add parenthesis when committing type with accessible nested type using dot (PR: [#80846](https://github.com/dotnet/roslyn/pull/80846))
27
+
* Completion for `#:project` paths in file based programs (PR: [#80844](https://github.com/dotnet/roslyn/pull/80844))
28
+
* Allow semantic tokens in Razor to be better behaved (PR: [#80815](https://github.com/dotnet/roslyn/pull/80815))
29
+
* When searching for the original file from a PDB, only allow absolute paths (PR: [#80804](https://github.com/dotnet/roslyn/pull/80804))
30
+
* Bump Razor to 10.0.0-preview.25552.2 (PR: [#8734](https://github.com/dotnet/vscode-csharp/pull/8734))
31
+
* Add CodeAction to simplify fully-qualified component tags (PR: [#12379](https://github.com/dotnet/razor/pull/12379))
32
+
* Fix component and component attribute rename in cohosting (PR: [#12374](https://github.com/dotnet/razor/pull/12374))
33
+
* Fix formatting of mixed indentation in VS Code (PR: [#12418](https://github.com/dotnet/razor/pull/12418))
34
+
* Allow cohosting quick info to show html tag information even when on a taghelper or component tag. (PR: [#12415](https://github.com/dotnet/razor/pull/12415))
35
+
* Fix(ish) formatting of RenderFragments (C# templates) (PR: [#12397](https://github.com/dotnet/razor/pull/12397))
36
+
* Drop Html edits that would split a C# literal across multiple lines (PR: [#12396](https://github.com/dotnet/razor/pull/12396))
37
+
* Fix completion resolve for provisional completion (PR: [#12403](https://github.com/dotnet/razor/pull/12403))
38
+
6
39
# 2.96.x
7
40
* Update Debugger to v2.95.0 (PR: [#8710](https://github.com/dotnet/vscode-csharp/pull/8710))
8
41
* Remove default editor.formatOnType configuration for C# (PR: [#8709](https://github.com/dotnet/vscode-csharp/pull/8709))
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+13-3Lines changed: 13 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,9 +64,9 @@ To debug unit tests locally, press <kbd>F5</kbd> in VS Code with the "Launch Tes
64
64
To debug integration tests
65
65
1. Import the `csharp-test-profile.code-profile` in VSCode to setup a clean profile in which to run integration tests. This must be imported at least once to use the launch configurations (ensure the extensions are updated in the profile).
66
66
2. Open any integration test file and <kbd>F5</kbd> launch with the correct launch configuration selected.
67
-
- For integration tests inside `test/lsptoolshost`, use either `Launch Current File slnWithCsproj Integration Tests` or `[DevKit] Launch Current File slnWithCsproj Integration Tests` (to run tests using C# + C# Dev Kit)
67
+
- For integration tests inside `test/lsptoolshost`, use either `[Roslyn] Run Current File Integration Test` or `[DevKit] Launch Current File Integration Tests` (to run tests using C# + C# Dev Kit)
68
68
- For integration tests inside `test/razor`, use `[Razor] Run Current File Integration Test`
69
-
- For integration tests inside `test/omnisharp`, use one of the `Omnisharp:` current file profiles
69
+
- For integration tests inside `test/omnisharp`, use one of the `[O#] Run Current File Integration Test` current file profiles
70
70
71
71
These will allow you to actually debug the test, but the 'Razor integration tests' configuration does not.
72
72
@@ -196,15 +196,25 @@ More details for this are [here] (https://devdiv.visualstudio.com/DevDiv/_git/Vi
196
196
## Snapping for releases
197
197
Extension releases on the marketplace are done from the prerelease and release branches (corresponding to the prerelease or release version of the extension). Code flows from main -> prerelease -> release. Every week we snap main -> prerelease. Monthly, we snap prerelease -> release.
198
198
199
+
### Versioning Scheme
200
+
The extension follows a specific versioning scheme for releases:
201
+
-**Prerelease versions**: Use standard minor version increments (e.g., 2.74, 2.75, 2.76...)
202
+
-**Stable release versions**: Use the next tens version (e.g., 2.74 prerelease becomes 2.80 stable)
203
+
-**Main branch after RC snap**: Jumps to one above the next stable version (e.g., if snapping 2.74 as RC, main becomes 2.81)
204
+
199
205
### Snap main -> prerelease
200
206
The snap is done via the "Branch snap" github action. To run the snap from main -> prerelease, run the action via "Run workflow" and choose main as the base branch.
When running the snap action, you can optionally check the "Is this a release candidate snap" checkbox. If checked:
210
+
- The prerelease branch will receive the snapped code with the current version (e.g., 2.74)
211
+
- The main branch version will be updated to be higher than the next stable release (e.g., 2.81, since the next stable would be 2.80)
212
+
203
213
This will generate two PRs that must be merged. One merging the main branch into prerelease, and the other bumps the version in main.
204
214

205
215
206
216
### Snap prerelease -> release
207
-
To snap from prerelease to release, run the same action but use **prerelease** as the workflow branch. This will generate a single PR merging from prerelease to release.
217
+
To snap from prerelease to release, run the same action but use **prerelease** as the workflow branch. This will generate a PR merging from prerelease to release, and automatically update the version to the next stable release version (e.g., 2.74 -> 2.80) on the merge branch before the PR is merged.
208
218
209
219
### Marketplace release
210
220
The marketplace release is managed by an internal AzDo pipeline. On the pipeline page, hit run pipeline. This will bring up the pipeline parameters to fill out:
Copy file name to clipboardExpand all lines: SUPPORT.md
+12-2Lines changed: 12 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,7 @@ If you encounter issues with document classification (e.g., incorrect syntax hig
107
107
For issues with diagnostics, please provide values of the background analysis scope options, `dotnet.backgroundAnalysis.analyzerDiagnosticsScope` and `dotnet.backgroundAnalysis.compilerDiagnosticsScope`
If the language server crashes, general logs are often helpful for diagnosing the issue. However, in some cases, logs alone may not provide enough information and we may need a crash dump. Follow these steps to collect a crash dump:
113
113
- Set the `dotnet.server.crashDumpPath` setting in VSCode to a user-writable folder where crash dumps can be saved.
@@ -117,7 +117,7 @@ If the language server crashes, general logs are often helpful for diagnosing th
117
117
> [!WARNING]
118
118
> The dump can contain detailed information on the project - generally we will provide an email so that it can be shared privately
119
119
120
-
####Recording a language server trace
120
+
### Recording a language server trace
121
121
122
122
When investigating performance issues, we may request a performance trace of the language server to diagnose what is causing the problem. These are typically taken via [dotnet-trace](https://learn.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-trace) (a cross platform tool to collect performance traces of .NET processes)
123
123
@@ -132,6 +132,16 @@ The C# extension has a built in command, `csharp.recordLanguageServerTrace` to h
132
132

133
133
5. Share the trace. Note that the trace may contain PII, so generally we will provide an email or other confidential way to share the trace with us.
134
134
135
+
### Sharing information privately
136
+
Detailed logs, dumps, traces, and other information can sometimes contain private information that you do not wish to share publicly. Instead, you can utilize the Developer Community page to share these privately to Microsoft.
137
+
138
+
1. Go to https://developercommunity.visualstudio.com/dotnet/report
139
+
2. Fill in the issue title, reference the GitHub issue in the description, and upload the attachments
140
+

141
+
3. Once created, a comment on the GitHub issue a link to the new Developer Community ticket.
142
+
143
+
144
+
135
145
## Microsoft Support Policy
136
146
137
147
Support for this project is limited to the resources listed above.
0 commit comments