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
-[O# Parity] Support loading projects/files without a solution file [#5722](https://github.com/dotnet/vscode-csharp/issues/5722)
7
-
-[O# Parity]Some csproj projects will not correctly load [#5721](https://github.com/dotnet/vscode-csharp/issues/5721)
7
+
-[O# Parity]Projects running on Mono may not load correctly[#5721](https://github.com/dotnet/vscode-csharp/issues/5721)
8
8
-[O# Parity] Run and debug tests in context [#5719](https://github.com/dotnet/vscode-csharp/issues/5719)
9
9
- Debug from .csproj and .sln [#5876](https://github.com/dotnet/vscode-csharp/issues/5876)
10
10
11
11
## Latest
12
+
* Update Roslyn version (PR: [#6285](https://github.com/dotnet/vscode-csharp/pull/6285))
13
+
* Includes better support for .NET 8 and .NET Framework-targeting projects (PR: [#69616](https://github.com/dotnet/roslyn/pull/69616))
14
+
* This should fix a number of reports where projects don't have full IntelliSense. .NET Framework projects on Windows should load without errors. .NET Framework targeting projects on Mac and Linux which would use Mono are still processed as if they are .NET Core projects and may not load correctly; support for Mono is coming in a future update.
15
+
16
+
## 2.0.448
12
17
* Update Roslyn version (PR: [#6264](https://github.com/dotnet/vscode-csharp/pull/6264))
13
18
* Upgrade MSBuildLocator to fix homebrew dotnet resolution (PR: [#69769](https://github.com/dotnet/roslyn/pull/69769))
0 commit comments