Skip to main content

FxCop - The .Net Assembly COP


FxCop (Framework Police) is a free code analysis tool provided by Microsoft basically intended for class library developers. It is a must have tool for new developers who want help in getting familiarized with  Microsoft Design Guidelines. FxCop helps to write robust code and easily maintain code by telling you about the possible design, localization, performance and security improvements. It can prevent flaws in the code and helps the programmer to follow best practices.

FxCop is fully integrated in the Visual Studio and is distributed as both a fully featured application that has a graphical user interface (FxCop.exe) for interactive work, and a command-line tool (FxCopCmd.exe) suited for use as part of automated build processes or integrated with Microsoft Visual Studio® .NET as an external tool. It analyses Binary Common Intermediate Language (CIL) instead of the source code, it is not language specific tool and can be used for analysing a dll written in any programming language.

FxCop reads the metadata (data about data) contained in the .Net Assembly and checks it for compliance against built in custom rules and recommended coding standard and practices.

FxCop not only provides 200+ built in rules broadly classified into the following categories:
  1. Design Rules
  2. Globalization Rules
  3. Naming Rules
  4. Portability Rules
  5. Interoperability Rules
  6. performance Rule
  7. Security Rules
  8. Usage Rules
but also gives you the option of adding custom rules and new keywords to FxCop dictionary.

To use FxCop: download it from www.microsoft.com/downloads. Start FXCop Application. Add a project by clicking on File - New Project. Add target dlls by clicking on Projects - Add Targets. Click Analyze...
Once FxCop has analyzed the assemblies, it reports any rule violations and produces well-formatted XML test reports.


One may think "Do we fix all warnings? " Well, you must validate all the warning, and fix only ones that are appropriate for the  project. I don't mean that FxCop gives you warnings that are not needed to be fixed. But you can skip few depending on your requirements. eg: An application that will only be used on one machine, can ignore portability related warnings

For more information on FxCop visit http://msdn.microsoft.com/en-us/library/bb429473(v=vs.80).aspx

Labels:

Comments

Post a Comment

Popular posts from this blog

Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098)

While accessing the active directory (AD) and authorization manager (AZMAN) , If you get “   Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098)  “ message check the    account that is being used to get the LDAP query from AD .  ERROR DETAILS Exception Details:  System.Runtime.InteropServices.COMException: Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098) Source Error: Line 154:    'Session("FullName") = System.Security.Principal.WindowsIdentity.GetCurrent.Name.ToString() Line 155: Line 156:    If Not User.IsInRole("Role1") Then Line 157:          Response.Redirect("./Login.aspx") Line 158:    End If  Stack Trace : .... SOLVE IT Steps to do check the app pool rights: Click on the website name that you are having problem with in IIS  In the right panel you will se...
Post a Comment
Read more

JavaScript Interview Questions

This is a compilations of all the interview questions related to Javascript that i have encountered.  Q: Difference between window.onload and onDocumentReady? A: The onload event does not fire until every last piece of the page is loaded, this includes css and images, which means there’s a huge delay before any code is executed. That isnt what we want. We just want to wait until the DOM is loaded and is able to be manipulated. onDocumentReady allows the programmer to do that. Q:  What is the difference between == and === ? A: The == checks for value equality, but === checks for both type and value. Few examples: "1" == 1; // value evaluation only, yields true "1" === 1; // value and type evaluation, yields false "1" == true; // "1" as boolean is true, value evaluation only, yields true "1" === false; // value and type evaluation, yields false Q: What does “1″+2+5 evaluate to? What about 5 + 2 +...
1 comment
Read more

Do's and Don't SQL

Do's: Writing comments whenever something is not very obvious, as it won’t impact the performance.  (--) for single line  (/*…*/) to mark a section Use proper indentation Use Upper Case for all SQL keywords. SELECT, UPDATE, INSERT, WHERE, INNER JOIN, AND, OR, LIKE. Use BEGIN... END block for multiple statements in conditional code  Use Declare and Set in beginning of Stored procedure Create objects in same database where its relevant table exists otherwise it will reduce network performance. Use PRIMARY key in WHERE condition of UPDATE or DELETE statements as this will avoid error possibilities. If User table references Employee table than the column name used in reference should be UserID where User is table name and ID primary column of User table and UserID is reference column of Employee table. Use select column name instead of select * Use CTE (Common Table Expression); its scope is limited to the next statement in SQL query, instead of...
Post a Comment
Read more