StyleCop+

Commented Issue: CoreParser Exception [9754]

tomerr — Mon, 11 Feb 2013 09:18:36 GMT

This looks like it is happening in every C# file that has a destructor.I conditionally compiled out the destructor in one of the files having the issue, and it was able to successfully handle the file. This crash ONLY happens with StyleCop plus is used with the latest version of StyleCop -- 4.7.42.0. -=-After upgrading to the latest, I receive this on several files. Error 58 SA0001 : CoreParser : An exception occurred while parsing the file: System.MissingMethodException, Method 'StyleCop.CSharp.DocumentationRules.GetExampleSummaryTextForDestructor' not found. at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams) at StyleCopPlus.Plugin.ExtendedOriginal.ExtendedOriginalRules.GetExampleSummaryTextForDestructor(SourceAnalyzer customDocumentationAnalyzer) at StyleCopPlus.Plugin.ExtendedOriginal.ExtendedOriginalRules.Handle1643(ViolationEventArgs e) at StyleCopPlus.Plugin.ExtendedOriginal.ExtendedOriginalRules.OnCustomViolationEncountered(Object sender, ViolationEventArgs e) at StyleCop.StyleCopCore.OnViolationEncountered(ViolationEventArgs e) at StyleCop.StyleCopCore.AddViolation(ICodeElement element, Violation violation) at StyleCop.StyleCopCore.AddViolation(ICodeElement element, Rule type, Int32 line, Object[] values) at StyleCop.StyleCopAddIn.AddViolation(ICodeElement element, Int32 line, String ruleName, Object[] values) at StyleCop.StyleCopAddIn.AddViolation(ICodeElement element, Enum ruleName, Object[] values) at StyleCop.CSharp.DocumentationRules.CheckDestructorSummaryText(Destructor destructor, XmlDocument formattedDocs) at StyleCop.CSharp.DocumentationRules.ParseHeader(CsElement element, XmlHeader header, Int32 lineNumber, Boolean partialElement) at StyleCop.CSharp.DocumentationRules.CheckHeader(CsElement element, AnalyzerSettings settings, Boolean partialElement) at StyleCop.CSharp.DocumentationRules.CheckDocumentationForElement(CsElement element, CsElement parentElement, AnalyzerSettings settings) at StyleCop.CSharp.CodeWalker`1.VisitElement(CsElement element, CsElement parentElement, T& context) at StyleCop.CSharp.CodeWalker`1.WalkElement(CsElement element, CsElement parentElement, T context) at StyleCop.CSharp.CodeWalker`1.WalkElement(CsElement element, CsElement parentElement, T context) at StyleCop.CSharp.CodeWalker`1.WalkElement(CsElement element, CsElement parentElement, T context) at StyleCop.CSharp.CodeWalker`1.WalkElement(CsElement element, CsElement parentElement, T context) at StyleCop.CSharp.DocumentationRules.CheckElementDocumentation(CsDocument document) at StyleCop.CSharp.DocumentationRules.AnalyzeDocument(CodeDocument document) at StyleCopPlus.Plugin.ExtendedOriginal.ExtendedOriginalRules.AnalyzeDocument(CodeDocument document) at StyleCopPlus.StyleCopPlusRules.AnalyzeDocument(CodeDocument document) at StyleCop.StyleCopThread.RunAnalyzers(CodeDocument document, SourceParser parser, IEnumerable`1 analyzers) at StyleCop.StyleCopThread.TestAndRunAnalyzers(CodeDocument document, SourceParser parser, IEnumerable`1 analyzers, Int32 passNumber) at StyleCop.StyleCopThread.ParseAndAnalyzeDocument(SourceCode sourceCode, DocumentAnalysisStatus documentStatus) at StyleCop.StyleCopThread.DoWork(Object sender). C:\XPJustice\Source\Dev\V1.92\Dev\Platform\Diagnostics\Diagnostics\PerformanceCounters.cs 1 1 Diagnostics
Comments: ** Comment from web user: tomerr **

caused because of mismatch between stylecopplus version and stylecop version. Make sure u use the stylecop version that stylecopplus targets.
For 1.8, it should be stylecop v 4.7.17.

