Community Static Analysis Rules

  •        65

Community Static Analysis Rules is a community based project for creating a set of static analysis rules to extend those provided by the FxCop team.

http://csar.codeplex.com/

Tags
Implementation
License
Platform

   




Related Projects

FinlogiK Statistics Collector for FxCop


The FinlogiK statistics collector tool for FxCop is intended to help development teams to track the progress of an FxCop backlog cleanup effort. It is capable of counting total remaining and TODO rule violations in an FxCop 1.35 project.

FxCop Delta


A custom check-in policy for Visual Studio Team System that runs FxCop rules before performing a check-in. FxCop Delta differs from the normal static analysis policy by running FxCop only on the code that changed since checking out, thus eliminating tens or hundreds of static ...

Lephone FxCop Rules


Lephone FxCop Rules is the custom rules for FxCop. For now it includes 2 rules: function should less than limited lines and file should less than limited lines.

FxCop Integrator


FxCop Integrator allows to integrate stand-alone FxCop and Code Metrics PoewrTool into VS2010. You can analysis your source code on VS2010 Pro.

Fxcop ASP.NET Security Rules


Fxcop ASP.NET security rules This is a set of code analysis rules aiming at analyzing ASP.NET and ASP.NET MVC security against best practices. The rules can be used by Visual Studio 10 Ultimate or FxCop v10 standalone.



CSAR


CSAR, Corpus Server Architecture, a set of libraries and CGI interfaces to facilitate user interaction with corpus management systems, such as CWB.

fxcop-unit - Helper class for unit-testing FxCop-Rules


Helper class for unit-testing FxCop-Rules

NetBuildConfigurator


A re-usable framework and Toolsets to integrate MSbuild,MSTest,Nunit,SVN,VSS,VSTS,NCover,VstsCodeCoverage,Ndepend,Fxcop,StyleCop,CAT.net,IIS deployment tasks,DB tasks from a cool WebInterface.

FreeToDev MSBuild Tasks Suite


Welcome to the FreeToDev MSBuild Tasks Suite. Here you will find a collection of MSBuild tasks dedicated to the .Net 3.5 Framework. The Suite provides over 170 tasks covering the .Net Framework, BizTalk, FxCop, IIS7, SourceSafe, StyleCop, Team Foundation Server, WMI and more....

BizTalkCop


A set of FxCop rules for enforcing coding standards on BizTalk projects. First release includes configurable naming rules based on Scott Colestock's published conventions.

FxFix


Fixes defect identified by static code analysis tools like FxCop and StyleCop.

LINQ to FxCop


LINQ applied to make declarative expression of custom rules in FxCop easier.

Code Quality Extensions


Code Quality Extensions allows advanced code analysis by providing additional Microsoft(R) FxCop and Microsoft(R) StyleCop rules. It's developed in C#.

fxcoptask - FxCop MSBuild task, slightly modified from original by Brad Wilson.


FxCop MSBuild task, slightly modified from original by Brad Wilson.

sqlcop - Like FxCop and StyleCop, but for SQL.


Like FxCop and StyleCop, but for SQL.

RxCop - Static analysis for observable sequences using the FxCop system.


Static analysis for observable sequences using the FxCop system.

PycoFxCop - customize rules of FxCop to adapt Pyco Convention


customize rules of FxCop to adapt Pyco Convention

FxCop4NUnit - FxCop rules for NUnit unit tests


FxCop rules for NUnit unit tests

research - CP vs IP runtimes when using Google-CP Solver on a time scheduling problem


CP vs IP runtimes when using Google-CP Solver on a time scheduling problem

heat-translator - Translate non-heat templates to Heat Orchestration Template.


Heat-Translator is an Openstack project and licensed under Apache 2. It is a command line tool which takes non-Heat templates as an input and produces a Heat Orchestration Template (HOT) which can be deployed by Heat. Currently the development and testing is done with an aim to translate OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) templates to HOT. However, the tool is designed to be easily extended to use with any format other than TOSCA.Heat-Translator project takes a non-Heat template (e.g. TOSCA flat YAML template or template embedded in TOSCA Cloud Service Archive (CSAR) format) as an input, calls an appropriate Parser (e.g. TOSCA Parser) per the type of input template to parse it and create an in-memory graph, maps it to Heat resources and then produces a Heat Orchestration Template (HOT) as an output.