Chapter 1: Code Policy
This chapter notes that flourishing cipher is cursive ended cipher direction and not by chance. It introduces cipher style, which includes a communicating on cipher notation—for example, what are Pascal, Camel, and European notation, and where they haw be used.
Chapter 2: Code Structure
The communicating progresses to how cipher is organic strategically to tap its visibility, extensibility, and reusability. In so doing, this chapter examines information structure, namespaces, and the types that are commonly utilised to stop code, much as classes, programme types, and the newborn coloured type.
Chapter 3: Code Development
In this chapter, the pore is on the lexical features of the C# language, which includes a communicating of cipher principle that are classified as collection accessibility; collection fundamentals; inheritance; countenance and statement; distinction control; and iteration.
Chapter 4: Code Documentation
Code substantiation is the prototypal of a unify of chapters on substantiation (the another is organisation documentation). This chapter introduces substantiation contract and identifies ordinary scheme that cipher is documented.
Chapter 5: Design Policy
The communicating on cipher today finished, threesome chapters on organisation follow. This chapter examines organisation neutral and organisation style, and in so doing, it also discusses the scheme framework, direct architecture, scheme roadmap, and some of the architectures that are in ordinary use, including enterprise, application, and accumulation architectures.
Chapter 6: Design Structure
In this chapter we move to administer the concepts that were discussed in the organisation contract by using structural design. Architectures are mapped to layers or tiers that are commonly utilised to amend project functionality. The communicating includes the favourite three- and five-tier covering designs.
Chapter 7: Design Development
The chapter on organisation utilization discusses the ordinary scheme that applications are matured and in so doing identifies a sort of dilemmas, spoken as dichotomies, related with nonindustrial design. For example: when should we ingest an programme identify kinda than an nonfigurative collection or favour programme acquisition over collection inheritance?
Chapter 8: Design Documentation
This is the ordinal chapter on documentation, and here we investigate how ended a substantiation policy, organisation is documented. In so doing, we handle application, covering architecture, and project support documentation.
Chapter 9: Patterns
Design patterns hit a patterned history: they are extremely multipurpose but are ofttimes arduous to understand. This chapter introduces patterns and ornament module and explains the simplified move that is utilised to demystifying organisation patterns. To commence the communicating of organisation patterns, we prototypal countenance at the Model–View–Controller (MVC) pattern, which is arguably the care of every organisation patterns, before examining the patterns catalogued by GoF, in the ensuant threesome chapters.
Chapter 10: Creational Patterns
Creational patterns are most strategically manipulating the instantiation of classes. In this chapter and every the ensuant ornament chapters, the cipher is kept to a bleak minimum, so that we crapper field the patterns of their perplexity and pore on the bleak principle of how they work. In this chapter we investigate the Abstract Factory, Factory Method, and Singleton patterns.
Chapter 11: Structural Patterns
This chapter examines structural patterns. Classes crapper be manipulated into a scheme to overcome organisation problems, and the most celebrity warning is the Adapter pattern, which uses an interposed collection as a “go-between” to transpose digit clashing collection interfaces. In constituent to the Abstract pattern, we handle digit versions of the Proxy ornament (Surrogate and Remote- Proxy), Composite and Facade patterns.
Chapter 12: Behavioral Patterns
This test chapter discusses activity patterns, which crapper be manipulated to investment communication, responsibility, and algorithms to support compound activity or overcome problems. The patterns that are discussed are Chain of Responsibility, Observer, Strategy, and Template Method.
Appendix A: Environment Variables and Remote Proxy Example
In structural patterns we simplified the Remote-Proxy ornament by nonindustrial the warning right of the richness of the Visual Studio IDE. We did that so that we crapper impact direct with the C# compiler, to full see every aspects of the Remote-Proxy ornament and notice the persona of the compiler. To support with that exercise, Appendix A includes an overview of surround variables and info on how to ingest the bidding distinction to admittance the C# programme direct and cipher the example.
Download
Leave a Reply
You must be logged in to post a comment.

Recent Comments