All Versions
10
Latest Version
Avg Release Cycle
60 days
Latest Release
1771 days ago

Changelog History

  • v2016.1.0

    May 02, 2016

    ๐Ÿš€ This is a release of the ReSharper plugin for StyleCop.

    ๐Ÿ’… Please install from the Extension Manager (ReSharper โ†’ Extension Manager), searching for "StyleCop by JetBrains". It does not require StyleCop for Visual Studio to be installed.

    ๐Ÿš€ This release is based on StyleCop 4.7.49. It does not (yet) contain any of the changes made to StyleCop core in 4.7.53 on the (recently reactivated) CodePlex site. I hope we can merge the two developments in the very near future.

    ๐Ÿš€ In this release:

    • ๐Ÿ‘Œ Support for ReSharper 2016.1
    • ๐Ÿ›  Fix to allow filtering by StyleCop issues in code inspections window (#37)
    • ๐Ÿ›  Fix error messages in installer (#32)
    • ๐Ÿ›  Fix to stop code cleanup opening unedited files (#27)
    • ๐Ÿ›  Fix to more reliably check if StyleCopAnalyzers is installed (#20)

    ๐Ÿ”‹ Features

    • ๐Ÿ’… No longer requires StyleCop for Visual Studio to be installed
    • Provides ReSharper 10 compatible settings, including a reset button
    • ๐Ÿ›  Fixes memory leaks and provides better performance throttling
    • ๐Ÿ‘Œ Support for StyleCop addins (e.g. StyleCop+)
    • ๐Ÿ‘ High DPI support in options page
    • Simplified Code Cleanup options

    ๐Ÿ‘ Visual Studio 2015 support

    Please Note: The 4.7.49 StyleCop analyser uses a custom C# parser, rather than ReSharper's code model (hence the requirement for performance throttling). As such, it doesn't understand C# 6 features, and has no C# 6 specific rules.

    ๐Ÿ’… In the near future, I hope to merge the changes in this fork back into the main StyleCop CodePlex repo, at which point, this plugin can start using the 4.7.53 parser, which includes C# 6 support.

    ๐Ÿ’… If you are using Visual Studio 2015, and C# 6, it is recommended that you use the DotNetAnalyzers/StyleCopAnalyzers project, which implements nearly all StyleCop rules as a set Roslyn code analysers. This plugin will notice that StyleCopAnalyzers is referenced in a project, and automatically disable the ReSharper StyleCop rules.

  • v5.0.0-beta01

    December 10, 2016
  • v4.8.0

    November 23, 2015

    ๐Ÿš€ This is a release of the ReSharper plugin for StyleCop.

    ๐Ÿ’… Please install from the Extension Manager (ReSharper โ†’ Extension Manager), searching for "StyleCop by JetBrains". It does not require StyleCop for Visual Studio to be installed.

    ๐Ÿš€ This release is based on the same StyleCop parser and rules as the latest release (4.7.49) - there have been no changes to StyleCop itself, only the ReSharper plugin.

    ๐Ÿš€ In this release:

    • ๐Ÿ‘Œ Support for ReSharper 10

    ๐Ÿš€ This release also includes all of the fixes included in 4.7.1 for ReSharper 9.2.

    ๐Ÿ”‹ Features

    • ๐Ÿ’… No longer requires StyleCop for Visual Studio to be installed
    • Provides ReSharper 10 compatible settings, including a reset button
    • ๐Ÿ›  Fixes memory leaks and provides better performance throttling
    • ๐Ÿ‘Œ Support for StyleCop addins (e.g. StyleCop+)
    • ๐Ÿ‘ High DPI support in options page
    • Simplified Code Cleanup options

    ๐Ÿ’… Why are there two versions of StyleCop in the ReSharper Extension Manager?

    ๐Ÿ’… Unfortunately, there are two versions of StyleCop in the ReSharper Extension Manager.

    ๐ŸŽ This version, listed in the Extension Manager as "StyleCop by JetBrains" is maintained by me (@citizenmatt) on behalf of JetBrains. It contains a number of important fixes over the original codebase, notably memory leaks and improved performance throttling. It also no longer needs StyleCop to be installed in Visual Studio.

    ๐Ÿš€ The other version, "ReSharper.StyleCop" is maintained by a member of the community, and appears to be a simple recompile of the original codebase from CodePlex. Development stalled after the ReSharper 9.1 release, but restarted after the release of this "StyleCop by JetBrains" version.

    ๐ŸŽ I would very much like to combine these two versions into a single version, containing these important performances fixes, and I would love it to be maintained by the community. Unfortunately, the author of the other version still isn't responding to emails, and hasn't published the source for their version.

    ๐Ÿ’… Until that can happen, JetBrains recommends using this "StyleCop by JetBrains" version.

    ๐Ÿ‘ Visual Studio 2015 support

    Please Note: The StyleCop analyser uses a custom C# parser, rather than ReSharper's code model (hence the requirement for performance throttling). As such, it doesn't understand C# 6 features, and has no C# 6 specific rules. If you are using Visual Studio 2015, and C# 6, it is recommended that you use the DotNetAnalyzers/StyleCopAnalyzers project, which implements nearly all StyleCop rules as a set Roslyn code analysers. You can use this extension in conjunction with the analysers, by disabling the "run analysis" setting in the options page.

  • v4.7.55.0

    November 11, 2016
  • v4.7.54.0

    May 13, 2016
  • v4.7.53.0

    April 30, 2016
  • v4.7.52.0

    April 21, 2016
  • v4.7.51.0

    March 14, 2016
  • v4.7.50.0

    February 04, 2016
  • v4.7.1

    November 19, 2015

    ๐Ÿš€ This is a release of the ReSharper plugin for StyleCop.

    ๐Ÿ’… Please install from the Extension Manager (ReSharper โ†’ Extension Manager), searching for "StyleCop by JetBrains". It does not require StyleCop for Visual Studio to be installed.

    ๐Ÿš€ This release is based on the same StyleCop parser and rules as the latest release (4.7.49) - there have been no changes to StyleCop itself, only the ReSharper plugin.

    ๐Ÿš€ In this release:

    • ๐Ÿ‘Œ Supports loading custom StyleCop addins (such as StyleCop+). Specify the path to load in the options page. (#18)
    • ๐Ÿ’… Automatically disable analysis if the DotNetAnalyzers/StyleCopAnalyzers package is referenced in Visual Studio 2015 (#18)
    • ๐Ÿ’… Code Cleanup would not use settings when adjusting file header (#14)
    • ๐Ÿ’… Code Cleanup has a new setting to not create XML doc stubs, as this is something that is better done by a developer (#15)
    • ๐Ÿ’… StyleCop issues now grouped under "StyleCop" in Inspection Results (#16)
    • ๐Ÿ›  Fix duplication of constructor summary text in XML docs when running Code Cleanup (#17)

    ๐Ÿš€ Release notes for 4.7.0

    ๐Ÿ’… Why are there two versions of StyleCop in the ReSharper Extension Manager?

    ๐Ÿ’… Unfortunately, there are two versions of StyleCop in the ReSharper Extension Manager.

    ๐ŸŽ This version, listed in the Extension Manager as "StyleCop by JetBrains" is maintained by me (@citizenmatt) on behalf of JetBrains. It contains a number of important fixes over the original codebase, notably memory leaks and performance work. It also no longer needs StyleCop to be installed in Visual Studio.

    ๐Ÿš€ The other version, "ReSharper.StyleCop" is maintained by a member of the community, and appears to be a simple recompile of the original codebase from CodePlex. Development stalled after the ReSharper 9.1 release, but restarted after the release of this "StyleCop by JetBrains" version.

    ๐ŸŽ I would very much like to combine these two versions into a single version, containing these important performances fixes, and I would love it to be maintained by the community. Unfortunately, the author of the other version still isn't responding to emails, and hasn't published the source for their version.

    ๐Ÿ’… Until that can happen, JetBrains recommends using this "StyleCop by JetBrains" version.

    ๐Ÿ‘ Visual Studio 2015 support

    Please Note: The StyleCop analyser uses a custom C# parser, rather than ReSharper's code model (hence the requirement for performance throttling). As such, it doesn't understand C# 6 features, and has no C# 6 specific rules. If you are using Visual Studio 2015, and C# 6, it is recommended that you use the DotNetAnalyzers/StyleCopAnalyzers project, which implements nearly all StyleCop rules as a set Roslyn code analysers. You can use this extension in conjunction with the analysers, by disabling the "run analysis" setting in the options page.