CustomFxCop

NEW POST: Feedback about the Implementation

Jose_Adan — Fri, 17 Oct 2008 19:04:44 GMT

Hi Amit,

Thaks a lot for this contribution.

Do u know how it can be implemented in Visual Studio Team System 2008 with "Analysis Code"?

I copied the files to "C:\Archivos de programa\Microsoft Visual Studio 9.0\Team Tools\Static Analysis Tools\FxCop\Rules", but I im getting error when I open VSTS :(

NEW POST: Feedback about the Implementation

amitmnagarwal503 — Tue, 26 Aug 2008 11:27:27 GMT

It has been more than a month since i have uploaded the implementation and close to 300 downloads have taken place which is an indicator that people are using the Custom code.

I just wanted to get some feedback, your experience about using it. It could just be a small comment.
Please do the same which will give me an idea of the usability of the Implementation.

Anticipating a reply.

Amit Agarwal

UPDATED WIKI: Home

amitmnagarwal503 — Sun, 27 Jul 2008 08:24:04 GMT

Custom FxCop Implementation

Most of the people are aware of FxCop Code Analysis Tool 1.35 of Microsoft. It provides us with automation of code review process and ensures that our code adhers to Standard Specifications thereby ensuring code delivered is of utmost quality.

The default FxCop Rules provides us with a vast library of Rules prescribed by Microsoft. Here there is no provision of checking variable naming convention and control variable convention in a customized manner which varies from project to project. By Customized manner I mean, there is an accompanying config file where you configure the conventions according to your requirements giving complet Flexibility.

Here I have made an attempt to add new rule sets to check variable naming conventions in a project. This will really help projects to automate their code review process.

Please check out in the downloads section, Release of the Custom Rules Dll.

Regards,

Amit M Agarwal
Mastek Ltd
Mumbai,India

NEW POST: Custom FxCop Released

amitmnagarwal503 — Sun, 27 Jul 2008 08:16:17 GMT

First of all sorry for replying late

This idea evolved when I discovered that the default FxCop was unable to provide the naming convention check to the user in a customized manner.

1) Regarding new custom rules to develop , as of now a bit busy in current projects, but however would be intereseted in as and when there is free time.

2) Yep, I would be more than happy if the Custom FxCop Users come up with their suggestion's/contributions and enhancements in it

Thanks for your interest in my work. Also is it possible for you to share links to more custom fxcop rule implementation you were talking about on the owasp wiki.

Finally have you used the implementation. Can you comment on it. Do you hv a chat id to talk to.

Thanks
Amit Agarwal
Mastek Ltd,Mumbai,India

3)Following is the main feature of my implementation
It is Completely Configurable according to user needs. Each Project has their own naming conventions so they can set in the config file and use it accordingly

NEW POST: Custom FxCop Released

ParanoidMike — Sun, 20 Jul 2008 21:46:54 GMT

amitmnagarwal503 wrote:
HI All I have released the custom rule implementation to .NET community worldwide for the benefit of all.

Feel free to take advantage of it. Also share your experiences while using it and report any bugs if any.

Hi Amit, thanks for sharing the benefit of your hard work with all of us.

I'd like to understand where this project may go in the future - what are your intentions for future development (if any) for this project? I've been amassing links to the various FxCop-custom-rules projects on the OWASP wiki, and it would help if we could provide more details around:

Other custom rules you are planning to implement
Whether you're planning to invite and include contributions from other FxCop custom rules developers
How your project is unique compared with the other projects making available their FxCop custom rules.

This isn't meant to criticize your project - in fact, I'm strongly encouraging it. At the same time, there are enough separate open-source projects for custom rules that it's non-trivial for anyone considering investing time and effort in either (a) reading and enhancing the code or (b) contributing their own custom rules. I'm posting the same request at the other projects as well, to understand their intentions as well.

Thanks!

NEW POST: Custom FxCop Released

amitmnagarwal503 — Sun, 20 Jul 2008 20:31:10 GMT

HI All I have released the custom rule implementation to .NET community worldwide for the benefit of all.

Feel free to take advantage of it. Also share your experiences while uising it and report any bugs if any.

UPDATED RELEASE: Custom FxCop Rules (Jul 20, 2008)

Sun, 20 Jul 2008 13:40:27 GMT

CREATED RELEASE: Custom FxCop Rules (Jul 20, 2008)

Sun, 20 Jul 2008 13:38:03 GMT

UPDATED WIKI: Home

amitmnagarwal503 — Sun, 20 Jul 2008 13:31:41 GMT

Custom FxCop Implementation

Most of the people are aware of FxCop Code Analysis Tool 1.35 of Microsoft. It provides us with automation of code review process and ensures that our code adhers to Standard Specifications thereby ensuring code delivered is of utmost quality.

The default FxCop Rules provides us with a vast library of Rules prescribed by Microsoft. Here there is no provision of checking variable naming convention and control variable convention in a customized manner which varies from project to project.

Here I have made an attempt to add new rule sets to check variable naming conventions in a project. This will really help projects to automate their code review process.

I have attached the User Manual document to help you configure the Custom Rules.

Also check out in the downloads section, Release of the Custom Rules Dll.

UPDATED WIKI: Home

amitmnagarwal503 — Sun, 20 Jul 2008 13:29:36 GMT

Custom FxCop Implementation

Most of the people are aware of FxCop Code Analysis Tool 1.35 of Microsoft. It provides us with automation of code review process and ensures that our code adhers to Standard Specifications thereby ensuring code delivered is of utmost quality.

The default FxCop Rules provides us with a vast library of Rules prescribed by Microsoft. Here there is no provision of checking variable naming convention and control variable convention in a customized manner which varies from project to project.

Here I have made an attempt to add new rule sets to check variable naming conventions in a project. This will really help projects to automate their code review process.

I have attached the User Manual document to help you configure the Custom Rules.

Also check out in the downloads section, Release of the Custom Rules Dll.

UPDATED WIKI: Home

amitmnagarwal503 — Sun, 20 Jul 2008 13:03:58 GMT

Custom FxCop Implementation

Most of the people are aware of FxCop Code Analysis Tool 1.35 of Microsoft. It provides us with automation of code review process and ensures that our code adhers to Standard Specifications thereby ensuring code delivered is of utmost quality.

The default FxCop Rules provides us with a vast library of Rules prescribed by Microsoft. Here there is no provision of checking variable naming convention and control variable convention in a customized manner which varies from project to project.

Here I have made an attempt to add new rule sets to check variable naming conventions in a project. This will really help projects to automate their code review process.