It appears that later version changed the signature of GetExampleSummaryTextForDestructor, so now t receives a parameter. Stylecopplus search for for the previous version (via reflection) which didn't recieve parameter, making the clr throw a runtime exception.

Commented Issue: Ignore length of [SuppressMessage] lines? [9201]

barnichb — Wed, 16 Jan 2013 03:42:44 GMT

Would it be possible to disable the length check on lines containing the SuppressMessage attribute?
 
When you add the category and the checkId (some of which can be quite long) parameters, it leaves very little space for the Justification, and it makes for ugly code to have a 2-line SuppressMessage for a 3-line method.
 
I came across an ironic case where rule SP2100 was triggering on a [SuppressMessage] that was suppressing the length check on the next line.
 
What do you think?

Comments: ** Comment from web user: barnichb **

I did this in a fork, https://github.com/barnichb/StyleCopPlus .

Created Issue: CoreParser Exception [9754]

John_H_Bergman — Thu, 29 Nov 2012 18:35:16 GMT

After upgrading to the latest, I receive this on several files.

Error 58 SA0001 : CoreParser : An exception occurred while parsing the file: System.MissingMethodException, Method 'StyleCop.CSharp.DocumentationRules.GetExampleSummaryTextForDestructor' not found.
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at StyleCopPlus.Plugin.ExtendedOriginal.ExtendedOriginalRules.GetExampleSummaryTextForDestructor(SourceAnalyzer customDocumentationAnalyzer)
at StyleCopPlus.Plugin.ExtendedOriginal.ExtendedOriginalRules.Handle1643(ViolationEventArgs e)
at StyleCopPlus.Plugin.ExtendedOriginal.ExtendedOriginalRules.OnCustomViolationEncountered(Object sender, ViolationEventArgs e)
at StyleCop.StyleCopCore.OnViolationEncountered(ViolationEventArgs e)
at StyleCop.StyleCopCore.AddViolation(ICodeElement element, Violation violation)
at StyleCop.StyleCopCore.AddViolation(ICodeElement element, Rule type, Int32 line, Object[] values)
at StyleCop.StyleCopAddIn.AddViolation(ICodeElement element, Int32 line, String ruleName, Object[] values)
at StyleCop.StyleCopAddIn.AddViolation(ICodeElement element, Enum ruleName, Object[] values)
at StyleCop.CSharp.DocumentationRules.CheckDestructorSummaryText(Destructor destructor, XmlDocument formattedDocs)
at StyleCop.CSharp.DocumentationRules.ParseHeader(CsElement element, XmlHeader header, Int32 lineNumber, Boolean partialElement)
at StyleCop.CSharp.DocumentationRules.CheckHeader(CsElement element, AnalyzerSettings settings, Boolean partialElement)
at StyleCop.CSharp.DocumentationRules.CheckDocumentationForElement(CsElement element, CsElement parentElement, AnalyzerSettings settings)
at StyleCop.CSharp.CodeWalker`1.VisitElement(CsElement element, CsElement parentElement, T& context)
at StyleCop.CSharp.CodeWalker`1.WalkElement(CsElement element, CsElement parentElement, T context)
at StyleCop.CSharp.CodeWalker`1.WalkElement(CsElement element, CsElement parentElement, T context)
at StyleCop.CSharp.CodeWalker`1.WalkElement(CsElement element, CsElement parentElement, T context)
at StyleCop.CSharp.CodeWalker`1.WalkElement(CsElement element, CsElement parentElement, T context)
at StyleCop.CSharp.DocumentationRules.CheckElementDocumentation(CsDocument document)
at StyleCop.CSharp.DocumentationRules.AnalyzeDocument(CodeDocument document)
at StyleCopPlus.Plugin.ExtendedOriginal.ExtendedOriginalRules.AnalyzeDocument(CodeDocument document)
at StyleCopPlus.StyleCopPlusRules.AnalyzeDocument(CodeDocument document)
at StyleCop.StyleCopThread.RunAnalyzers(CodeDocument document, SourceParser parser, IEnumerable`1 analyzers)
at StyleCop.StyleCopThread.TestAndRunAnalyzers(CodeDocument document, SourceParser parser, IEnumerable`1 analyzers, Int32 passNumber)
at StyleCop.StyleCopThread.ParseAndAnalyzeDocument(SourceCode sourceCode, DocumentAnalysisStatus documentStatus)
at StyleCop.StyleCopThread.DoWork(Object sender). C:\XPJustice\Source\Dev\V1.92\Dev\Platform\Diagnostics\Diagnostics\PerformanceCounters.cs 1 1 Diagnostics

New Post: Namspace with dot (".")

trbaphong — Tue, 06 Nov 2012 04:00:21 GMT

I want to check whether all namespace begin with "App." or not. How can I do this

New Post: Exception Loading StyleCop+

adhemar82 — Sat, 03 Nov 2012 15:49:01 GMT

*Edit*

Never mind, I found out what the issue was for me. It seems in Windows 8 you have to be extra careful when unblocking the dll. If you do it with the dll in the StyleCop dir (where you need admin rights), it fails silently (if you go back to properties you'll see the Unblock button is there again).

To get around this, you have to first put the dll in a dir you own, your desktop for example, unblock it there, then copy it over to the StyleCop dir. That fixed it for me.

Oleg, you might want to amend your documentation with this info.

New Post: Exception Loading StyleCop+

shuruev — Fri, 02 Nov 2012 10:41:10 GMT

Hi guys,

Sorry for the long delay - was very busy with my job.

StyleCop+ 1.8 works with any StyleCop version, newer than 4.7.17.
Right now, I am using StyleCop 4.7.39.0, both in Windows 7 + VS2010 as well as Windows 8 + VS2012.

All the compatibility issues seems gone in past.
I guess I should update release comment and documentation to make it more clear.

Please let me know if something does not work, I think I can help.

Thank you!

Commented Issue: Namespace issue with two letter acronyms [7110]

shuruev — Fri, 02 Nov 2012 10:36:23 GMT

I found an issue with naming namespaces. The MSDN (e.g. http://msdn.microsoft.com/en-us/library/893ke618%28VS.71%29.aspx) says (I follow that rules) that two letter acronyms are written in uppercase where acronyms with more than two letters are written "first letter upper case, the rest lower case):
System.IO (NOT: System.Io)
System.Web
System.Web.UI
System.Gps (NOT: GPS)
etc.
 
When I use MyNamespace.IO than StyleCop+ will give me a SP0100 warning.
 
Workaround: Abbreviations: Add "IO", "UI" etc.
But this is only a workaround since the abbreviations are used for everything (local variable like: someUI would'nt be nice).

Comments: ** Comment from web user: shuruev **

Hi Calinoiu,
Could you please specify what did you mean in more details?

If you add "UI", for example, into abbreviations, and $(AaBb) is your template, then the following will be allowed:
- SimpleUI
- SimpleUIAndTools
- UITools

Or did you mean that you don't like specifying abbreviations list and would like to allow every two-letter combination as an abbreviation (like if you added all AA AB AC AD etc... combinations into your abbreviation list)?

New Post: Exception Loading StyleCop+

GruetzmacherD — Tue, 23 Oct 2012 19:29:03 GMT

Is using StyleCop+ with newer builds of StyleCop than 4.7.17 supported? If not, is an official updated build of StyleCop+ forthcoming?

Thanks :)

Dominic

Commented Issue: Namespace issue with two letter acronyms [7110]

calinoiu — Wed, 17 Oct 2012 19:27:54 GMT

Short acronyms can occur anywhere in a name. Since the $(AaBb) and $(aaBb) macros don't account for this, I'm having to resort to fun stuff like the following:

$(AaBb)
$(A)$(AaBb)
$(A)$(A)$(AaBb)
$(AaBb)$(A)$(AaBb)
$(AaBb)$(A)$(A)$(AaBb)
... and more permutations.

Given that caps are the (unfortunate) standard for acronyms under 3 characters, it would really be very helpful if there were macros that accounted for them. (Presumably these would need to be new macros since there are probably a lot of folks who like the current macro behaviour.)

Closed Issue: Exception error "Operation not supported" while trying to load StyleCop Plus [9661]

shuruev — Tue, 09 Oct 2012 03:59:57 GMT

I've installed StyleCop and wanted to add StyleCop+ to it so I dropped the StyleCopPlus.dll into the StyleCop installed directory. As soon as I do that, I get an exception whenever I start Visual Studio that says an exception occurred while loading on of the StyleCop add-ins.
 
OS: Windows 8 x64
Visual Studio Version: 2012 Ultimate
StyleCop Version: 4.7.39
StyleCopPlus Version: 1.8.0

Comments:

Commented Issue: Exception error "Operation not supported" while trying to load StyleCop Plus [9661]

mgressman — Tue, 09 Oct 2012 00:40:46 GMT

Deleting the existing file and downloading again solved the problem. Apparently, the file that I originally downloaded would not unblock. Downloading a new one and unblocking solved the problem.

Thanks for the help.

Commented Issue: Exception error "Operation not supported" while trying to load StyleCop Plus [9661]

shuruev — Sat, 06 Oct 2012 10:26:16 GMT

Hi again,
The error you get is exactly about "blocked" StyleCopPlus.dll.

After you donwloaded StyleCopPlus.dll, you should select it in Explorer, make a right click and press "Unblock" button.
In you case I would even recommend you deleting StyleCopPlus.dll, closing Visual Studio, download StyleCopPlus.dll once again, unblock it in downloads folder, and than copy "unblocked" version to Program Files\Style Cop folder.

This should definitely help, please respond if some issues still occur.
Thank you!

P.S. And yes, I did test it on Windows 8 x64 + Visual Studio 2012 Premium + StyleCop 4.7.41.

Commented Issue: Exception error "Operation not supported" while trying to load StyleCop Plus [9661]

mgressman — Sat, 06 Oct 2012 00:18:41 GMT

The problem only happens when starting up Visual Studio. I can edit the StyleCop settings file successfully outside of Visual Studio and the StyleCop+ tab is there. It is only when actually trying to open Visual Studio that the exception occurs.

Has anyone else tested StyleCop+ with Windows 8 and Visual Studio 2012?

Commented Issue: Exception error "Operation not supported" while trying to load StyleCop Plus [9661]

shuruev — Thu, 04 Oct 2012 16:32:06 GMT

Hi mgressman,
Didn't you forget to Unblock downloaded DLL like it's said here?
http://stylecopplus.codeplex.com/wikipage?title=Quick%20Start%20Guide

Source code checked in, #69631

Project Collection Service Accounts — Mon, 01 Oct 2012 21:13:48 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #69630

Project Collection Service Accounts — Mon, 01 Oct 2012 21:07:03 GMT

Checked in by server upgrade

Created Issue: Exception error "Operation not supported" while trying to load StyleCop Plus [9661]

mgressman — Sat, 29 Sep 2012 03:17:23 GMT

I've installed StyleCop and wanted to add StyleCop+ to it so I dropped the StyleCopPlus.dll into the StyleCop installed directory. As soon as I do that, I get an exception whenever I start Visual Studio that says an exception occurred while loading on of the StyleCop add-ins.

OS: Windows 8 x64
Visual Studio Version: 2012 Ultimate
StyleCop Version: 4.7.39
StyleCopPlus Version: 1.8.0

New Post: Exception Loading StyleCop+

adhemar82 — Sat, 15 Sep 2012 16:40:10 GMT

This problem was indeed solved for a while but it's now back for me:

StyleCopPlus.dll 1.8.0.0 (unblocked as explained)

StyleCop.dll 4.7.36.0

VS2012 Professional

x64 Windows 8

Are you planning on building a new StyleCop+ dll?

Created Issue: SP2100: CodeLineMustNotBeLongerThan is supported? [9540]

angellaa — Thu, 09 Aug 2012 10:27:57 GMT

Hello,

I am using Stylecop for Resharper and I can't find in the UI a way to set a maximum number of characters for my files (C#, Javascript, CSS) and show a warning in case of violation.

Any help?

Thanks

New Post: What is the difference between RegionDirective and Region?

Swapna554 — Tue, 07 Aug 2012 05:28:28 GMT

I would like to know the difference between RedionDirective and Region provided in StyleCop SDK.

I would also like to know how are they usefull programatically. with an example like in which situation what should be used.

Please help me as easr;y as possible.

Thanks,

Swapna