Fluent C#

12. OOA&D

In the last eleven chapters, you’ve learned about C# syntax and the .NET Framework types that represent basic data. You know (in theory) how to define a type in code or by using the Visual Studio Class Designer. But if you’re like most people, the idea of starting from a problem description and working out how to represent it as .NET Framework types is probably still pretty scary. How do you decide how the problem should be divided into classes? How do you choose between classes, structures, or something else? How do you know what properties and methods they need to expose? And how are those classes going to interact to actually do something?

Every application you build is going to be different. That’s what makes application design ...