All of our IDE's are built on the same core IntelliJ IDEA Community Edition. This means that when we improve one IDE, our other IDE’s usually also benefit from our improvements. Rider is no exception! I recently reached for DataGrip, our amazing database administration tool, only to remember that Rider has many of the same features. (more…)

Rider contains many features for styling code so that it’s easy to read, and therefore easy to understand and maintain that code. This post is part of a series around finding a coding style that fits you like a glove, and how Rider can help: Find your perfect coding style using Rider Find your perfect C# style using Rider Find your perfect database development style using Rider Find your perfect web development style using Rider In this post, we’ll look at how you can create a style that works for all your database programming. For the purposes of this post, we’ll focus on Micr

The latest Rider 2018.3 EAP build extends Rider's language injections functionality quite a bit, with SQL language support in string literals. This gives us highlighting, code completion and code analysis, and a Run in console action for SQL inside of a C# string! For all existing and newly added language injections, we can edit fragments in a separate editor! And last but not least, we can now configure automatic language injections, so that Rider automatically recognizes language fragments inside strings. More than enough for a long blog post! Grab a coffee or tea, sit back, and let's

In previous blog posts in this series, we looked at connecting to a Microsoft SQL Server and getting familiar with the features in Rider 2017.3 to work with SQL databases. In this final post in our series, we will look at how to query and work with the data in the tables in our database. This post is part of a series around working with databases and data in Rider: Configuring SQL Server 2017 for Rider Getting started with database support in Rider Working with Tables and Indexes in Rider Working with Data in Rider (Note: we'll use the Visual Studio keymap on Windows throughout

In previous blog posts in this series, we looked at connecting to a Microsoft SQL Server and getting familiar with the features in Rider to work with SQL databases. In this blog post, we will look at how to work with a database to create tables and indexes. This post is part of a series around working with databases and data in Rider: Configuring SQL Server 2017 for Rider Getting started with database support in Rider Working with Tables and Indexes in Rider Working with Data in Rider (Note: we'll use the Visual Studio keymap on Windows throughout this post - check the web help

If you are new to using Rider, it’s worth mentioning that you get all the .NET features of ReSharper, along with the web development features of WebStorm, which provides the developer with great overall experience. What’s more, you also get all the data features of DataGrip as well, so you have a single IDE to work with for all facets of your project work! In this blog post, we will look at setting up the database connection and running some queries against our database. This post is part of a series around working with databases and data in Rider: Configuring SQL Server 2017 for Rid

Rider is not only a great .NET IDE, it also is a wonderful tool for working with databases that are associated with .NET Core solutions. Many .NET Core developers use Microsoft SQL Server on their laptops; more specifically, the Developer edition of the database server tool. Let's start a series of blog posts about Rider's database tools (powered by DataGrip)! Before you can start using Rider with a SQL Server database, you may discover that you must configure SQL Server 2017 to allow Rider to connect through a TCP port which is not set up at install. In this post, let’s look at configuring

Application performance depends on a huge variety of factors: code design, web server performance, possible network lags, and so on. Effective execution of SQL queries is an additional concern. Naturally, you want your profiler to cover as many of these performance aspects as possible. In dotTrace 6.1 we introduced the long-awaited 'SQL queries profiling' feature. Now you can get exact data on how long a particular query took to execute, as well as what method ran the query. Important notes: SQL queries can be profiled only in the Timeline profiling mode. The feature is availab