StyleCop

Updated Release: 4.7 (Jan 05, 2012)

andyr — Thu, 17 May 2012 13:56:55 GMT

Compatible with the Visual Studio 11 Preview.

Install order should be :

VS10
VS11
R#6.1.1 msi (for VS10)
R#6.1.1 vsix (for VS11)
StyleCop 4.7

This version is now compatible with R# 5.1 (5.1.3000.12), R# 6.0 (6.0.2202.688), R# 6.1 (6.1.37.86) and R# 6.1.1 (6.1.1000.82).

Here are the bug details for fixed in 4.7 and closed in 4.7 issues (over 100 issues fixed since 4.6)

Here are the bug details for all issues since 4.3.3.0 that have been fixed and closed (over 450 fixes).

Release Notes
2 new rules in 4.7.21

SA1214:StaticReadonlyElementsMustAppearBeforeStaticNonReadonlyElements

Validates that all static readonly elements are placed before all static non-readonly elements of the same type.

SA1215:InstanceReadonlyElementsMustAppearBeforeInstanceNonReadonlyElements

Validates that all non-static readonly elements are placed before non-static non-readonly elements of the same type.

Released: 4.7 (Jan 05, 2012)

Thu, 17 May 2012 13:56:55 GMT

Compatible with the Visual Studio 11 Preview.

Install order should be :

VS10
VS11
R#6.1.1 msi (for VS10)
R#6.1.1 vsix (for VS11)
StyleCop 4.7

SA1214:StaticReadonlyElementsMustAppearBeforeStaticNonReadonlyElements

Validates that all static readonly elements are placed before all static non-readonly elements of the same type.

SA1215:InstanceReadonlyElementsMustAppearBeforeInstanceNonReadonlyElements

Validates that all non-static readonly elements are placed before non-static non-readonly elements of the same type.

Updated Release: 4.7 (Jan 05, 2012)

andyr — Thu, 17 May 2012 13:55:48 GMT

Compatible with the Visual Studio 11 Preview.

Install order should be :

VS10
VS11
R#6.1.1 msi (for VS10)
R#6.1.1 vsix (for VS11)
StyleCop 4.7

SA1214:StaticReadonlyElementsMustAppearBeforeStaticNonReadonlyElements

Validates that all static readonly elements are placed before all static non-readonly elements of the same type.

SA1215:InstanceReadonlyElementsMustAppearBeforeInstanceNonReadonlyElements

Validates that all non-static readonly elements are placed before non-static non-readonly elements of the same type.

New Post: Visual Studio 2008 Compatibility

andyr — Thu, 17 May 2012 13:47:55 GMT

Fixed in checkin 07f64ec59887

New Post: Visual Studio 2008 Compatibility

andyr — Thu, 17 May 2012 10:52:47 GMT

Removing support for VS2008 was not my intention. I'm rolling this back now.

Edited Issue: Add method header adds duplicate references to custom exceptions thrown in the method [7259]

andyr — Thu, 17 May 2012 10:19:13 GMT

When I click on StyleCop icon next to a method with no help header, it creates some text using a header template.

This works marvelously with the exception of methods where I throw custom exceptions. If I throw the same custom exception on a number of lines, each throwing of the exception adds a new reference to this exception in the header text.

Would it be possible to add only one reference to each custom exception, pls?

Closed Issue: Crash Visual studio while writing #region [7260]

andyr — Thu, 17 May 2012 08:36:45 GMT

Today i am update to 4.7.22.0. When i try write #region block or cut existing block, VS crashes.

NullReferenceException here:
> StyleCop.ReSharper610.dll!StyleCop.ReSharper610.Core.StyleCopRunnerInt.OnViolationEncountered(object sender, StyleCop.ViolationEventArgs e) + 0x25 bytes

Comments: Duplicate of 7258

New Post: Visual Studio Crashing following recent upgrade to 4.7.22.0

andyr — Thu, 17 May 2012 08:35:53 GMT

New Post: Visual Studio crashed with 4.7.22

shtin — Thu, 17 May 2012 08:23:56 GMT

Just downloaded and installed latest version 4.7.22. After solution is loaded and resharper starts to analyze file, VS crashed. Resharper version is 6.1.37.86 (Public 6.1 AFAIK). For now, I just disabled StyleCop in resharper and it works. But I want them work together.

Previous version was 4.7.17 and it was working fine. Am I alone with this problem?

Commented Issue: Crash Visual studio while writing #region [7260]

andyr — Thu, 17 May 2012 07:56:41 GMT

Created Issue: Crash Visual studio while writing #region [7260]

devi_ous — Thu, 17 May 2012 07:42:16 GMT

New Post: Command Line Options

shuruev — Thu, 17 May 2012 07:30:15 GMT

There is also an article describing how to make such console app by your own:

http://stylecopplus.codeplex.com/wikipage?title=Running%20StyleCop%20from%20Your%20Code

Best regards,
Oleg Shuruev

Edited Issue: Add method header adds duplicate references to custom exceptions thrown in the method [7259]

jiripik — Thu, 17 May 2012 06:29:29 GMT

Created Issue: Add method header adds duplicate references to custom exceptions thrown in the method [7259]

jiripik — Thu, 17 May 2012 06:29:13 GMT

Commented Feature: Feature Request: Create standard rules for the layout of element documentation [6640]

Tim_S — Thu, 17 May 2012 04:53:57 GMT

With the right rules this would dramatically improve the readability of doc comments. My suggestion would be to insist on a CRLF before and after the opening element and closing element of many of the tags. For many of the tags insist on a CRLF before the InnerXml starts also.

The following elements to have their opening element and closing element always on a new line:
code, description, example, exception, include, item, list, listheader, para, param, permission, remarks, returns, seealso, summary, term, typeparam, value.

The following have their innerxml on a new line:
code, example, exception, item, list, listheader, para, param, permission, remarks, returns, summary, typeparam, value
Comments: I agree with Przemyslaw - Two styles are required. /// <summary> /// Sample summary /// </summary> /// <param name="paramOne">Sample param one comments.</param> /// <param name="paramTwo">Sample param two comments.</param> /// <returns>Sample return comments.</returns>

Commented Issue: R# Naming Style for private fields [7073]

andyr — Wed, 16 May 2012 23:23:37 GMT

Please add a setting in the default R# user settings for private static readonly fields to use lower camel case. This will override the R# default setting which uses upper camel case. The setting can be found in ReSharper > Options > Languages > Common > Naming Style. The setting is "Static readonly fields (private)" which should be set to "lowerCamelCase".

Also consider other private field settings. In the UserSettings.xml, these will be:

<PredefinedRule Inspect="False" Prefix="" Suffix="" Style="aaBb" ElementKind="PrivateStaticReadonly" />
<PredefinedRule Inspect="False" Prefix="" Suffix="" Style="AaBb" ElementKind="PrivateConstants" />
<PredefinedRule Inspect="False" Prefix="" Suffix="" Style="aaBb" ElementKind="PrivateInstanceFields" />
<PredefinedRule Inspect="False" Prefix="" Suffix="" Style="aaBb" ElementKind="PrivateStaticFields" />

Comments: From here: http://stylecop.codeplex.com/releases/view/79972#DownloadId=324788

Commented Issue: R# Naming Style for private fields [7073]

andyr — Wed, 16 May 2012 23:22:50 GMT

New Post: Visual Studio 2008 Compatibility

chadb — Wed, 16 May 2012 22:59:37 GMT

I do have 4.0 installed. Everything works fine under Visual Studio 2010 and MSBuild 4.0.

I'm working on a project that targets both 3.5 and 4.0. I don't do full builds until I'm about to release, and primarily work in the 4.0 environment. That's why I didn't discover the issue immediately.

Anyway, it appears as if you can't import 4.0 DLLs into MSBuild 3.5 build scripts.

New Post: Visual Studio 2008 Compatibility

andyr — Wed, 16 May 2012 22:54:08 GMT

I changed the dlls to target framework 4 instead of 3.5.

But if you have 4.0 framework installed it should work fine.

Or so I thought. :-)

Do you have 4.0 installed?

~A.

On 16 May 2012, at 23:24, chadb <notifications@codeplex.com> wrote:

From: chadb
First off, thanks for the hard work on release 4.7.22 so quickly.

I'm not sure which update (but I believe it is somewhere after 4.7.19) broke it, but Visual Studio 2008 is now reporting errors loading StyleCop.dll.

More specifically, MSBuild v3.5 can't load something:
The "StyleCopTask" task could not be loaded from the assembly C:\Program Files (x86)\MSBuild\..\StyleCop 4.7\StyleCop.dll. Could not load file or assembly 'file:///C:\Program Files (x86)\StyleCop 4.7\StyleCop.dll' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. Confirm that the  declaration is correct, and that the assembly and all its dependencies are available.
My question is: is building StyleCop using a newer runtime intentional (i.e., is Visual Studio 2008 support being deprecated)?

New Post: Visual Studio 2008 Compatibility

chadb — Wed, 16 May 2012 22:24:19 GMT

First off, thanks for the hard work on release 4.7.22 so quickly.

I'm not sure which update (but I believe it is somewhere after 4.7.19) broke it, but Visual Studio 2008 is now reporting errors loading StyleCop.dll.

More specifically, MSBuild v3.5 can't load something:

The "StyleCopTask" task could not be loaded from the assembly C:\Program Files (x86)\MSBuild\..\StyleCop 4.7\StyleCop.dll. Could not load file or assembly 'file:///C:\Program Files (x86)\StyleCop 4.7\StyleCop.dll' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. Confirm that the  declaration is correct, and that the assembly and all its dependencies are available.

My question is: is building StyleCop using a newer runtime intentional (i.e., is Visual Studio 2008 support being deprecated)?