StyleCop

New Post: StyleCop and R#

andyr — Thu, 23 Feb 2012 00:20:12 GMT

#1 it doesn't. It assumes the defaults as that's the most common scenario. If you turn many rules off ignore the message.

2. It updates the settings in r#

3. It's not using any StyleCop.settings files.

On 22 Feb 2012, at 23:29, "spiderM9" <notifications@codeplex.com> wrote:

From: spiderM9

When using the StyleCop/ReSharper integration (6.1.1)...

1. Where does StyleCop look for a .StyleCop file to compare to the R# settings?

2. When you update the settings so they match, is a file rewritten?

After attempting to synchronize the settings, I can't ever find a modified .StyleCop file. It seems odd that this option is available even when no solution is open. In that case, is it using the default Settings.StyleCop from the Program Files installation directory?

Even with the newest StyleCop and Resharper (4.7.11.0 and 6.1.1000.82) every time I go back to the options the "Reset C# Code Style Options" button is enabled. I just don't understand how this feature is supposed to work.

New Post: StyleCop and R#

spiderM9 — Wed, 22 Feb 2012 23:29:49 GMT

When using the StyleCop/ReSharper integration (6.1.1)...

1. Where does StyleCop look for a .StyleCop file to compare to the R# settings?

2. When you update the settings so they match, is a file rewritten?

After attempting to synchronize the settings, I can't ever find a modified .StyleCop file. It seems odd that this option is available even when no solution is open. In that case, is it using the default Settings.StyleCop from the Program Files installation directory?

Even with the newest StyleCop and Resharper (4.7.11.0 and 6.1.1000.82) every time I go back to the options the "Reset C# Code Style Options" button is enabled. I just don't understand how this feature is supposed to work.

Commented Issue: ReSharper - Reset C# Code Style Options is (still) broken [7164]

andyr — Wed, 22 Feb 2012 21:15:37 GMT

ReSharper 6.1.1 build 6.1.38.184
StyleCop 4.7 build 4.7.6.0

Multiple layers, only one is checked. Right click on the layer in use, select "Edit..." then navigate to the "Tools | StyleCop" page (see image #1 in the attachment)

When I click the "Reset C# Code Style Options" the entire Tools/StyleCop page (the right hand side of the R# Options dialog) immediately goes blank. All that remains is the "StyleCop" grey-bar header, nothing else is visible (see image #2 in the attachment). The "ReSharper - Settings Layers" dialog comes to the front.

Pressing the R# Options dialog "Save" button does not appear to save anything.
Pressing the R# Options dialog "Cancel" button does not appear to do anything either.

From this point, if I now close the Options dialog with the title bar 'x' and export the Settings Layer in use, there are still no changes presented.

If I once again open the R# Options dialog (right click on layer and choose Edit), the StyleCop page is once again available, and still indicates that my R# and StyleCop settings are incompatible.

I can't find any way to change the R# settings to match StyleCop. Worse, I can't figure out which settings are different, so I can't modify the settings myself to get rid of the warning.

At the very least, is there somewhere I can look to see which StyleCop settings are paired with which R# settings for this comparison?

Comments: So I'm failing to repro this using the exact steps above with 6.1.1 and 4.7.11. Can you check the steps are still an issue with the new 6.1.1 build please?

Updated Wiki: Home

andyr — Tue, 21 Feb 2012 22:09:33 GMT

StyleCop Governance

Microsoft has turned over governance and coordination of the StyleCop project to the community. The new Coordinator of this project is responsible for managing contributions. Microsoft is not granting any IP rights to code or other material contributed to this project by third parties. The IP rights to each particular contribution are granted to you by the respective contributor under the Ms-PL license.

Project Description

StyleCop analyzes C# source code to enforce a set of style and consistency rules. It can be run from inside of Visual Studio or integrated into an MSBuild project. StyleCop has also been integrated into many third-party development tools.

4.7 is compatible with JetBrains 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).

This release includes the StyleCop ReSharper plugin (compatible with ReSharper 5.1, 6.0, 6.1 and 6.1.1) and will automatically uninstall previous versions of StyleCop. It also includes syntax support for the Async CTP and the first few of StyleCop compliant Visual Studio default templates are now included too.

Core Principles

StyleCop provides value by enforcing a common set of style rules for C# code. StyleCop will continue to ship with a single, consistent set of rules, with minimal rule configuration allowed. Developers can implement their own rules if they so choose.

StyleCop ships with the ability to seamlessly integrate with Visual Studio, MSBuild, TFS, etc. Developers are free to implement custom code to integrate StyleCop into other development and tooling environments, as described in the SDK documentation.

Updated Wiki: Home

andyr — Tue, 21 Feb 2012 22:08:34 GMT

StyleCop Governance

Microsoft has turned over governance and coordination of the StyleCop project to the community. The new Coordinator of this project is responsible for managing contributions. Microsoft is not granting any IP rights to code or other material contributed to this project by third parties. The IP rights to each particular contribution are granted to you by the respective contributor under the Ms-PL license.

Project Description

StyleCop analyzes C# source code to enforce a set of style and consistency rules. It can be run from inside of Visual Studio or integrated into an MSBuild project. StyleCop has also been integrated into many third-party development tools.

4.7 - compatible with JetBrains 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).

