Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

Member Design Guidelines 

Types and interfaces are composed of members which can be any of the following:

  • Methods

  • Properties

  • Constructors

  • Events

  • Fields

Portions Copyright 2005 Microsoft Corporation. All rights reserved.

Portions Copyright Addison-Wesley Corporation. All rights reserved.

For more information on design guidelines, see the "Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries" book by Krzysztof Cwalina and Brad Abrams, published by Addison-Wesley, 2005.

In This Section

Member Overloading

Describes guidelines for overloaded members.

Implementing Interface Members Explicitly

Describes guidelines for explicit interface implementations.

Choosing Between Properties and Methods

Describes guidelines for determining when to implement functionality as a property versus a method.

Property Design

Describes guidelines for implementing properties.

Constructor Design

Describes guidelines for implementing constructors.

Event Design

Describes guidelines for implementing events.

Field Design

Describes guidelines for defining fields.

Operator Overloads

Describes guidelines for overloading operators.

Conversion Operators

Describes guidelines for implementing conversion operators.

Parameter Design

Describes guidelines for defining parameters.

Reference

Related Sections

.NET Framework Class Library Reference

Documents each of the public classes that constitute the .NET Framework.

Design Guidelines for Developing Class Libraries

Describes the best practices for class library development.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

Show:
© 2014 Microsoft