eli fessler, Author at C++ Team Blog

Post by this author

Code analysis with clang-tidy in Visual Studio

October 8th, 2019

[Updated on 11/6/2019] - Removed "Setup: Installing Clang tools" section; this is no longer required starting in Visual Studio 2019 version 16.4 Preview 3. Visual Studio 2019 version 16.4 Preview 1 brings a significant improvement to the C++ code analysis experience: native support for clang-tidy, a Clang-based “linter” tool developed ...

New code analysis quick fixes for uninitialized memory (C6001) and use before init (C26494) warnings

May 7th, 2019

In the latest Preview release of Visual Studio 2019 version 16.1, we’ve added two quick fixes to the Code Analysis experience focused around uninitialized variable checks. These quick fixes are available via the Quick Actions (lightbulb) menu on relevant lines, accessed by hovering over the line or squiggle, or by pressing Ctrl+...

In-editor code analysis in Visual Studio 2019 Preview 2

January 24th, 2019

The C++ team has been working to refresh the Code Analysis experience inside Visual Studio. Last year, we blogged about some in-progress features in this area. We’re happy to announce that in Visual Studio 2019 Preview 2, we’ve integrated code analysis directly into the editor, improved upon previously experimental features, and enabled ...

New, experimental code analysis features in Visual Studio 2017 15.8 Preview 3

June 26th, 2018

The Visual C++ team has been working to refresh our code analysis experience inside Visual Studio. We’re aiming to make these tools both more useful and natural to use and hope that they’ll benefit you no matter your workflow, style, or project type. Trying out new features In Visual Studio 2017 version 15.8 Preview 3, available in the ...

Recently completed UserVoice Suggestions for Visual Studio

May 7th, 2018

In our blog posts on the Visual C++ Team Blog, we often encourage readers to submit suggestions on how to improve Visual Studio via UserVoice. We review these suggestions regularly and often work to incorporate them into future releases. This post aims to provide an update, expanding on our previous entry on completed UserVoice suggestions, ...