|
Chapter 1: Code Policy - This chapter notes that successful code is written through code management and not by chance. It introduces code style, which includes a discussion on code notation—for example, what are Pascal, Camel, and Hungarian notation, and where they may be used.Chapter 2: Code Structure - The discussion progresses to how code is structured strategically to maximize its visibility, extensibility, and reusability. In so doing, this chapter examines program structure, namespaces, and the types that are commonly used to hold code, such as classes, interface types, and the new partial type. Chapter 3: Code Development - In this chapter, the focus is on the lexical features of the C# language, which includes a discussion of code fundamentals that are categorized as class accessibility; class fundamentals; inheritance; expression and statement; flow control; and iteration. Chapter 4: Code Documentation - Code documentation is the first of a pair of chapters on documentation. This chapter introduces documentation policy and identifies common ways that code is documented. Chapter 5: Design Policy - The discussion on code now finished, three chapters on design follow. This chapter examines design objective and design style, and in so doing, it also discusses the architecture framework, target architecture, architecture roadmap, and many of the architectures that are in common use, including enterprise, application, and data architectures. Chapter 6: Design Structure - In this chapter we start to apply the concepts that were discussed in the design policy by using structural design. Architectures are mapped to layers or tiers that are commonly used to develop enterprise functionality. Chapter 7: Design Development - The chapter on design development discusses the common ways that applications are developed and in so doing identifies a number of dilemmas, expressed as dichotomies, associated with developing design. Chapter 8: Design Documentation - This is the second chapter on documentation, and here we examine how through a documentation policy, design is documented. Chapter 9: Patterns - Design patterns have a checkered history: they are extremely useful but are often difficult to understand. This chapter introduces patterns and pattern language and explains the simplified approach that is used to demystifying design patterns. Chapter 10: Creational Patterns - Creational patterns are about strategically manipulating the instantiation of classes. In this chapter and all the subsequent pattern chapters, the code is kept to a bare minimum, so that we can strip the patterns of their mystery and focus on the bare basics of how they work. Chapter 11: Structural Patterns - This chapter examines structural patterns. Classes can be manipulated into a structure to overcome design problems, and the most notable example is the Adapter pattern, which uses an interposed class as a “go-between” to map two incompatible class interfaces. Chapter 12: Behavioral Patterns - This final chapter discusses behavioral patterns, which can be manipulated to leverage communication, responsibility, and algorithms to help enhance behavior or overcome problems. Download free pdf ebooks on c#: Pro .NET 2.0 Code and Design Standards in C#
|
Free programing ebooks
Chapter 1: Code Policy - This chapter notes that successful code is written through code management and not by chance. It introduces code style, which includes a discussion on code notation—for example, what are Pascal, Camel, and Hungarian notation, and where they may be used.