Annotations in Source Code
The easiest way to benefit from ReSharper's code annotations is to add the annotation attributes to symbols of your source code and make ReSharper analyze your solution with greater accuracy and insight.
By default, all annotation attribute classes are marked with
[Conditional("JETBRAINS_ANNOTATIONS")] attribute so the compiler will ignore the attribute usages in your code, which means that no binary reference to the 'JetBrains.Annotations.dll' assembly will be produced. However, you can define 'JETBRAINS_ANNOTATIONS' conditional compilation symbol in your projects to preserve the attributes in the metadata.
Enable code annotations support in your project
To make use of ReSharper code annotation attributes in your project, you should reference them in one of the following ways:
The recommended way is to install the NuGet package with the
Actually, you do not even need to go to the NuGet website to get the package. Just add the
using JetBrains.Annotations;directive, and use the corresponding Alt+Enter action to automatically fetch the package.
You can add a project reference to the JetBrains.Annotations.dll, which you can find in the ReSharper installation directory.
You can also embed attribute declarations anywhere in your project, using the default
JetBrains.Annotationsnamespace, or any other namespace.
If the JetBrains.Annotations.dll is referenced or attribute declarations are embedded in any of the projects within your solution, you can type the desired annotation attribute and press Alt+Enter to invoke the quick-fix that will reference this module in the current project and add the missing namespace import directive:
Alternatively, you can press Control+Alt+Space twice to invoke the double import completion, which will find the attribute, import the namespace, and add the reference.
Embed declarations of code annotations in your source code
You can get a copy of the code-annotations declarations on the Alt+R O). Optionally, when copying you can choose to make the declarations internal and/or add the
[Conditional("JETBRAINS_ANNOTATIONS")] attribute to the declarations.
The default implementation of the annotation attributes are declared in the
JetBrains.Annotations namespace, but this namespace is not required for the annotations to work. You can put the declarations anywhere in your solution — ReSharper will detect them automatically. However, if the declarations are in a different namespace you should explicitly specify the namespace with annotation attributes as described below.
There also may be cases when your solution contains several implementations of the annotation attributes, for example, you have classes with the same names as ReSharper annotations classes (
NotNullAttribute, and so on) or you are using a third-party assembly that contains ReSharper annotation classes. In such cases, you can choose namespaces where ReSharper should look for the proper set of the annotations-attributes classes.
Change sources of code annotation attributes
Select Alt+R O, then choose on the left.from the main menu or press
All namespaces (from both source code and referenced assemblies) other than
JetBrains.Annotationswith the annotation classes (ReSharper will only look for
NotNullAttributedeclarations) are shown in the Namespaces with code annotation attributes list. Check the entry that contains the desired implementation.
If there are several namespaces in the list, select the one that should be used by the ReSharper code analysis engine it in the Default annotation namespace list.
Click Save to apply the modifications and let ReSharper choose where to save them, or save the modifications to a specific settings layer using the Save To list. For more information, see Manage and Share ReSharper Settings.
Use Context Actions to add annotation attributes
As soon as ReSharper is aware of annotation classes location, you can use context actions to add the most popular annotation attributes:
To add these annotations, press Alt+Enter on the symbol you want to annotate, and ReSharper will suggest an attribute depending on the context: