EF-specific code inspections

ReSharper provides the following code inspections for code issues specific to Entity Framework projects:

Inspection	Default severity
Database function must not be called in non-database context	Warning
Function is not convertible to SQL and must not be called in the database context	Warning
Possible multiple queries to the database (N+1 problem)	Warning
Possible multiple queries to the database for related entities (N+1 problem)	Suggestion
Possible performance issues caused by unlimited string length	Warning
Query can return incomplete data for related entities	Suggestion
The relationship defined by this property contributes to a dependency loop	Hint
Usage of navigational property can return incomplete data	Warning

If you do not find some or all of these inspections helpful, you can clear the Enable Entity Framework-specific inspections checkbox on the Code Inspection | Entity Framework page of ReSharper options Alt+R, O, or alternatively, you can disable only model-specific or only query-specific inspections on that page.

On that settings page, you can also list FQNs (fully qualified names) of database context classes (classes inherited from DbContext) that will be ignored during code analysis for identifying N+1, incomplete data, and other related issues.

You can click Add above the table to specify FQNs manually, or you can press Alt+Enter in the editor at the corresponding highlighting and choose to ignore the related context class:

ReSharper: Disabling Entity Framework inspections for a DB context class from the 'Alt+Enter' menu

Last modified: 27 November 2024