I try to run Run StyleCop(Rescan All) in VS 2015 and project always crash.
How can I resolve the crush?
Id #7740 | Release:
| Updated: Mon at 2:04 PM by leapold | Created: Mon at 2:04 PM by leapold
In VS2015 the new Errors view (that has been noticeably changed from VS2013) does not show StyleCop issues.
Probably it is a pending issue to accomodate the warnings to be shown in this view.
Id #7739 | Release:
| Updated: Jul 19 at 6:37 PM by susanaconstanza | Created: Jul 19 at 3:58 PM by Ravelus
Rule SA1217, which for StyleCop Classic is first included in release 4.7.51, models the rule originally implemented in StyleCop Analyzers as SA1216. The identifier assigned to this rule should matc...
Id #7738 | Release:
| Updated: Jul 19 at 8:20 PM by probackpacker | Created: Jul 15 at 1:39 PM by sharwell
According to the rules documentation from the latest release prior to the year 2016, no rule SA1216 exists. However, information regarding a rule SA1216 can be found in the repository.
The rule w...
Id #7737 | Release:
| Updated: Jul 19 at 8:20 PM by probackpacker | Created: Jul 15 at 1:37 PM by sharwell
In our codebase, we've seen cases where documentation header text contains words which are spelled correctly, but not in the correct case.
This applies to acronyms as well as proper names.
Id #7736 | Release:
| Updated: Jul 14 at 9:26 PM by Rob263 | Created: Jul 14 at 9:26 PM by Rob263
In our codebase we've often seen documentation header text like this:
/// <summary>Specifies attributes of a widget message..</summary>
Notice that the text ends with two periods instead of one.
Id #7735 | Release:
| Updated: Jul 14 at 8:48 PM by Rob263 | Created: Jul 14 at 8:48 PM by Rob263
Version 4.7.54, VS2015 and VS2013, Resharper 9.2. when being prompted regarding copyright and company name in the file headers, the information is not being populated, or is just being erased inste...
Id #7734 | Release:
| Updated: Jun 17 at 10:42 AM by Snotface | Created: Jun 17 at 10:42 AM by Snotface
If there is a spelling error due to a deprecated word, and that word has a preferred alternate specified in the dictionary file, the warning message should tell the user what the preferred term is....
Id #7733 | Release:
| Updated: Jun 22 at 2:03 AM by Rob263 | Created: Jun 16 at 6:32 PM by Rob263
Sandcastle (and I believe NDoc) support the <exclude/> documentation element, which makes it so that the documentation for that member will be excluded from the generated documentation.
Id #7732 | Release:
| Updated: Jul 5 at 8:02 PM by Rob263 | Created: Jun 16 at 5:00 PM by Rob263
StyleCop will currently only check the first <exception> tag for spelling.
The problem is in DocumentationRules.CheckHeaderElementsForEmptyText(). It calls:
xmlNode = formattedDocs.SelectSingleN...
Id #7731 | Release:
| Updated: Jun 15 at 6:06 PM by Rob263 | Created: Jun 15 at 2:15 AM by Rob263