Provides guidelines for naming assemblies, namespaces, types, and members in class libraries. NET Libraries, 2nd Edition, by Krzysztof Cwalina and Brad Abrams. These guidelines are excerpted from the book Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable. Such cases should be rare, and it is important that you have a clear and compelling reason for your decision. There might be situations where good library design requires that you violate these design guidelines. These guidelines are intended to help class library designers understand the trade-offs between different solutions. The guidelines are organized as simple recommendations prefixed with the terms Do, Consider, Avoid, and Do not. Inconsistent library design adversely affects developer productivity and discourages adoption. We recommend that you follow these design guidelines when developing classes and components that extend the. The goal is to help library designers ensure API consistency and ease of use by providing a unified programming model that is independent of the programming language used for development. This section provides guidelines for designing libraries that extend and interact with the.
0 kommentar(er)
