Search gotdotnet for:
GotDotNet User Sample: Custom FxCop Rules: No Numerals in Variable Names, Naming Constants

   GotDotNet User Samples will be up and running - further update in Fall, 2007
   We will not phase out User Samples until we can provide customers with a great alternative. We will update you with futher schedule information in Fall, 2007.
 
 

   The GotDotNet site is being phased out

   Microsoft will be phasing out most features of the GotDotNet site by July 2007.
      
  • More about the GotDotNet phase-out
  • Contact the GotDotNet Support Team
  •  
     

    Return to User Samples home

    Custom FxCop Rules: No Numerals in Variable Names, Naming Constants
    Uploaded by JasonDCamp
     
    Description Avoid numerals in variable names.
    Capitalize the names of constants and separate the words with underscores.
    Downloads 5782 Target audience Beginner
    Uploaded date 7/6/2005 Edited date 7/6/2005
    Technologies
    Languages
  • C#


  • Rating for Custom FxCop Rules: No Numerals in Variable Names, Naming Constants
    Rate this resource
     
    Overall rating Number of votes 1

    Comments
    The comments below are provided by GotDotNet users and in no way reflect the opinions of Microsoft Corporation and/or the GotDotNet team.
    Posted by  
    User Posts:
    2
    Error loading XML
    Posted on:  10/24/2005 23:01:03


    I've made a similar class like this but checking the first letter of the checked variable. The class structure of the class and XML file are the same with this example but I have problem adding it to FxCop I always get "Error loading rule 'TypeAsPrefix': The following stream was not found in the assembly manifest: TestRules.xml" error. Anybody has a symilar problem?
    User Posts:
    2
    Error loading XML
    Posted on:  10/24/2005 23:46:15


    Fixed by putting the XML file as "Embedded Resource" in the solution


    [Printer friendly version]
    © Copyright 2007 Microsoft Corporation. All Rights Reserved.
    Terms of Use | Privacy Statement | Code of Conduct | About the team | Contact Us