This release includes the StyleCop ReSharper plugin (compatible with ReSharper 5.1, 6.0, 6.1 and 6.1.1) and will automatically uninstall previous versions of StyleCop. It also includes syntax support for the Async CTP and the first few of StyleCop compliant Visual Studio default templates are now included too.

Core Principles

StyleCop provides value by enforcing a common set of style rules for C# code. StyleCop will continue to ship with a single, consistent set of rules, with minimal rule configuration allowed. Developers can implement their own rules if they so choose.

StyleCop ships with the ability to seamlessly integrate with Visual Studio, MSBuild, TFS, etc. Developers are free to implement custom code to integrate StyleCop into other development and tooling environments, as described in the SDK documentation.

Updated Release: 4.7 (Jan 05, 2012)

andyr — Tue, 21 Feb 2012 22:07:08 GMT

This is now 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.9.0 (or later)

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 20 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 350 fixes).

Release Notes
4.7.9.0 - StyleCop Error reports now start to show the line and column of the issue and highlight accordingly for some issues. More to follow.

Released: 4.7 (Jan 05, 2012)

Tue, 21 Feb 2012 22:07:08 GMT

This is now 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.9.0 (or later)

Reviewed: 4.7 (Feb 21, 2012)

ajthomas — Tue, 21 Feb 2012 21:14:53 GMT

Rated 4 Stars (out of 5) - Since 6.1.1 is officially out, it'd be great to have a corresponding release of 4.7 to work with it without the installer warning.

New Comment on "Using File Lists"

witchdr — Mon, 20 Feb 2012 22:08:27 GMT

This doesn't appear to be working in 4.7.4

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

Przemyslaw — Mon, 20 Feb 2012 13:47:52 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: It would be better to go the route other rules go - allow either expand whole tag into multiple lines (opening tag on first line, then inner xml on own line(s) and closing tag on own last line) or keep whole tag in single line

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

Przemyslaw — Mon, 20 Feb 2012 13:44:40 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 would argue that innerxml of param, typeparam and returns should be expanded into own line. When VS generates empty xml doc, these tags are collapsed to single line. Many devs type inner text only - they don't add CRLF. And not everyone uses r# to do this for them.

New Post: StyleCop for Resharper 6.1.1000.82

andyr — Mon, 20 Feb 2012 09:51:42 GMT

4.7.10 will install but warn you that it may not work.

So far several people have reported it works fine.

This week the next build 4.7.11 will be built and auto-tested with the RTM of 6.1.1

