This is a really handy feature in @rider for fixing some flaky tests #dotnet #debugging

Rider 2025.1.3 is out with the following updates:

AI-powered features

• Rider now supports .aiignore files, helping you manage which files are included in the AI Assistant’s scope when working on your solution. [RIDER-121794]

• Semantic search is now enabled for both Search Everywhere and the AI Assistant, making it easier to find classes, methods, parameters, and other code elements even when your query differs in case, punctuation, or formatting. [LLM-2266]

Crucial fixes:

• Step over and Step into actions now work as expected when debugging ASP.NET projects with Docker Compose. [RIDER-120783]

• Sticky selection now works correctly with all editor actions, including arrow key navigation in .cs files. [RIDER-125224]

• Local edits across multiple files are now reliably preserved, even during formatting and undo/redo operations. [RIDER-124865]

• Files excluded from indexing above the solution folder are now correctly omitted from search results. [RIDER-123858]

• Editing C++ code during debugging is now fully supported again when the Allow editing in debug mode option is enabled. [RIDER-125020]

• C++ run/debug configurations once again reliably detect projects. [RIDER-124829]

Ok... after using @rider new functionality code with me, I'm seeing a lot of errors: ctrl+c won't copy, autocomplete won't complete on enter/tab, highlighting stops working after a while. I checked that the keybindinds are still correct. WTF!

The strangest thing with @rider happened after I experimented with the new 'code with me' feature. Ctrl+c (copy) won't work in .cs files. It works fine in .sql, .ts and other files (this includes the commit and search windows). When I press ctlr+c, nothing happens; I keep the previously copied content. I checked that my shortcuts have not been modified.

I have found others with the same issue (or at least similar): https://youtrack.jetbrains.com/issue/RIDER-117911/Copying-is-not-working-with-enabled-Code-with-me

/cc @jetbrains

@khalidabuhakmeh - What's the state of @rider and debugging #dapr hosted #dotnet applications?

Around two years ago I was on a really small team, just two or three developers, and the other developer decided they wanted us to use Rider. Because I didn't have a preference, I used Rider and rather enjoyed it. However, that developer has since moved teams and now it is just me (for the time being).

So I was considering moving back to Visual Studio or even switching to Visual Studio Code, but I wanted to see some arguments against this.

Here is my list so far, but it's probably out of date since I haven't used Visual Studio in a long time.

Pros of Rider:

• Much faster than using ReSharper
• Less sharp interface with a better font
• I'm used to it at this point
• I have a Nyan cat loading bar which is kind of fun

Cons of Rider:

• Enterprise license is expensive (probably)
• New versions of C# aren't immediately supported
• Refactorings are becoming less necessary with the rise of AI assistants
• Don't really like their source control manager

Wanted to hear what other users think. What keeps you using Rider?