Head First C sharp

action over and over; 2.11 if/else statements make decisions; 2.12 Build an app from the ground up; 2.13 Make each button do something; 2.14 Set up conditions and see if they're true; 2.15 Windows Desktop apps are easy to build; 2.16 Rebuild your app for Windows Desktop; 2.17 Your desktop app knows where to start; 2.18 You can change your program's entry point; 2.19 When you change things in the IDE, you're also changing your code;Chapter 3: Objects: Get Oriented!: Making code make sense; 3.1 How Mike thinks about his problems; 3.2 How Mike's car navigation system thinks about his problems; 3.3 Mike's Navigator class has methods to set and modify routes; 3.4 Use what you've learned to build a program that uses a class; 3.5 Mike gets an idea; 3.6 Mike can use objects to solve his problem; 3.7 You use a class to build an object; 3.8 When you create a new object from a class, it's called an instance of that class; 3.9 A better solution...brought to you by objects!; 3.10 An instance uses fields to keep track of things; 3.11 Let's create some instances!; 3.12 Thanks for the memory; 3.13 What's on your program's mind; 3.14 You can use class and method names to make your code intuitive; 3.15 Give your classes a natural structure; 3.16 Class diagrams help you organize your classes so they make sense; 3.17 Build a class to work with some guys; 3.18 Create a project for your guys; 3.19 Build a form to interact with the guys; 3.20 There's an easier way to initialize objects; 3.21 A few ideas for designing intuitive classes;Chapter 4: Types and References: It's 10:00. Do you know where your data is?; 4.1 The variable's type determines what kind of data it can store; 4.2 A variable is like a data to-go cup; 4.3 10 pounds of data in a 5-pound bag; 4.4 Even when a number is the right size, you can't just assign it to any variable; 4.5 When you cast a value that's too big, C# will adjust it automatically; 4.6 C# does some casting automatically; 4.7 When you call a method, the arguments must be compatible with the types of the parameters; 4.8 Debug the mileage calculator; 4.9 Combining = with an operator; 4.10 Objects use variables, too; 4.11 Refer to your objects with reference variables; 4.12 References are like labels for your object; 4.13 If there aren't any more references, your object gets garbage-collected; 4.14 Multiple references and their side effects; 4.15 Two references means TWO ways to change an object's data; 4.16 A special case: arrays; 4.17 Arrays can contain a bunch of reference variables, too; 4.18 Welcome to Sloppy Joe's Budget House o' Discount Sandwiches!; 4.19 Objects use references to talk to each other; 4.20 Where no object has gone before; 4.21 Build a typing game; 4.22 Controls are objects, just like any other object;C# Lab: A Day at the Races; Chapter 5: Encapsulation: Keep your privates... Private; 5.1 Kathleen is an event planner; 5.2 What does the estimator do?; 5.3 You're going to build a program for Kathleen; 5.4 Kathleen's test drive; 5.5 Each option should be calculated individually; 5.6 It's easy to accidentally misuse your objects; 5.7 Encapsulation means keeping some of the data in a class private; 5.8 Use encapsulation to control access to your class's methods and fields; 5.9 But is the RealName field REALLY protected?; 5.10 Private fields and methods can only be accessed from inside the class; 5.11 A few ideas for encapsulating classes; 5.12 Encapsulation keeps your data pristine; 5.13 Properties make encapsulation easier; 5.14 Build an application to test the Farmer class; 5.15 Use automatic properties to finish the class; 5.16 What if we want to change the feed multiplier?; 5.17 Use a constructor to initialize private fields; Chapter 6: Inheritance: Your object's family tree; 6.1 Kathleen does birthday parties, too; 6.2 We need a BirthdayParty class; 6.3 Build the Part y Planner version 2.0; 6.4 One more thing...can you add a $100 fee for parties over 12?; 6.5 When your classes use inheritance, you only need to write your code once; 6.6 Build up your class model by starting general and getting more specific; 6.7 How would you design a zoo simulator?; 6.8 Use inheritance to avoid duplicate code in subclasses; 6.9 Different animals make different noises; 6.10 Think about how to group the animals; 6.11 Create the class hierarchy; 6.12 Every subclass extends its base class; 6.13 Use a colon to inherit from a base class; 6.14 We know that inheritance adds the base class fields, properties, and methods to the subclass...; 6.15 A subclass can override methods to change or replace methods it inherited; 6.16 Any place where you can use a base class, you can use one of its subclasses instead; 6.17 A subclass can hide methods in the superclass; 6.18 Use the override and virtual keywords to inherit behavior; 6.19 A subclass can access its base class using the base keyword; 6.20 When a base class has a constructor, your subclass needs one, too; 6.21 Now you're ready to finish the job for Kathleen!; 6.22 Build a beehive management system; 6.23 How you'll build the beehive management system; 6.24 Use inheritance to extend the bee management system; Chapter 7: Interfaces and Abstract Classes: Making classes keep their promises; 7.1 Let's get back to bee-sics; 7.2 We can use inheritance to create classes for different types of bees; 7.3 An interface tells a class that it must implement certain methods and properties; 7.4 Use the interface keyword to define an interface; 7.5 Now you can create an instance of NectarStinger that does both jobs; 7.6 Classes that implement interfaces have to include ALL of the interface's methods; 7.7 Get a little practice using interfaces; 7.8 You can't instantiate an interface, but you can reference an interface; 7.9 Interface references work just like object references; 7.10 You can find out if a class implements a certain interface with "is"; 7.11 Interfaces can inherit from other interfaces; 7.12 The RoboBee 4000 can do a worker bee's job without using valuable honey; 7.13 is tells you what an object implements; as tells the compiler how to treat your object; 7.14 A CoffeeMaker is also an Appliance; 7.15 Upcasting works with both objects and interfaces; 7.16 Downcasting lets you turn your appliance back into a coffee maker; 7.17 Upcasting and downcasting work with interfaces, too; 7.18 There's more than just public and private; 7.19 Access modifiers change visibility; 7.20 Some classes should never be instantiated; 7.21 An abstract class is like a cross between a class and an interface; 7.22 Like we said, some classes should never be instantiated; 7.23 An abstract method doesn't have a body; 7.24 Polymorphism means that one object can take many different forms; Chapter 8: Enums and Collections: Storing lots of data; 8.1 Strings don't always work for storing categories of data; 8.2 Enums let you work with a set of valid values; 8.3 Enums let you represent numbers with names; 8.4 We could use an array to create a deck of cards...; 8.5 Arrays are hard to work with; 8.6 Lists make it easy to store collections of...anything; 8.7 Lists are more flexible than arrays; 8.8 Lists shrink and grow dynamically; 8.9 Generics can store any type; 8.10 Collection initializers are similar to object initializers; 8.11 Let's create a List of Ducks; 8.12 Lists are easy, but SORTING can be tricky; 8.13 IComparable helps your list sort its ducks; 8.14 Use IComparer to tell your List how to sort; 8.15 Create an instance of your comparer object; 8.16 IComparer can do complex comparisons; 8.17 Overriding a ToString() method lets an object describe itself; 8.18 Update your foreach loops to let your Ducks and Cards print themselves; 8.19 You can upcast an entire list using IEnumerable; 8.20 You can build your own overloaded methods; 8.21 Use a dictionary to store keys and values; 8.22 The dictionary functionality rundown; 8.23 Build a program that uses a dictionary; 8.24 And yet MORE collection types...; 8.25 A queue is FIFO-First In, First Out; 8.26 A stack is LIFO-Last In, First Out; Chapter 9: Reading and Writing Files: Save the last byte for me!; 9.1 .NET uses streams to read and write data; 9.2 Different streams read and write different things; 9.3 A FileStream reads and writes bytes to a file; 9.4 Write text to a file in three simple steps; 9.5 The Swindler launches another diabolical plan; 9.6 Reading and writing using two objects; 9.7 Data can go through more than one stream; 9.8 Use built-in objects to pop up standard dialog boxes; 9.9 Dialog boxes are just another WinForms control; 9.10 Dialog boxes are objects, too; 9.11 Use the built-in File and Directory classes to work with files and directories; 9.12 Use file dialogs to open and save files (all with just a few lines of code); 9.13 IDisposable makes sure your objects are disposed of properly; 9.14 Avoid filesystem errors with using statements; 9.15 Trouble at work; 9.16 Writing files usually involves making a lot of decisions; 9.17 Use a switch statement to choose the right option; 9.18 Use a switch statement to let your deck of cards read from a file or write itself out to one; 9.19 Add an overloaded Deck() constructor that reads a deck of cards in from a file; 9.20 What happens to an object when it's serialized?; 9.21 But what exactly IS an object's state? What needs to be saved?; 9.22 When an object is serialized, all of the objects it refers to get serialized, too...; 9.23 Serialization lets you read or write a whole object graph all at once; 9.24 If you want your class to be serializable, mark it with the [Serializable] attribute; 9.25 Let's serialize and deserialize a deck of cards; 9.26 .NET uses Unicode to store characters and text; 9.27 C# can use byte arrays to move data around; 9.28 Use a BinaryWriter to write binary data; 9.29 You can read and write serialized files manually, too; 9.30 Find where the files differ, and use that information to alter them; 9.31 Working with binary files can be tricky; 9.32 Use file streams to build a hex dumper; 9.33 StreamReader and StreamWriter will do just fine (for now); 9.34 Use Stream.Read() to read bytes from a stream;C# Lab: The Quest; Chapter 10: Designing Windows Store Apps with XAML: Taking your apps to the next level; 10.1 Brian's running Windows 8; 10.2 Windows Forms use an object graph set up by the IDE; 10.3 Use the IDE to explore the object graph; 10.4 Windows Store apps use XAML to create UI objects; 10.5 Redesign the Go Fish! form as a Windows Store app page; 10.6 Page layout starts with controls; 10.7 Rows and columns can resize to match the page size; 10.8 Use the grid system to lay out app pages; 10.9 Data binding connects your XAML pages to your classes; 10.10 XAML controls can contain text...and more; 10.11 Use data binding to build Sloppy Joe a better menu; 10.12 Use static resources to declare your objects in XAML; 10.13 Use a data template to display objects; 10.14 INotifyPropertyChanged lets bound objects send updates; 10.15 Modify MenuMaker to notify you when the GeneratedDate property changes; Chapter 11: Async, Await, and Data Contract Serialization: Pardon the interruption; 11.1 Brian runs into file trouble; 11.2 Windows Store apps use await to be more responsive; 11.3 Use the FileIO class to read and write files; 11.4 Build a slightly less simple text editor; 11.5 A data contract is an abstract definition of your object's data; 11.6 Use async methods to find and open files; 11.7 KnownFolders helps you access high-profile folders; 11.8 The whole object graph is serialized to XML; 11.9 Stream some Guy objects to XML files; 11.10 Take your Guy Serializer for a test drive; 11.11 Use a Task to call one async method from another; 11.12 Build Brian a new Excuse Manager app; 11.13 Separate the page, excuse, and Excuse Manager; 11.14 Create the main page for the Excuse Manager; 11.15 Add the app bar to the main page; 11.16 Build the ExcuseManager class; 11.17 Add the code-behind for the page; Chapter 12: Exception Handling: Putting out fires gets old; 12.1 Brian needs his excuses to be mobile; 12.2 When your program throws an exception, .NET generates an Exception object; 12.3 Brian's code did something unexpected; 12.4 All exception objects inherit from Exception; 12.5 The debugger helps you track down and prevent exceptions in your code; 12.6 Use the IDE's debugger to ferret out exactly what went wrong in the Excuse Manager; 12.7 Uh oh-the code's still got problems...; 12.8 Handle exceptions with try and catch; 12.9 Use the debugger to follow the try/catch flow; 12.10 If you have code that ALWAYS should run, use a finally block; 12.11 Use the Exception object to get information about the problem; 12.12 Use more than one catch block to handle multiple types of exceptions; 12.13 One class throws an exception that a method in another class can catch; 12.14 Bees need an OutOfHoney exception; 12.15 An easy way to avoid a lot of problems: using gives you try and finally for free; 12.16 Exception avoidance: implement IDisposable to do your own cleanup; 12.17 The worst catch block EVER: catch-all plus comments; 12.18 Temporary solutions are OK (temporarily); 12.19 A few simple ideas for exception handling; 12.20 Brian finally gets his vacation...; Chapter 13: Captain Amazing: The Death of the Object; 13.1 Your last chance to DO something... your object's finalizer; 13.2 When EXACTLY does a finalizer run?; 13.3 Dispose() works with using; finalizers work with garbage collection; 13.4 Finalizers can't depend on stability; 13.5 Make an object serialize itself in its Dispose(); 13.6 A struct looks like an object...; 13.7 ...but isn't an object; 13.8 Values get copied; references get assigned; 13.9 Structs are value types; objects are reference types; 13.10 The stack vs. the heap: more on memory; 13.11 Use out parameters to make a method return more than one value; 13.12 Pass by reference using the ref modifier; 13.13 Use optional parameters to set default values; 13.14 Use nullable types when you need nonexistent values; 13.15 Nullable types help you make your programs more robust; 13.16 "Captain" Amazing...not so much; 13.17 Extension methods add new behavior to EXISTING classes; 13.18 Extending a fundamental type: string; Chapter 14: Querying Data and Building Apps With Linq: Get control of your data; 14.1 Jimmy's a Captain Amazing super-fan...; 14.2 ...but his collection's all over the place; 14.3 LINQ can pull data from multiple sources; 14.4 .NET collections are already set up for LINQ; 14.5 LINQ makes queries easy; 14.6 LINQ is simple, but your queries don't have to be; 14.7 Jimmy could use some help; 14.8 Start building Jimmy an app; 14.9 Use the new keyword to create anonymous types; 14.10 LINQ is versatile; 14.11 Add the new queries to Jimmy's app; 14.12 LINQ can combine your results into groups; 14.13 Combine Jimmy's values into groups; 14.14 Use join to combine two collections into one sequence; 14.15 Jimmy saved a bunch of dough; 14.16 Use semantic zoom to navigate your data; 14.17 Add semantic zoom to Jimmy's app; 14.18 You made Jimmy's day; 14.19 The IDE's Split App template helps you build apps for navigating data; Chapter 15: Events and Delegates: What your code does when you're not looking; 15.1 Ever wish your objects could think for themselves?; 15.2 But how does an object KNOW to respond?; 15.3 When an EVENT occurs...objects listen; 15.4 One object raises its event, others listen for it...; 15.5 Then, the other objects handle the event; 15.6 Connecting the dots; 15.7 The IDE generates event handlers for you automatically; 15.8 Generic EventHandlers let you define your own event types; 15.9 Windows Forms use many different events; 15.10 One event, multiple handlers; 15.11 Windows Store apps use events for process lifetime management; 15.12 Add process lifetime management to Jimmy's comics; 15.13 XAML controls use routed events; 15.14 Create an app to explore routed events; 15.15 Connecting event senders with event listeners; 15.16 A delegate STANDS IN for an actual method; 15.17 Delegates in action; 15.18 An object can subscribe to an event...; 15.19 Use a callback to control who's listening; 15.20 A callback is just a way to use delegates; 15.21 MessageDialog uses the callback pattern; 15.22 Use delegates to use the Windows settings charm; Chapter 16: Architecting Apps with the mvvm Pattern: Great apps on the inside and outside; 16.1 The Head First Basketball Conference needs an app; 16.2 But can they agree on how to build it?; 16.3 Do you design for binding or for working with data?; 16.4 MVVM lets you design for binding and data; 16.5 Use the MVVM pattern to start building the basketball roster app; 16.6 User controls let you create your own controls; 16.7 The ref needs a stopwatch; 16.8 MVVM means thinking about the state of the app; 16.9 Start building the stopwatch app's Model; 16.10 Events alert the rest of the app to state changes; 16.11 Build the view for a simple stopwatch; 16.12 Add the stopwatch ViewModel; 16.13 Finish the stopwatch app; 16.14 Converters automatically convert values for binding; 16.15 Converters can work with many different types; 16.16 Styles set properties on multiple controls; 16.17 Use a resource dictionary to share resources between pages; 16.18 Visual states make controls respond to changes; 16.19 Use DoubleAnimation to animate double values; 16.20 Use object animations to animate object values; 16.21 Build an analog stopwatch using the same ViewModel; 16.22 UI controls can be instantiated with C# code, too; 16.23 C# can build "real" animations, too; 16.24 Create a user control to animate a picture; 16.25 Make your bees fly around a page; 16.26 Use ItemsPanelTemplate to bind controls to a Canvas; 16.27 Congratulations! (But you're not done yet...);C# Lab Invaders; Leftovers: The top 10 things we wanted to include in this book; #1. There's so much more to Windows Store; #2. The Basics; #3. Namespaces and assemblies; #4. Use BackgroundWorker to make your WinForms responsive; #5. The Type class and GetType(); #6. Equality, IEquatable, and Equals(); #7. Using yield return to create enumerable objects; #8. Refactoring; #9. Anonymous types, anonymous methods, and lambda expressions; #10. LINQ to XML; Did you know that C# and the .NET Framework can...; Windows Presentation Foundation: WPF Learner's Guide to Head First C#; Why you should learn WPF; Build WPF projects in Visual Studio; How to use this appendix; Chapter 1; Chapter 2; Chapter 10; Chapter 11; Chapter 12; Chapter 14; Chapter 15; Chapter 16;