We're a Team, You and I Technology authors write for a demanding group
of people (I should know--I'm one of them). You know that building
software solutions using any platform (e. g., . NET, Java, and COM) is
extremely complicated and is highly specific to your department,
company, client base, and subject matter. Perhaps you work in the
electronic publishing industry, develop systems for the state or local
government, or work at NASA or a branch of the military. Speaking for
myself, I have developed children's educational software (Oregon Trail /
Amazon Trail anyone?), various n-tier systems, and projects within the
medical and financial industries. The chances are almost 100 percent
that the code you write at your place of employment has little to do
with the code I write at mine (unless we happened to work together
previously!). Therefore, in this book, I have deliberately chosen to
avoid creating examples that tie the example code to a specific industry
or vein of programming. Given this, I explain C#, OOP, the CLR, and the
. NET 4. 0 base class libraries using industry-agnostic examples. Rather
than having every blessed example fill a grid with data, calculate
payroll, or whatnot, I'll stick to subject matter everyone can relate
to: automobiles (with some geometric structures and employee payroll
systems thrown in for good measure). And that's where you come in. My
job is to explain the C# programming language and the core aspects of
the .
