Setting Up StyleCop MSBuild Integration

Source Analysis Build Integration

Microsoft Source Analysis for C# — Sat, 24 May 2008 19:29:17 GMT

The following article describes how to integrate Source Analysis into the build, so that the tool will

Microsoft Source Analysis for C#

Sun, 25 May 2008 00:46:06 GMT

"Source Analysis, also known as StyleCop, analyzes C# source code to enforce a set of best practice

Stylecop has been released

I know the answer (it's 42) — Sun, 25 May 2008 00:48:14 GMT

Microsoft released the internal tool StyleCop to public under the fancy yet boring name of Microsoft

Interesting Finds: 2008.05.25

gOODiDEA.NET — Sun, 25 May 2008 05:06:06 GMT

Web Fantastic, Free Calendar and Datepicker Scripts .NET Evaluation Engine - a parser and interpreter

Microsoft Source Analysis for C# 4.2 was published

Juan Pablo Garcia — Sun, 25 May 2008 09:39:15 GMT

Microsoft has published a great tool called Microsoft Source Analysis for C# , also known as StyleCop

Analysis Rules

Wojtek — Sun, 25 May 2008 12:25:44 GMT

Great! On my blog (wojciech.zimirski.net) you can find list of all rules currently embedded in the Microsoft Source Analysis for C#.

Microsoft Source Analysis for C# (aka StyleCop), un camarade pour FxCop

CoqBlog — Sun, 25 May 2008 19:11:08 GMT

Un nouvel outil est disponible pour les développeurs C#. Comme son nom l'indique il s'agit d'un analyseur

TFS Task

FreeToDev — Mon, 26 May 2008 13:24:01 GMT

I've written a task to perform analysis on custom file collections which makes it easy to integrate with TFS builds. http://freetodev.spaces.live.com/blog/cns!EC3C8F2028D842D5!400.entry

NAnt??

Sebastian Jancke — Mon, 26 May 2008 14:01:55 GMT

I like this tool! Are there plans for NAnt tasks? As i use NAnt for hand-written build-files, this would be really nice. If there is no support planned, I would think of building a custom task for NAnt myself - however work should not be done multiple times...

TFS Task

FreeToDev — Mon, 26 May 2008 16:16:23 GMT

I've written a task to scan csutom collections. Handy for TFS builds... http://freetodev.spaces.live.com/blog/cns!EC3C8F2028D842D5!400.entry

re: Setting Up Source Analysis MSBuild Integration

redsolo — Mon, 26 May 2008 18:16:40 GMT

Is it possible to output the result to an XML file similar to FxCop? If not, are you planning to add such feature?

[Note from jasonall - An XML file is automatically produced when running through MSBuild integration]

re: Setting Up Source Analysis MSBuild Integration

redsolo — Mon, 26 May 2008 22:58:54 GMT

Ah, great!

It would also be nice if the XML file could have a <rules> tag that contains all rules that are mentioned in the XML report (Similar to FxCop). Im particular looking for a URL and a longer descrption. Or is there any other way to find out a URL from the RuleId?

【Code Gallery】Microsoft Source Analysis for C#

長沢智治のライフサイクルブログ — Tue, 27 May 2008 05:42:55 GMT

こんにちは。手みじかですが、Microsoft Spurce Analysis for C# v4.2 が MSDN Code Gallery に公開されました。バージョン番号を見ていただければ、わかるとおり、4.2

Microsoft Source Analysis for C#

Maor David — Tue, 27 May 2008 11:08:55 GMT

Microsoft announce the public release of a new developer tool -  Source Analysis for C# . Inside

re: Setting Up Source Analysis MSBuild Integration

Guillaume — Tue, 27 May 2008 12:23:00 GMT

Are you plannig to add a command line tool (as FxCop) to integrate this tool in any other build system?

re: Setting Up Source Analysis MSBuild Integration

Greg — Fri, 30 May 2008 11:23:12 GMT

How do you get ExcludeFromSourceAnalysis to work? I've tried

but that doesn't work (the project won't load).

Cheers.

Integration with MSBuild

David — Thu, 05 Jun 2008 15:56:41 GMT

I tried to integrate SourceAnalysis with MSBuild, that worked well as long as I added

to each projects msbuild file (.proj):

It wrote a "SourceAnalysis.Cache" file.

Now I wanted to add this import line to the proj-file I wrote for the solution. No errors when I run MSBuild, but also no XML-Output. Any idea what can be wrong?

