Unity Features

Editor helpers

Colors defined via UnityEngine.Color, UnityEngine.Color32, and Color.HSVToRGB are highlighted in the editor. You can also press Alt+Enter on a color usage and choose Pick color from palette to open the color editor and modify the color visually.

Find Usages

In Unity projects, the Find Usages Alt+F7 feature is extended with data pulled from Unity scenes, assets, and prefabs. If you search for a class or a method used as an event handler, ReSharper will show where it is used in Unity files, grouped by type, component name, and parent game objects.

Performance analysis

ReSharper shows you performance-sensitive areas: event functions that are called each frame, such as Update, FixedUpdate and LateUpdate, as well as coroutine methods. Inside these frequently called methods, performance indicators will also draw your attention to known expensive operations, like calls to GetComponent, Find or SendMessage, with context actions to move the initialization to Start or Awake.

Unity has a number of methods that get called very frequently. These methods are treated as a performance-critical context and are highlighted in the editor gutter.

You can enable and configure performance analysis on the Code Editing | Unity Engine page of ReSharper options Alt+R, O, under Enable performance analysis in frequently called code.

To configure the colors for specific problems, go to the Visual Studio options (Tools | Options), open the Environment | Fonts and Colors page, and then select the desired colors for items that start with ReSharper Unity.

Event functions

You can generate event functions using Unity Event Functions in the Generate Code menu Alt+Insert. This action is also available from Alt+Enter everywhere inside a Unity-based class.
Auto-completion will suggest event function names when declaring methods in Unity-based classes, and expand to include method signature. Start typing an event function within a class deriving from a known Unity class, such as MonoBehaviour.
Descriptions for event functions and parameters in Unity-based classes are shown in tooltips and Quick Documentation.

Inspections and quick-fixes

ReSharper shows warnings for unknown scenes, tags, and layers.
When the Solution-wide analysis is enabled, ReSharper understands implicitly used fields and event functions and do not highlight them as not accessed.
Empty event functions are shown as dead code, with a quick-fix to remove them.
Using the SyncVarAttribute inside any class other than NetworkBehaviour is treated as an error.
A quick-fix is suggested to create a serialized field from a usage of an unresolved symbol:
ReSharper ensures that all of your event functions have correct signatures: it highlights incorrect signatures and offers a quick-fix to correct them:
ReSharper warns you against using an inefficient string literal comparison with the tag property, and provides a quick-fix to rewrite this as a call to CompareTag.
ReSharper warns you if you try to use the new keyword to create a new instance of a class deriving from MonoBehaviour or ScriptableObject. A quick-fix is suggested to use gameObject.AddComponent<T>() or ScriptableObject.CreateInstance<T>() instead.
There are also inspections for the [InitializeOnLoad] and [InitializeOnLoadMethod] attributes, ensuring that they have the correct method or constructor signatures, and ReSharper will grey out a redundant [InitializeOnLoad] attribute if the class doesn't have a static constructor, with a quick-fix to either quickly remove the attribute, or create the constructor.
and more...

You can see the full list of Unity-specific code inspections in ReSharper here.

External annotations

A lot of Unity-specific assemblies are annotated with External annotations to improve code inspection when you make use of these assemblies.

Treating code marked with attributes from UnityEngine.dll, UnityEngine.Networking.dll and UnityEditor.dll as implicitly used.
Marking Component.gameObject and Object.name as not-nullable.
Debug.Assert marked as assertion method to help null-value analysis (for example "value cannot be null" after Debug.Assert(x != null)).
Debug.AssertFormat, LogFormat, and so on gets string formatting helper functionality.
Assertions.Assert methods marked as assertion methods to help null-value analysis.
EditorTestsWithLogParser.ExpectLogLineRegex gets regular expression helper functionality.
Various attributes now require the class they are applied to derive from a specific base type. For example, [CustomEditor] requires a base class of Editor.
Support for Unity 2017.2's modularised UnityEngine assemblies.

Support for .shader files

ReSharper provides support for ShaderLab syntax in .shader files, with support for Cg/HLSL blocks.

Syntax and syntax error highlighting for ShaderLab syntax.
Color assistance:
ReSharper provides code completion.
Brace matching and highlighting, comment/uncomment Control+/, and to-do explorer support.
[Cg/HLSL] Syntax highlighting for CGPROGRAM/CGINCLUDE blocks and .cginc files.
[Cg/HLSL] Code completion in Cg/HLSL blocks.

Support for assembly definition files

Assembly definition files (.asmdef) are used to separate project scripts into multiple assemblies to reduce compilation time. Unity will rebuild only required assemblies when you make changes in a script.

ReSharper provides support for .asmdef files: JSON schema validation, code completion, Find Usages, Rename refactoring, Navigation on references elements, and inspections/quick-fixes for self-reference and filename/assembly name mismatch. For more information about .asmdef files support, refer to the blog post.

Live templates

ReSharper offers a couple of Unity-specific live templates, for example, sprop for a Unity property with a serialized backing field, or sfield for a Unity serialized field.

Here is a full list of predefined Unity-specific file templates.

File templates

ReSharper offers a number of file templates for new C# script, tests, and shader files.

Here is a full list of predefined Unity-specific file templates.

Last modified: 15 April 2025