👾 Rider meets Unity3D 🎮

Two of the most outstanding reasons for using Rider as a Unity developer:

• Reduced context switches between your IDE and the Unity editor. Rider duplicates many of the frequently accessed Unity editor parts so that you don't find yourself tabbing through applications. This includes the explorer view, play-mode controls, test execution/visualization and more.
• Deep knowledge about Unity engine code to help improving game performance. Rider continuously receives new code inspections that detect common mistakes specifically for the Unity platform. Refactorings and symbol searches even consider non-C# references, like in YAML files. Indicators tell us about hot paths in our code and the built-in profiler helps nail down bottlenecks.

Think of Rider as your co-pilot for fast and pleasant Unity game development! 🏎 🏎 🏎

See Also

• Working with Unity
• Getting started with Rider and Unity
• Working with external class libraries in Unity and Rider
• Control Unity editor play mode with Rider 2018.1
• View Unity console logs directly in Rider 2018.1
• Unity Explorer and new code inspections in Rider 2018.1
• Unity Package Explorer in Rider 2018.2
• Unity Assembly Definition Files and Rider 2018.2
• Integrating Rider 2018.2 and the Unity Editor
• Unity-specific code analysis in Rider 2018.2
• Unity Performance Best Practices with Rider, Part 1
• Unity performance best practice with Rider, part 2