.NET Framework Design Guidelines pudn（。）.doc

.NET Framework Design Guidelines Desiging Class Libraries for the .NET Framework Public version of the document can be found at /team/libraries/. Overview Moving to a managed execution environment offers an opportunity to improve the programming model. The goal of this document is to encourage consistency and predictability in the publicly exposed APIs while enabling integration with multiple languages and application models. Document Info Owner KCwalina Last Saved 7/11/2005 File designguidelines.doc Primary Reviewers urtlib; External reviewers netprof; lapilead UE GlennHa Contributors The following people substantially contributed to the document: Brad Abrams, Chris Anderson, Erik Christensen, Jason Clark, Krzysztof Cwalina, Patrick Dussud, Anders Hejlsberg, Jim Miller, Michael Murray, Lance Olson, Chi-Yan Tong, Eric Gunnerson, Dare Obasanjo, Ahmed Abou-Taleb, Steve Starck. Table of Contents 1 Introduction 7 1.1 Goals 8 1.2 How to Read the Document 9 1.2.1 Document Styles 9 1.2.2 FxCop Rules Coverage 10 2 Library Design Fundamentals 10 2.1 Targeting the Breadth of Developers 10 2.1.1 Architecture 11 2.2 Exposing Functionality to COM [TO be removed when new section added] 13 3 Naming Guidelines 13 3.1 Capitalization Conventions 14 3.1.1 Capitalization Rules for Identifiers 14 3.1.2 Capitalizing Acronyms 16 3.1.3 Capitalizing Compound Words and Common Terms 18 3.1.4 Case Sensitivity 19 3.2 General Naming Conventions 20 3.2.1 Word Choice 20 3.2.2 Using Abbreviations and Acronyms 22 3.2.3 Avoiding Language-specific Names 22 3.3 Names of Assemblies and DLLs 24 3.4 Names of Namespaces 25 3.4.1 Standard Sub-Namespace Names 26 3.4.2 Namespaces and Type Name Conflicts 28 3.4.3 WinFx Namespace Plan (MS Internal) 29 3.5 Names of Classes, Value Types, and Interfaces 33 3.5.1 Names of Generic Type Parameters 35 3.5.2 Names of Common Types 36 3.5.3 Naming Enumerations 38 3.6 Names of Type Members 39 3.6.1 Names of Methods 39 3.6.2 Names of Properties 39 3.6.3 Names of Ev