On 20 Feb 2012, at 09:42, "msmolka" <notifications@codeplex.com> wrote:

From: msmolka

Is latest stylecop compatibile with 6.1.1 (6.1.1000.82)?

New Post: StyleCop for Resharper 6.1.1000.82

msmolka — Mon, 20 Feb 2012 09:42:21 GMT

Is latest stylecop compatibile with 6.1.1 (6.1.1000.82)?

Commented Issue: StyleCop 4.7.10.0 is not working in VS2008 with R#6.1.37.86 [7193]

alexeysafronov — Fri, 17 Feb 2012 15:56:37 GMT

Hi,

I have VS 2008 and VS 2010 and installed R# 6.1.37.86 and StyleCop 4.7.10.0. In VS 2010 everything works fine. In VS 2008, however, I can see that the StyleCop plugin is loaded by R#, however I do not see any StyleCop options under "Inspection Severity" tab, so effectively I don't get any StyleCop issues. Weird thing is that Code Cleanup contains StyleCop settings and appears to work properly. Anothor thing is that when I right-click on C# project, I don't see a menu option to change StyleCop settings. I tried repairing and reinstalling the StyleCop but with no luck. Can you help?

Regards,

Alexey

Comments: Hi, I have just installed VS2008 and VS2010 on a brand new laptop (clean install), then R#6.1 and StyleCop 4.7.10, and I have got the same issue in VS2008 ("Inspection Severity" tab settings are missing). There is a new version of R# 6.10 available by the way.

Edited Issue: SA0001: An exception occurred while parsing the file: System.NullReferenceException, Object reference not set to an instance of an object. [7194]

andyr — Fri, 17 Feb 2012 07:53:56 GMT

During file processing next error took place (StyleCop 4.7.10.0):
[Any CPU/Release] (1,1): error : SA0001: An exception occurred while parsing the file: System.NullReferenceException, Object reference not set to an instance of an object.

The code that cause exception:

var originalCalcs = originalPeriodInvoices
.Select(i => -[decimal]);

Actual problem is on minus sign on lambda expression.

Next code can be handled properly:

var originalCalcs = originalPeriodInvoices
.Select(i => [decimal] * -1);

Created Issue: SA0001: An exception occurred while parsing the file: System.NullReferenceException, Object reference not set to an instance of an object. [7194]

didenkoroman — Fri, 17 Feb 2012 07:24:01 GMT

New Post: Nuget package for build integration

chripede — Fri, 17 Feb 2012 07:12:35 GMT

Please include the target file in the nuget package.

Edited Issue: StyleCop 4.7.10.0 is not working in VS2008 with R#6.1.37.86 [7193]

andyr — Thu, 16 Feb 2012 16:28:12 GMT

Commented Issue: StyleCop 4.7.10.0 is not working in VS2008 with R#6.1.37.86 [7193]

andyr — Thu, 16 Feb 2012 16:27:35 GMT

Commented Issue: StyleCop 4.7.10.0 is not working in VS2008 with R#6.1.37.86 [7193]

alexeysafronov — Thu, 16 Feb 2012 15:46:20 GMT

Hi,

I have VS 2008 and VS 2010 and installed R# 6.1.37.86 and StyleCop 4.7.10.0. In VS 2010 everything works fine. In VS 2008, however, I can see that the StyleCop plugin is loaded by R#, however I do not see any StyleCop options under "Inspection Severity" tab, so effectively I don't get any StyleCop issues. Weird thing is that Code Cleanup contains StyleCop settings and appears to work properly. Anothor thing is that when I right-click on C# project, I don't see a menu option to change StyleCop settings. I tried repairing and reinstalling the StyleCop but with no luck. Can you help?

Regards,

Alexey

Comments: I found and deleted few old DLLs in teh Roaming folder, now I only have stylecop.resharper610.dll, but still no luck. "Inspection Severity" tab settings are still missing.