﻿<?xml version="1.0" encoding="utf-8"?><Type Name="DoNotUseReservedInEnumValueNamesRule" FullName="Gendarme.Rules.Naming.DoNotUseReservedInEnumValueNamesRule"><TypeSignature Language="C#" Value="public class DoNotUseReservedInEnumValueNamesRule : Gendarme.Framework.Rule, Gendarme.Framework.ITypeRule" /><TypeSignature Language="ILAsm" Value=".class public auto ansi beforefieldinit DoNotUseReservedInEnumValueNamesRule extends Gendarme.Framework.Rule implements class Gendarme.Framework.IRule, class Gendarme.Framework.ITypeRule" /><AssemblyInfo><AssemblyName>Gendarme.Rules.Naming</AssemblyName><AssemblyVersion>3.10.0.0</AssemblyVersion></AssemblyInfo><Base><BaseTypeName>Gendarme.Framework.Rule</BaseTypeName></Base><Interfaces><Interface><InterfaceName>Gendarme.Framework.ITypeRule</InterfaceName></Interface></Interfaces><Attributes><Attribute><AttributeName>Gendarme.Framework.FxCopCompatibility("Microsoft.Naming", "CA1700:DoNotNameEnumValuesReserved")</AttributeName></Attribute><Attribute><AttributeName>Gendarme.Framework.Problem("This type is an enumeration that contains value(s) named 'reserved'.")</AttributeName></Attribute><Attribute><AttributeName>Gendarme.Framework.Solution("The 'reserved' value should be removed since there is no need to reserve enum values.")</AttributeName></Attribute></Attributes><Docs><summary>
            This rule checks for enumerations that contain values named <c>reserved</c>. This
            practice, often seen in C/C++ sources, is not needed in .NET since adding new
            values will not normally break binary compatibility. However renaming a <c>reserved</c>
            enum value can since there is no way to prevent people from using the old value.
            </summary><remarks>To be added.</remarks><example>
            Bad example:
            <code>
            public enum Answer {
            	Yes,
            	No,
            	Reserved
            	// ^ renaming this to 'Maybe' would be a breaking change
            }
            </code></example><example>
            Good example:
            <code>
            public enum Answer {
            	Yes,
            	No
            	// we can add Maybe here without causing a breaking change
            	// (but note that we may break code if we change the values of
            	// existing enumerations)
            }
            </code></example></Docs><Members><Member MemberName=".ctor"><MemberSignature Language="C#" Value="public DoNotUseReservedInEnumValueNamesRule ();" /><MemberSignature Language="ILAsm" Value=".method public hidebysig specialname rtspecialname instance void .ctor() cil managed" /><MemberType>Constructor</MemberType><AssemblyInfo><AssemblyVersion>3.10.0.0</AssemblyVersion></AssemblyInfo><Parameters /><Docs><summary>To be added.</summary><remarks>To be added.</remarks></Docs></Member><Member MemberName="CheckType"><MemberSignature Language="C#" Value="public Gendarme.Framework.RuleResult CheckType (Mono.Cecil.TypeDefinition type);" /><MemberSignature Language="ILAsm" Value=".method public hidebysig newslot virtual instance valuetype Gendarme.Framework.RuleResult CheckType(class Mono.Cecil.TypeDefinition type) cil managed" /><MemberType>Method</MemberType><AssemblyInfo><AssemblyVersion>3.10.0.0</AssemblyVersion></AssemblyInfo><ReturnValue><ReturnType>Gendarme.Framework.RuleResult</ReturnType></ReturnValue><Parameters><Parameter Name="type" Type="Mono.Cecil.TypeDefinition" /></Parameters><Docs><param name="type">To be added.</param><summary>To be added.</summary><returns>To be added.</returns><remarks>To be added.</remarks></Docs></Member></Members></Type>