Visual Studio 2015 - What does the Analyzers link mean?

Question

Creating a simple C # Console application in Visual Studio 2015 Preview, we get a pseudo-link called "Analyzers":

What does the Analyzers link above only mean?

The project file has nothing inside, and the properties window does not show anything (completely empty) about this entry (although, unlike the "link properties", the heading says "folder properties", but this does not say much).

I expect this to be connected with Roslin, but I have no idea. I have ReSharper installed, but I do not assume that it has anything to do with it.

Change 6.8.2016

The accepted answer explains the tools provided by the analyzers, but it remains open why the development tool becomes a link (runtime?). This is actually not a run-time reference, unlike other links. So, the answer to this miracle is Hans Passans comment below:

They chose awkward places to add the function of a code analyzer, they simply could not find a better place without a radical overhaul of the explorer and nuget solutions. - Hans Passant May 26 15:15 at 8:59

Answer 1

Live code analyzers are used to add custom error messages and warnings that appear live when you type, along with automatic code fixes to help you clear them. They are available as NuGet packages that you add to your projects in Visual Studio 2015.

This is one of the best and useful key features of Visual Studio 2015, which allows the NuGet package to include custom warnings and errors in the editor in real time when entering code with automatic code fixes that can clear these problems for us.

Packages can even be combined together as a “code-supporting library” that draws on both APIs and domain analyzers to make sure you stay up to date with its use.

We will have focused guidance from the moment we download the NuGet package. And since these analyzers are part of our project, everyone in your team receives the same warnings.

Change 1:

Analyzers have the following rules:

These rules focus on the most important issues in your code, including potential security holes, application crashes, and other important design logic and errors . You must include this rule in any custom rule that you create for your projects.

Answer 2

There are currently many good analysts - Microsoft.AnalyzerPowerPack, Code Cracker, CSharp Essentials, SonarLint, etc.

Each of these analyzers has its own set of rules, so we can decide which analyzer to add based on our requirements. After installing through Nuget, the bulbs and quick actions in VS2015 will select the appropriate set of rules and provide developers with coding assistance on the fly.