Using Rider under Windows without Visual Studio: prerequisites

  1. If you have JetBrains Rider installed on your Windows machine and there is also .NET Core SDK or Visual Studio installed, we expect JetBrains Rider to start working without taking any further configuration steps. Please note that when you use VisualStudio, installing some components within it may be required (ASP.NET or F# targets).
  2. If you want to use JetBrains Rider on a copy of Windows that does not have Visual Studio installed and you are developing projects having legacy project files:
    1. Download and install the JetBrains redistributable of MSBuild (to learn more, please visit the blog post.)
    2. Download and install Microsoft .NET Framework Developer Pack 4.5.1 or later from this list: https://www.microsoft.com/net/targeting. 
  3. If you are interested in developing Web applications for classic ASP.NET, or .NET Core with IIS Express deployment, download and install IIS Express: https://www.microsoft.com/en-us/download/details.aspx?id=48264.
  4. If you are interested in developing .NET Core with IIS Express deployment, follow the documentation on setting up ASP.NET Core apps in IIS Express: https://www.jetbrains.com/help/rider/Running_IISExpress.html.
    NOTE: this is not required for ASP.NET Core if you use the Kestrel server (one of the default options for modern ASP.NET Core apps.)
  5. If you are interested in developing non-SDK FSharp applications (projects with the legacy project files):
    1. Add NuGet https://www.nuget.org/packages/FSharp.Compiler.Tools to your project (changing TargetFrameworkVersion may be required).
    2. In some cases, installing F# targets via Visual Studio or VS Build Tools may be more preferable than using this package.
39 comments
Comment actions Permalink

Hi! Please try to set different MSBuild in Rider settings.

0
Comment actions Permalink

Thanks for your reply.

I can get rid of the ".Net framework not installed" error after I set the MSBuild to v3.5 manually. but it has the error below and the Loading solution is syncing forever. I guess maybe Rider is not supporting the project that builds in .NET 3.5?

 

0
Comment actions Permalink

Unfortunately, my project can only use .NET3.5. I tried to use .NET 4.0 to build my existing .NET 3.5 project, and it caused some issue on my project. 

0
Comment actions Permalink

I have just reported the issue to JetBrains as report no. DEXP-402411.

0
Comment actions Permalink

I can see the .NET framework 3.5 when creating a new project, though

 

0
Comment actions Permalink

Have you tried MSBuild 4.0 (C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe)?

Do you have "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v3.5" folder?

Edited by Ivan Shakhov
0
Comment actions Permalink

I have visual studio 2017 already installed. Tried moving to Rider but get the followings errors on my .net core and .net standard libraries

 

Could not load SDK Resolver. A manifest file exists, but the path to the SDK Resolver DLL file could not be found. Manifest file path 'C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\SdkResolvers\Microsoft.Build.NuGetSdkResolver\Microsoft.Build.NuGetSdkResolver.xml'. SDK resolver path: C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\Common7\IDE\CommonExtensions\Microsoft\NuGet\Microsoft.Build.NuGetSdkResolver.dll 

any ideas?

0
Comment actions Permalink

Hi there,

The article was updated according to the last requirements. Please take a look and feel free to contact Rider support if you have questions.

 

Kind regards, 

Sofia.

0

Please sign in to leave a comment.

Have more questions?

Submit a request