Skip to content

Launching Multiple Projects in JetBrains Rider

Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free.

Learn more about Software Architecture & Design.
Join thousands of developers getting weekly updates to increase your understanding of software architecture and design concepts.

This sounds trivial, and it is.  But if you have a Visual Studio background and are trying out JetBrains Rider for the first time, this may not be apparent how to setup launching multiple projects in JetBrains Rider. This entire week I’ve almost exclusively used Rider.  I’ve used some of the early EAP’s, but not on an actual project. One of the first roadblocks I hit was trying to figure out how to launch multiple projects from my solution. Thankfully, it didn’t take me too long to figure out. However, I then had a colleague ask me the very next day how to do it, as he was also trying it out for the first time.

Run Configurations

Under the Run > Edit Configurations... menu, brings up a dialog where you can manage different configurations.  Under the .NET Projects, you will have one default entry that points to an existing project.  Create any new .NET Project entries to any other executable projects you have in your solution.


Next, to run multiple configurations together at once, create a Compound configuration and add your .NET Projects to it. As I mentioned, it’s pretty trivial but maybe not obvious to someone not familiar with JetBrains IDE’s.

Rider Review

I’m looking forward to the next couple weeks using Rider.  I plan on giving a full review after I’ve given it is paces with real project work. Are you using Rider? How are you enjoying it?  I’d love to hear your comments below or on Twitter.

3 thoughts on “Launching Multiple Projects in JetBrains Rider”

  1. I switch to Rider from VS 2017 and I’m enjoying it. As an IntelliJ IDEA user for long time, I’m almost familiar with working on Rider. The most important thing for me is Rider uses much less RAM than VS2017. Sometimes VS2017 eats more than 2GB of RAM but Rider only use about 600MB of RAM. But I still need to use VS2017 for some features.

      1. As I’m working on project that uses ASP.NET Core, Angular and Postgres, Rider provides me an all-in-one IDE so I don’t need to switch between IDEs/tools to work. Angular support in Rider is superb and database support is great. Rider is not fully support ASP.NET Core 2.0 yet but it will come with EAP builds ( which will available this September.

Leave a Reply

Your email address will not be published. Required fields are marked *