- Daniel Mackay
I've been using Visual Studio for a very long time. Probably close to two decades. It has it's strengths and weaknesses, but I've always been able to get the job done. I've been using Rider for a few months now and I'm really enjoying it. I made the switch partially to try something new, and partially from some mild peer pressure from all the young guns in the office. It's a great IDE and I'm finding it to be a great alternative to Visual Studio.
Recently, I noticed that JSON configuration files (as are commonly found in ASP.NET Core projects) were not nested like they normally are in Visual Studio. I googled around for a solution, but after a reading a few inadequate solutions, I decided to write my own. I'm sharing it here in case anyone else is looking for a solution.
In Visual Studio, JSON configuration files are nested by default. This is a nice feature because it keeps the project structure clean and organized. In Rider, JSON configuration files are not nested by default. This is a problem because it makes the project structure messy and disorganized.
While Rider does support nested files, it only works for hardcoded file suffixes (e.g.
.map.js). There is no way to wildcard the 'environment' part of the filename (e.g.
First navigate to
File Nesting Settings:
We can get around the lack of a wildcard filename, but using the specific environment names we have in our project (e.g.
Once this is done, you can see the files are now nested:
While, none of this is ground breaking, I hope it helps someone else out there. I'm really enjoying Rider and I'm looking forward to learning more about it. If you have any tips or tricks, please share them in the comments below.