Subscribe: TheScarms - Custom FxCop Rules
http://www.thescarms.com/dotnet/fxcop.xml
Preview: TheScarms - Custom FxCop Rules

TheScarms - Custom FxCop Rules



Create Custom FxCop (Framework Police) Code Analysis Rules



 



Create Custom FxCop Rules - Overview
Create Custom FxCop (Framework Police) Code Analysis Rules - Overview



Custom FxCop Rule - Do not call .NET Garbage Collector
Create Custom FxCop (Framework Police) Code Analysis Rule - Do not call .NET Garbage Collector



Custom FxCop Rule - Do not use GOTO Statements
Create Custom FxCop (Framework Police) Code Analysis Rule - Do not use GOTO Statements



Custom FxCop Rule - Do not use VB6 Conversion Functions
Create Custom FxCop (Framework Police) Code Analysis Rule - Do not use VB6 Conversion Functions



Custom FxCop Rule - Do Use the VB Compatibility Namespace
Create Custom FxCop (Framework Police) Code Analysis Rule - Do Use the VB Compatibility Namespace



Custom FxCop Rule - Do not use MSFlexGrid Interop
Create Custom FxCop (Framework Police) Code Analysis Rule - Do not use MSFlexGrid Interop



Custom FxCop Rule - Remove Empty Methods
Create Custom FxCop (Framework Police) Code Analysis Rule - Remove Empty Methods



Custom FxCop Rule - Verify use of VB's IsNothing or IsDBNull
Create Custom FxCop (Framework Police) Code Analysis Rule - Verify use of VB's IsNothing or IsDBNull



Custom FxCop Rule - Do not use Wildcards in Assembly Version Number
Create Custom FxCop (Framework Police) Code Analysis Rule - Do not use Wildcards in Assembly Version Number



Custom FxCop Rule - Do not store passwords in variables in code
Create Custom FxCop (Framework Police) Code Analysis Rule - Do not store passwords in variables in code