Breaking changes thread

[seblyng]

This thread will be updated with breaking changes.

I will soon be doing one where the server needs to be updated to the latest version after roslyn finally supports connecting to a pipe named by the client, which means I can delete a hacky workaround to start the server

[seblyng]

#120 is now merged.

Update roslyn server to the latest version if you plan on updating this plugin. It will also print an error message about this if the version is too old

[bosvik]

Not sure if this is the best place to write it but a word of caution. Skip upgrading roslyn to v5.0.0-1.25113.3. It’s broken and crashes. Staying on 5.0.0-1.25111.6 for now.

[5PK]

Had some trouble with both v5.0.0-1.25113.3 and 5.0.0-1.25111.6, I kept getting the below error, hate to put a random error out there but there it is...I've been using 4.14.0-2.25118.5 and it seems to be working okay.

[ERROR][2025-02-19 13:08:46] ...lsp/handlers.lua:623 "[LanguageServerExtensionManager] Microsoft.CodeAnalysis.CSharp.Completion.Providers.ReferenceDirectiveCompletionProvider threw an exception. System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter 'position')\n at Microsoft.CodeAnalysis.Text.SourceText.LineInfo.IndexOf(Int32 position) in //src/Compilers/Core/Portable/Text/SourceText.cs:line 1002\n at Microsoft.CodeAnalysis.Text.SourceText.LineInfo.GetLineFromPosition(Int32 position) in //src/Compilers/Core/Portable/Text/SourceText.cs:line 1039\n at Microsoft.CodeAnalysis.Completion.Providers.AbstractDirectivePathCompletionProvider.ShouldTriggerCompletion(SourceText text, Int32 caretPosition, CompletionTrigger trigger, OptionSet options) in //src/Features/Core/Portable/Completion/Providers/Scripting/AbstractDirectivePathCompletionProvider.cs:line 68\n at Microsoft.CodeAnalysis.Extensions.IExtensionManagerExtensions.PerformFunction[T](IExtensionManager extensionManager, Object extension, Func`1 function, T defaultValue) in //src/Workspaces/Core/Portable/ExtensionManager/IExtensionManagerExtensions.cs:line 39"
[WARN][2025-02-19 13:18:11] ...lsp/handlers.lua:625 "[Microsoft.CodeAnalysis.LanguageServer.HostWorkspace.FileWatching.DelegatingFileChangeWatcher] We are unable to use LSP file watching; falling back to our in-process watcher."

[seblyng]

Please do not comment on this thread. It is meant as a thread to only communicate breaking changes so that people can subscribe to it and only get relevant info. Will try to configure this so that only I am allowed to comment here

[seblyng]

• exe option is now deprecated
• args option is now deprecated
• Default install location is now deprecated

For all of these: please configure like this:

require("roslyn").setup({
    config = {
        cmd = {
            "dotnet",
            "<target>/Microsoft.CodeAnalysis.LanguageServer.dll",
            "--logLevel=Information",
            "--extensionLogDirectory=" .. vim.fs.dirname(vim.lsp.get_log_path()),
            "--stdio",
        },
    },
})

NOTE: For users installing roslyn via mason, then no action is needed.

This is a part of this larger PR I am working on, configuring roslyn with vim.lsp.config and vim.lsp.enable: #178

This is also a soft-deprecation, so the options will still work for now, but it will warn users if they are using those

The options will stop working with that PR. However, I will not merge that PR for at least some weeks

[seblyng]

8dc729a removes hacky mason custom registry setup after breaking mason v2 update. Set it up manually in your mason config like specified in the README

[seblyng]

#178 is now merged, meaning version nvim 0.11 or later is required

Other breaking changes:

Hard breaking changes:

• exe and args options are no longer working
• Default installation location is no longer working

Soft deprecations

• config option is still working, but deprecated in favor of vim.lsp.config. This will be removed at a later time (a couple of months at least)

[seblyng]

The config option has been deprecated since may. This commit: d136e5a removes it.

Use vim.lsp.config instead