This post is the first part of a blog post series that covers different technical challenges that we had to resolve during the migration of the Rider backend process from Mono to .NET Core. By sharing our experiences, we hope to help out those who are in the same boat. There’s too much to share in one post, so we will make this into a series of posts. In this series: How Socket Error Codes Depend on Runtime and Operating System How Sorting Order Depends on Runtime and Operating System How ListSeparator Depends on Runtime and Operating System Let’s dive in! (more…)

There are many users of Rider that value the IDE for developing .NET Core applications on macOS. They also have need of running their Microsoft SQL Server databases locally for their work. This blog post will give developers insight on how to create SQL Server containers with Docker, and how to work with them in Rider. The best thing about working with Docker is that it is supported in many of our IDE's - including DataGrip! (more…)

We are excited to introduce to you the new Rider release - please welcome Rider 2018.2! This release comes with a solid set of bug-fixes, and a bunch of new features and improvements which are highlighted in the list below: Debugger: call stacks are now displayed in a more understandable way, thread-specific breakpoints have been introduced, and inspecting and expanding unsafe pointers is now supported. Docker support has reached the debugger: It is now possible to debug ASP.NET Core apps in a local (Linux) Docker container: inspecting variables, the stack frames, threads, as well