StyleCop analyzes C# source code to enforce a set of style and consistency rules. It can be run from inside of Visual Studio or integrated into an MSBuild project. StyleCop has also been integrated into many third-party development tools.
The goal is to define guidelines to enforce consistent style and formatting and help developers avoid common pitfalls and mistakes.
StyleCop contributes to this maintainability by encouraging consistency of style, which in turn makes it easier for developers to pick up existing code and work with it productively, and by encouraging plenty of documentation for future developers to read thereby improving the long term maintainability of the source.
Historically, different development groups have used drastically different coding styles. Many teams have used inconsistent coding styles within a single product or even a single source file. StyleCop was originally written to provide a simple and efficient way to enforce a common coding style for C# code throughout Microsoft.
Over time, StyleCop evolved to include new rules that go beyond style checks. StyleCop has become a good complement to FxCop (Code Analysis). FxCop analyzes compiled .NET binaries, while StyleCop analyzes the original source code. This allows StyleCop to investigate issues in code that are thrown away by the compiler. StyleCop could also be used to investigate issues in non-compiled languages such as JavaScript or Xml.
StyleCop provides an extensibility mechanism allowing parsers and analyzers for any language to be plugged into the system. Individual developers or teams can write and deploy their own rules, or integrate support for new languages. The StyleCop SDK provides support for writing StyleCop add-ins.



How to enhance debugging in Visual Studio with just one simple step

Piotr Stapp. Stapp Space. 2016-09-12.
During the debugging session, I always had problems with complex structures. Preview most interesting properties were irritating, we need to expand a variable.
In most cases, I tried to override ToString method. But it isn’t always possible.
Default tooltip is useless

[How to enhance debugging in Visual Studio with just one simple step]

Visual Studio “15” Preview 4

John Montgomery. Visual Studio Blog. 2016-08-22.
Today we released Visual Studio “15” Preview 4, introducing many new improvements and bug fixes that bring us one stage closer to the product’s completion.
The highlight of this release is that nearly all of VS is running on the new setup engine, resulting in a smaller, faster and less impactful installation. The smallest install is less than 500 MB on disk (compared to 6GB in the previous release of Visual Studio). There are a couple of “workloads” that aren’t present yet, including .NET Core tooling and Azure tooling, but the rest of the existing VS 2015 feature set is available.

Visual Studio “15” Preview 4

The C# and Visual Basic Code-Focused IDE Experience

Dustin Campbell. Visual Studio Blog. 2014-11-12.
The new C# and Visual Basic code-focused IDE experience in the Visual Studio 2015 Preview is significantly improved over the experience in Visual Studio 2013 and I’m excited to share some highlights with you. We’ll look at a few key areas:
1.Refreshed Core IDE Experiences – your existing coding experience just got better
2.Code Fixes and Refactorings – improve your code with live code analysis and refactorings
3.Inline Rename – increase your productivity with a brand new Rename experience
Many of the new and refreshed features that I describe below come to us by way of the .NET Compiler Platform (formerly codenamed “Roslyn”), our rebuild of the C# and Visual Basic compilers and IDE experiences.

[The C# and Visual Basic Code-Focused IDE Experience]