Types that are automatically ordered by the runtime should not be visible to COM. Types that are automatically laid out by the runtime do not have a guaranteed order between versions. This can break COM clients of those types. To ensure compatibility between versions, the type should be explicitly or sequentially ordered.
Types and methods with a high degree of class coupling, cyclomatic complexity and/or program length can be difficult to maintain. ...
Types can have types or values as parameters. For example, a type defining a Bag could have a parameter representing the ...
Types deriving from the data collection context cannot be used for sending data and messages. The DataCollectionContext used ...
Types that allocate unmanaged resources should implement IDisposable to allow callers to release those resources on demand. ...
Types that are automatically ordered by the runtime should not be visible to COM. Types that are automatically laid out by ...
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 ...