Problems with Integration

David — Thu, 05 Jun 2008 16:29:44 GMT

I tried to integrate SourceAnalysis with MSBuild, that worked well as long as I added

to each projects msbuild file (.proj):

It wrote a "SourceAnalysis.Cache" file. (don't know if that is the right file?!)

Now I wanted to add this import line to the proj-file I wrote for the solution. No errors when I run MSBuild, but also no XML-Output. Any idea what could be wrong?

Cheers

re: Setting Up Source Analysis MSBuild Integration

Graeme Wells — Wed, 11 Jun 2008 17:20:47 GMT

Try :

It seems to work for me

Thanks

Graeme

Breaking the EULA

Martin — Thu, 12 Jun 2008 21:40:46 GMT

When reading the EULA it's clear that you aren't allowed to, quote: "publish the software for others to copy". As I see it putting the binaries into a repository directly violates this.

Can you elaborate on why this is not violating the EULA and does this exception apply to any product containing this limitation in the EULA?

re: Setting Up StyleCop MSBuild Integration

Chaitanya — Thu, 19 Jun 2008 15:35:10 GMT

I want to run this StyleCop using nant script. Can anybody know how to run stylecop on code base using Nant script? Is there any command line version of StyleCop available?

Microsoft Source Analysis for C# + ReSharper = Real-time Source Analysis

Howard van Rooijen's Blog — Tue, 24 Jun 2008 20:03:55 GMT

I've worked on a couple of projects for Microsoft UK - one of the many great aspects of those projects

NAnt support

John K — Mon, 30 Jun 2008 17:04:49 GMT

Great tool! Any support for NAnt anytime soon?

Nant

João Carlos Clementoni — Mon, 14 Jul 2008 20:02:13 GMT

Hi. How we can run this tool with Nant?

Linq to SQL Breaks Rules

Amir Simantov — Tue, 12 Aug 2008 23:54:33 GMT

As if Linq to SQL team members did not use StyleCop?...

A single System.Data.Linq.DataContext derivative class, which is generated automatically when dragging items from Database/Server Explorer, break this rules (the number of breaking the rules are given in parentheses):

1. SA1601: The partial class element must have a documentation header containing either a summary tag or a content tag.

(Once).

2. SA1600: The field/method/constructor must have a documentation header.

(6 times)

3. SA1633: The file has no header, the header Xml is invalid, or the header is not located at the top of the file.

(Once)

4. SA1512: A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'.

5. SA1507: The code must not contain multiple blank lines in a row.

(Once)

6. SA1505: An opening curly bracket must not be followed by a blank line.

(Once)

7. SA1400: The method must have an access modifier.

(Once)

8. SA1201: All methods must be placed after all constructors.

(4 times)

9. SA1101: The call to OnCreated must begin with the 'this.' prefix to indicate that the item is a member of the class.

(4 times)

10. The famous/notorious SA1027: Tabs are not allowed. Use spaces instead.

(41 time) and in words: forty-one.

Mind you, the file has only 60 lines of code :-)

Amir simantov

Dot, Net & Beyond

re: Setting Up StyleCop MSBuild Integration

Bart — Fri, 22 Aug 2008 12:28:47 GMT

Is it possible to integrate it with a Visual C# Express edition 2005?

re: Setting Up StyleCop MSBuild Integration

jasonall — Fri, 22 Aug 2008 13:15:31 GMT

@Bart:

We have not tested running StyleCop in Visual C# Express edition 2005 through MSBuild integration. I think it will _probably_ work, however, if you edit the .csproj file and add the StyleCop import tag as explained in this article.

Yes, Integrates With C# Express Edition

Amir Simantov — Sat, 30 Aug 2008 15:03:43 GMT

I have tested it and it works just fine.

Amir

Import Tags

Martin — Mon, 15 Sep 2008 12:01:39 GMT

Hi @ all!

my question about MSBuild integration is following. Is there a difference between using VS2005 and VS2008?

When i look at the *.csproj-file and would like to edit it, i find following tag:

Might replacing this tag with ...

and adding ...

lead to any troubles in future?

Best regards,

Martin

Introducing StyleCop on Legacy Projects

Microsoft StyleCop — Tue, 11 Nov 2008 15:49:33 GMT

A number of people have asked for tips on rolling out StyleCop on a large, pre-existing codebase. This