Code style rule preferences are saved with user profile settings and persisted across Visual Studio sessions on the machine for the same Visual Studio install. This means that any project opened in Visual Studio will have the same code style enforcement. However, the same sources opened on a different Visual Studio installation or a different machine with a different user profile will not have the same code style enforcement. To enable same code style enforcement for a repo across all users, users need to persist the code style settings into an .editorconfig file and check it into the repo along with the sources. Refer to, Using .editorconfig file for per-folder configuration for code style rules, recipe in this chapter for further details.
- Preface
- Writing Diagnostic Analyzers
- Introduction
- Creating, debugging, and executing an analyzer project in Visual Studio
- Creating a symbol analyzer to report issues about symbol declarations
- Creating a syntax node analyzer to report issues about language syntax
- Creating a syntax tree analyzer to analyze the source file and report syntax issues
- Creating a method body analyzer to analyze whole method and report issues
- Creating a compilation analyzer to analyze whole compilation and report issues
- Writing unit tests for an analyzer project
- Publishing NuGet package and VSIX for an analyzer project
- Consuming Diagnostic Analyzers in .NET Projects
- Writing IDE Code Fixes, Refactorings, and Intellisense Completion Providers
- Introduction
- Creating, debugging, and executing a CodeFixProvider to fix a compiler warning
- Applying batch code fixes (FixAll) across different scopes: document, project, and solution
- Creating a custom FixAllProvider to fix all occurrences of an issue across a scope
- Creating a CodeRefactoringProvider to refactor source code to recommend using C# 7.0 tuples
- Creating a CompletionProvider to provide additional intellisense items while editing code.
- Writing unit tests for a CodeFixProvider
- Improving Code Maintenance of C# Code Base
- Catch Security Vulnerabilities and Performance Issues in C# Code
- Introduction
- Identifying configuration-related security vulnerabilities in web applications
- Identifying cross-site scripting vulnerabilities in view markup files (.cshtml, .aspx files) in web applications
- Identifying insecure method calls that can lead to SQL and LDAP injection attacks
- Identifying weak password protection and management in web applications
- Identifying weak validation of data from external components to prevent attacks such as cross-site request forgery and path tampering
- Identifying performance improvements to source code using FxCop analyzers
- Live Unit Testing in Visual Studio Enterprise
- Introduction
- Running live unit tests in Visual Studio for unit test projects based on NUnit, XUnit, and MSTest frameworks
- Viewing and navigating live unit test results
- Understanding incremental live unit test execution with code changes
- Understanding Start/Stop/Pause/Continue/Restart functionality for fine grain control of LUT
- Including and excluding subset of tests for live execution
- Configuring different options for live unit testing using the Tools Options dialog
- C# Interactive and Scripting
- Introduction
- Writing a simple C# script and evaluating it within the Visual Studio interactive window
- Using script directives and REPL commands in the C# interactive window
- Using keyboard shortcuts for evaluating and navigating through script sessions in the C# interactive window
- Initializing the C# interactive session from the existing C# project
- Executing the C# script on a Visual Studio developer command prompt using csi.exe
- Using the Roslyn scripting API to execute C# code snippets
- Contribute Simple Functionality to Roslyn C# Compiler Open Source Code
- Introduction
- Setting up Roslyn enlistment
- Implementing a new syntax error in the C# compiler code base
- Implementing a new semantic error in the C# compiler code base
- Writing unit tests for a new error in the C# compiler code base
- Using Roslyn Syntax Visualizer to view Roslyn syntax tokens and nodes for a source file
- Sending a Roslyn pull request to contribute to next version of C# compiler and VS IDE
- Design and Implement a New C# Language Feature
- Introduction
- Designing syntax and grammar for a new C# language feature
- Implementing parser support for a new C# language feature
- Implementing binding/semantic analysis support for a new C# language feature
- Implementing lowering/code generation support for a new C# language feature
- Writing unit tests for C# parsing, binding, and codegen phases
- Command-Line Tools Based on Roslyn API
- Introduction
- Writing an application based on the Compiler Syntax API to parse and transform source files
- Writing an application based on the Compiler Semantic API to display diagnostics and overload resolution results
- Writing an application based on the Compiler Analyzer API to execute diagnostic analyzers and display analyzer diagnostics
- Writing an application based on the Workspaces API to format and simplify all source files in the solution
- Writing an application based on the Workspaces API to edit projects in a solution and display project properties
There is more...
Consider exploring the Naming rules in the Tools | Options... dialog under Text Editor | C# | Code Style | Naming. These rules allow users to enforce guidelines on how each different symbol kind should be named. For example, interface names should start with capital letter "I", type name should be Pascal cased, and so on.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.