roslyn | NET compiler provides C # and Visual Basic languages | Code Editor library

I don't have much knowledge about project files, but at least i can share some contents of my project file.
I had to reference other projects like this:

TL;DR

There is not much you can do except casting dynamicObject to object at the call site:

Try updating VS Code and Omnisharp to the latest versions. If does not help - install VS 2022 and try running VS Code again.

Accessing MSBuild properties and metadata in DiagnosticAnalyzers is actually quite similar to how they're read and tested in ISourceGenerators/IIncrementalGenerators, since Source Generators are technically .NET analyzers as well.

I assume that the documentation you've mentioned is the Source Generators Cookbook.

First, we need to make the MSBuild property available to the global analyzer config options of the analyzer:

The error clearly indicates you are using an old version of the DLL that contains the enum, from before C#9 was made available.

Just upgrade the package in your projects to use the latest one and it should work fine. Here is the latest version of that package:

• https://www.nuget.org/packages/Microsoft.CodeDom.Providers.DotNetCompilerPlatform/3.6.0

If upgrading manually is not possible, check for indirect dependencies on your project dependency tree, and upgrade whatever package is at the top that is referencing the old package. You can do that by navigating through the dependencies in the project's dependencies node in Solution Explorer.

Another way to find which project exactly is referencing the "problematic" (in this case, old) dll is by doing a windows search by the DLL name in the solution folder, and checking for the difference in file sizes: usually, the different versions will have different sizes, which then allows you to compare them across your projects and with the packages from NuGet.

An init-only property doesn't require that properties are set at creation time with the property initializer syntax. It allows them to be set that way instead of requiring that all read-only properties are set by constructors.

So with your code,

When you create a SyntaxTree you can set its language version with the ParseOptions argument.

First of all, it appears that this was a false alarm. I apparently neglected to finish rebooting my workstation after installing the release version of Visual Studio 2022. After restarting, I am now able to publish with full support for implicit usings. Whoops.

That said, this does provide a good opportunity to offer some insight into what I discovered after the fact, which may help future readers with similar types of issues—and certainly helped me better understand the integration between the various command-line tools.

Notably, there doesn't appear to be any command-line parameters for handling implicit usings built into any of the following tools:

• .NET 6.0 SDK (dotnet.exe)
• Visual C# compiler (csc.exe)
• Microsoft Build Engine (msbuild.exe)

Instead, this is handled via the Microsoft Build Engine (msbuild.exe) when working off of a C# project file (*.csproj), at which point it generates the following intermediate file at:

You should be able to write it like this: