13.07.2015 Views

C# in Depth

C# in Depth

C# in Depth

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Part 1Prepar<strong>in</strong>g for the journeyEvery reader will come to this book with a different set of expectations anda different level of experience. Are you an expert look<strong>in</strong>g to fill some holes, howeversmall, <strong>in</strong> your present knowledge? Perhaps you consider yourself an “average”developer, beg<strong>in</strong>n<strong>in</strong>g to migrate projects to .NET 2.0 but with an eye to the future.Maybe you’re reasonably confident with <strong>C#</strong> 2 but have no <strong>C#</strong> 3 experience.As an author, I can’t make every reader the same—and I wouldn’t want toeven if I could. I hope that all readers have two th<strong>in</strong>gs <strong>in</strong> common, however: thedesire for a deeper relationship with <strong>C#</strong> as a language, and at least a basic knowledgeof <strong>C#</strong> 1. If you can br<strong>in</strong>g those elements to the party, I’ll provide the rest.The potentially huge range of skill levels is the ma<strong>in</strong> reason for this partof the book exist<strong>in</strong>g. You may already know what to expect from <strong>C#</strong> 2 and 3—or it could all be brand new to you. You could have a rock-solid understand<strong>in</strong>gof <strong>C#</strong> 1, or you might be rusty on some of the details that didn’t matter muchbefore but that will become <strong>in</strong>creas<strong>in</strong>gly important as you learn <strong>C#</strong> 2 andthen 3. By the end of part 1, I won’t have leveled the play<strong>in</strong>g field entirely, butyou should be able to approach the rest of the book with confidence and anidea of what’s com<strong>in</strong>g later.For the first two chapters, we will be look<strong>in</strong>g both forward and back. One ofthe key themes of the book is evolution. Before <strong>in</strong>troduc<strong>in</strong>g any feature <strong>in</strong>to thelanguage, the design team carefully considers that feature <strong>in</strong> the context ofwhat’s already present and the general aims of the future. This br<strong>in</strong>gs a feel<strong>in</strong>gof consistency to the language even <strong>in</strong> the midst of change. To understand howand why the language is evolv<strong>in</strong>g, we need to see where we’ve come from andwhere we’re go<strong>in</strong>g to.Licensed to Rhona Hadida

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!