037d1f2f2323da1fd62eda3406b465e26bb677e8 — Victor Freire 5 months ago 08cbc95
article: making-jetbrains-rider-work-with-devenv
1 files changed, 36 insertions(+), 0 deletions(-)

M content-org/content.org
M content-org/content.org => content-org/content.org +36 -0
@@ 5085,8 5085,44 @@ once they are done, I paste them on the blog:
Maybe I'm just over-complicating things for myself with no real
benefit... maybe not. Let's see how it goes!

** Making JetBrains Rider work with Nix and devenv              :dotnet:nix:
:EXPORT_DATE: 2023-06-22
:EXPORT_FILE_NAME: making-jetbrains-rider-work-with-devenv
:EXPORT_HUGO_SLUG: making-jetbrains-rider-work-with-devenv

How to setup .NET's CLI and MSBuild on JetBrains Rider while using
Nix with devenv.

A few weeks (even months) ago I had a problem that made [[https://www.jetbrains.com/rider/][JetBrains
Rider]] stop working properly on my environment. I figured out that
the problem was due the way [[https://devenv.sh/][devenv]][fn:45] sets up the environment.

Using the ~dotnet~ module on devenv is trivial, you just need to
enable it:

#+begin_src nix
  languages.dotnet.enable = true;

This will set the ~$DOTNET_ROOT~ environment variable with the root
path of your chosen .NET SDK. In this case, you need to set the
following options on Rider:

- Toolset and Build -> .NET CLI executable path:
- Toolset and Build -> MSBuild version:

* Footnotes

[fn:45] Fun fact: I introduced the dotnet module on devenv!

[fn:44] Absolutely nothing related to procrastination!

[fn:43] Actually, there was a [[https://github.com/jacentino/SqlFun/issues/16][previous attempt]], but I failed