Skip to main content

Installation and configuration for FxCop tool

Today I am going to explain about the installation and configuration for fxcop tool.

Description about tool: FxCop is a tool that performs static code analysis of .NET code. It provides hundreds of rules that perform various types of analysis.
  • Design
  • Globalization
  • Interoperability
  • Maintainability
  • Mobility
  • Naming
  • Performance
  • Portability
  • Reliability
  • Security
  • Usage
Below are the steps for Installation and configuration of FxCorp tool:
1. Download FxCop from Microsoft site.
2. Double click on FxCopSetup.exe and install it on your system. (It will get installed on location C:\Program Files (x86)\Microsoft FxCop 1.36)
3. Once installation is done. Run FxCop tool.
Start->All Programs->Microsoft FxCop->Microsoft FxCop 1.36
clip_image002
4. Create a directory of name “FxCop” on “D:” drive.
Unzip “Sharepoint.zip” to this folder (D:\FxCop).This folder contains required dll for the project. You can also copy the required .dll from the {SharePoint Root}/ISAPI folder.
5. After opening FxCop tool.
Create a new project clip_image004
6. Click on “Save Project As” from menu.
clip_image006
7. Write name as “portal” in save as dialog
clip_image008
8. After creating portal add target assemblies to it.
clip_image010
9. Find location of your project dll from visual studio.
Path :- <Local Path>\<Your project Name>\bin\Debug
Note: - Here we are adding these two dynamic link libraries as we have to analyse those with FxCop. Same way we can add any dynamic link library to this for analysis.
Add your required dll that you want to do code analysis say “xyz.dll”
10. Select component which you want to analysis by selecting it in tree view.
Please refer to screen dump below:-
Here we are analysing only “ButtonCounter” class form Webcontrol.dll
clip_image012
11. Select Rules in “FXCop”
First select “Rule tab” then only select highlighted rules from “Naming Rules” section.
Following rules should be selected for this sample
1. Identifiers should be cased correctly.
2. Identifiers should be spelled correctly.
3. Identifiers should not contain underscores.
clip_image014
12. After rules selection. Click “Analyze button from tool bar”
Please refer to screen dump below
clip_image017
13. A popup will appear on the screen where user has to locate SharePoint dynamic link library (DLL). Here select the path of “D:\Fxcop” where we have unzipped all SharePoint assemblies. This popup will might come for three or four times for different SharePoint assemblies.
clip_image019
14. If any issues are found in code analysis then those will get added in right side pane of “FxCop”
clip_image022
15. To see details of issues click on it. Details will get highlighted in below pane.
Here you will get the location of issue.
clip_image025
16. Please go to visual studio fix the issue in given file and rebuild that assembly.
After successful rebuild again go to FxCop and analyse it or press “F5”. Issues which are fixed will get disappeared from issue pane. This way developer has to resolve all issues from his\her code.
Hope you like this article.For the developer this tool is very important and it’s good if you want to deliver good quality of code to reduce maintenance effort or future issues.

Comments

Popular posts from this blog

Create a Web Part Page with a Web Part in Sharepoint 2010

Source code from codeplex In this blog I am going to explain how to create a web part page along with a web part. After using this feature, we just need to activate the feature; the rest will complete automatically. Steps for creating the functionality: Step 1: Create a project with Farm-Based solution: Step 2: Add a new item as webpart: Step 3: Add feature event receiver class, your solution should look like the following: Step 4: Add your logic to the web part: 01 [ToolboxItemAttribute( false )] 02 public class CustomWebPart : WebPart 03 { 04 protected override void CreateChildControls() 05 { 06 LiteralControl lt = new LiteralControl(); 07 lt.Text = "This webpart automatically added with page" ; 08 this .Controls.Add(lt); 09 } 10 } Step 5: You need to provide logic in the feature Reciever class. Find the attached file to see the source code. Step 6: Build, deploy and activate the feature. Step 7: Go to Page library ( S

SharePoint Branding Solution Pack using VS2010

Introduction Today, in this blog I am trying to provide you the Custom Branding solution Pack. This solution pack will save time and effort while developing the custom sharepoint with publishing sites in sharepoint. It works great. So, we all are good to go and use this re-usable solution pack. Description The source code shows how to prepare a structure for Sharepoint Branding solution. This pack contains : Master Page Gallery structure Page Layout Gallery structure Image Gallery Styles Library gallery Event Receiver

How to create Sandbox solution with full trust Proxy

Download Files: CustomSBFullTrust.zip In this article I am explaining the step by step procedure to create a sandbox solution with full trust proxy. Before starting I am assuming you are aware of the sandbox limitations. Full trust solution is providing sandbox solution to work in a full environment. In short this is the way to achieve farm based solution functionality in a Sandbox. Namespace Required: using Microsoft.SharePoint.UserCode; using Microsoft.SharePoint.Security; using System.Security.Permissions; using Microsoft.SharePoint; using Microsoft.SharePoint.Publishing;