Future Plans

Since the release of StyleCop, many people have pointed out that a number of the rules enforced by the tool could be automatically corrected by the tool, without requiring the developer to do the corrections manually.

As you might imagine, this functionality is also highly desired by the developers using StyleCop within Microsoft, and this will be the main focus of the next major release of the tool.

Early stages of development have begun on this effort, but at this time there is no annoucement about a potential release date. Expect this to show up at some point in the future.

Comments

• Anonymous
  May 25, 2008
  Som thomas skriver, så har Microsoft udgive et værktøj til analyse af din kode - og som sædvanlig er

• Anonymous
  May 28, 2008
  Is there any future plan to support VB?

• Anonymous
  May 30, 2008
  Great! would be interested to see the feature coming soon.

• Anonymous
  June 02, 2008
  I could see a TFS Check-in policy to ensure code passes Source Analysis before getting to TFS.

• Anonymous
  July 02, 2008
  Hi Jason, Nice to see that StyleCop finally made it to the public. (We had a discussion about this some years ago, when I was till working for Microsoft) I've actually made a request through connect to see it in the next release of Visual Studio: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=354720 Good luck with your baby (the tool I mean ;-) Rudi

• Anonymous
  July 02, 2008
  We use VB.NET. What are your plans for a VB.net version? Thank you.

• Anonymous
  July 11, 2008
  I second Pascal's idea regarding a check-in policy to enforce this.  I could see this being a great companion to the Code Analysis policy.

• Anonymous
  July 31, 2008
  Any plans for providing StyleCop Source Code Analysis for C++? Why not?

• Anonymous
  August 04, 2008
  The comment has been removed

• Anonymous
  October 13, 2008
  Please use the StyleCop Discussion Forum for further comments as it provides a better mechanism for tracking topics and follow-ups.