Search

Adding mixed cased word to the Solution Dictionary still violates Code Analysis Rule CA2204 by GSAGranet

Closed
as Won't Fix Help for as Won't Fix

2
0
Sign in
 to vote
Type: Bug
ID: 776792
Opened: 1/17/2013 7:16:50 AM
Access Restriction: Public
1
Workaround(s)
0
User(s) can reproduce this bug
AllowNull in C# file always gives the warning even though it is the solution xml dictionary. The whole functionality of this area needs to be rechecked, including the ability to use acronyms and deprecation which also fail to work. In general Code Analysis for CA2204 does not function as described in the documentation at http://msdn.microsoft.com/en-us/library/bb264488.aspx.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

See above - xref to ID 521030

Product Language

English

Operating System

Windows 7 SP1

Operating System Language

English

Actual results

CA2204: Literals should be spelled correctly
Correct the spelling of the unrecognized token 'AllowNull' in the literal'"AllowNull"'.
FileName.cs (Line xx)

Expected results

Warning CA2204 should not be given.
File Attachments
0 attachments
Sign in to post a comment.
Posted by GSAGranet on 4/30/2013 at 1:15 AM
This bug was originally raised at http://connect.microsoft.com/VisualStudio/feedback/details/521030/ and then closed. It has 44 votes giving a total of 46 votes for this item.

Does this affect the triage?

We have a specialist application where the use of compound words is essential. In addition we are trying to reduce our warnings to zero.

This functionality should either work or be removed; not fudged by the workaround.

Graham
Posted by Microsoft on 4/29/2013 at 4:15 PM
Thanks for reporting this issue you've encountered with Code Analysis!

We agree that not supporting compound words does meaningfully reduce the value of the spell-checking rule. Unfortunately, a deeper fix to our spell-checking support here does not meet our triage bar for the next release of Visual Studio. We suggest trying the <DiscreteExceptions> workaround that a22kapoor posted in item 521030.

Alex Turner
Senior Program Manager
Visual Basic and C# Compiler
Posted by Microsoft on 1/17/2013 at 9:46 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 1/17/2013 at 7:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by GSAGranet on 4/30/2013 at 1:01 AM
Following up on MS comment on using the <DiscreteExceptions> workaround
This is fully described at http://connect.microsoft.com/VisualStudio/feedback/details/521030/
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement