ReSharper 2016.3 Help

Third-Party Code

ReSharper | Options | Code Editing | Third-Party Code

On this page, you can configure the list of C++, JavaScript, TypeScript, CSS, HTML and JSON files, folders, and file masks to be ignored by ReSharper.

Note that when specifying files and folders, you can oly add items that reside under the solution folder. To specify code outside your solution folder, use file masks.

Masks are prefixed by **\ and are matched against absolute file paths. If you want to match all files inside a folder, \** would also be required at the end of the mask. So, for example, files inside C:\Foo\Bar would be matched by Bar\** or Foo\Bar\** or C:\Foo\Bar\** (although shorter masks might match unwanted folders too).
The easiest way to check if the current file is matched by a mask is to type inside it and make sure that design-time code inspection is disabled in this file.

You can also ignore code in other ways for these and other languages on the the following options pages:

Skipped code Code specified in this section is completely ignored by ReSharper – it will not be indexed at all, which is probably what you want for third-party dependencies. This is useful when you have a file in your project that ReSharper would normally recognise as C++, JavaScript, TypeScript or JSON – perhaps a generated, minified file, or a script that is already gzipped, but you do not want the contents to appear in code completion or navigation and search results.
Library code Code specified in this section is treated as non-user code by ReSharper. The contents are still indexed, and appear in code completion and navigation (for example, you can find symbols in these files with Go to Symbol), but ReSharper will not apply code inspection for this code and will not try to modify this code with quick-fixes and refactorings. This section is useful for including third party code, such as jquery.js, where you do not maintain the code yourself but need in completion suggestions and you can always navigate there to check implementation details.
Last modified: 12 October 2017