Types that implement ICollection should also provide a version of CopyTo with the first parameter set to a strong type, namely a type other than an array of objects or System.Array. Implement the interface member explicitly and make the strongly typed version public. It is safe to ignore violations of this rule when you are implementing a new object-based collection, such as a binary tree, where types based on your collection will determine what the strong type is. These types should expose strongly typed members.
Types that declare disposable members should also implement IDisposable. If the type does not own any unmanaged resources, ...
Types that do not extend certain base types should not use reserved name suffixes. Types and members should not use 'Ex' ...
Types that extend certain base types have specified name suffixes. Types that extend Attribute, for example, should be suffixed ...
Types that extend ServicedComponent should not have the WebMethod attribute applied to members. Marking members of types ...
Types that implement ICollection should also provide a version of CopyTo with the first parameter set to a strong type, namely ...
Types that implement IComparable should redefine Equals and comparison operators to keep the meanings of less than, greater ...
Types that implement IEnumerator should also provide a version of the Current property that returns a type other than Object. ...
Types that redefine the equality operator should redefine Equals as well to ensure that these members return the same results. ...
Types with no public default constructor are not COM-creatable. COM does not support parameterized object construction. A ...