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
* Note - Building with higher major versions of Node.js is not advised - it may work but we do not test it.
26
27
* Npm (The version shipped with node is fine)
27
-
* .NET 7.0 SDK (dotnet should be on your path)
28
+
* .NET 8.0 SDK (dotnet should be on your path)
28
29
29
30
Once you have these installed, you can navigate to the cloned vscode-csharp repository to proceed with building, running, and testing the repository.
30
31
@@ -146,6 +147,8 @@ To package this extension, we need to create VSIX Packages. The VSIX packages ca
146
147
147
148
## Updating the `Roslyn` Language Server Version
148
149
150
+
In order to pull in new packages from upstreams into the msft_consumption feed we use for restoring, you will need to be a member of the 'CSharp VS Code Extension contributors' group in the [Azure Devops instance](https://dev.azure.com/azure-public/vside/_settings/teams).
151
+
149
152
To update the version of the roslyn server used by the extension do the following:
150
153
1. Find the the Roslyn signed build you want from [here](https://dnceng.visualstudio.com/internal/_build?definitionId=327&_a=summary). Typically the latest successful build of main is fine.
151
154
2. In the official build stage, look for the `Publish Assets` step. In there you will see it publishing the `Microsoft.CodeAnalysis.LanguageServer.neutral` package with some version, e.g. `4.6.0-3.23158.4`. Take note of that version number.
0 commit comments