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 (10)

  1. Som thomas skriver, så har Microsoft udgive et værktøj til analyse af din kode – og som sædvanlig er

  2. Is there any future plan to support VB?

  3. Rahul says:

    Great! would be interested to see the feature coming soon.

  4. Pascal says:

    I could see a TFS Check-in policy to ensure code passes Source Analysis before getting to TFS.

  5. Rudi Larno says:

    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:


    Good luck with your baby (the tool I mean 😉


  6. Fabian says:

    We use VB.NET. What are your plans for a VB.net version? Thank you.

  7. Joseph Ferris says:

    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.

  8. Mike says:

    Any plans for providing StyleCop Source Code Analysis for C++?

    Why not?

  9. Clive Chinery says:

    When is version 4.3 being released? A fix for the various bugs in StyleCop a.k.a. Source Code Analysis would be appreciated.

  10. jasonall says:

    Please use the StyleCop Discussion Forum for further comments as it provides a better mechanism for tracking topics and follow-ups.

Skip to main content