|
|
| Book details / order |
| HEAD FIRST C#, 3RD EDITION A LEARNER'S GUIDE TO REAL-WORLD PROGRAMMING WITH C#, XAML, AND .NET |
Head first c# is a complete learning experience for learning how to program with c#, xaml, the .net framework, and visual studio. fun and highly visual, this introduction to c# is designed to keep you engaged and entertained from first page to last.
you’ll build a fully functional video game in the opening chapter, and then learn how to use classes and object-oriented programming, draw graphics and animation, and query data with linq and serialize it to files. and you'll do it all by creating games, solving puzzles, and doing hands-on projects. by the time you're done, you'll be a solid c# programmer and you'll have a great time along the way!
create a fun arcade game in the first chapter, and build games and other projects throughout the book
learn how to use xaml to design attractive and interactive pages and windows
build modern windows store apps using the latest microsoft technology
learn wpf (windows presentation foundation) using the downloadable wpf learner's guide
using the model-view-viewmodel (mvvm) pattern to create robust architecture
build a bonus windows phone project and run it in the visual studio windows phone emulator
projects in the book work with all editions of visual studio, including the free express editions.
about the author
bestselling o'reilly authors jennifer greene and andrew stellman have been building software and writing about software engineering together since they first met in 1998. their first book, applied software project management, was published by o’reilly in 2005. other stellman and greene books for o’reilly include beautiful teams (2009), and their first book in the head first series, head first pmp (2007). they founded stellman & greene consulting in 2003 to build a really neat software project for scientists studying herbicide exposure in vietnam vets. in addition to building software and writing books, they’ve provided training and consulted for companies and spoken at conferences and meetings of software engineers, architects and project managers.
jenny studied philosophy in college but, like everyone else in the field, couldn’t find a job doing it. luckily, she’s a great software engineer, so she started out working at an online service, and that’s the first time she really got a good sense of what good software development looked like. she moved to new york in 1998 to work on software quality at a financial software company. she’s managed a teams of developers, testers and pms on software projects in media and finance since then. she’s traveled all over the world to work with different software teams and build all kinds of cool projects.
andrew stellman, despite being raised a new yorker, has lived in minneapolis, geneva, and pittsburgh... twice. the first time was when he graduated from carnegie mellon’s school of computer science, and then again when he and jenny were starting their consulting business and writing their first book for o’reilly. he and jenny first worked together at a company on wall street that built financial software, where he was managing a team of programmers. over the years he’s been a vice president at a major investment bank, architected large-scale real-time back end systems, managed large international software teams, and consulted for companies, schools, and organizations, including microsoft, the national bureau of economic research, and mit. he’s had the privilege working with some pretty amazing programmers during that time, and likes to think that he’s learned a few things from them.
chapter 1 start building with c#: build something cool, fast!
why you should learn c#
c# and the visual studio ide make lots of things easy
what you do in visual studio...
what visual studio does for you...
aliens attack!
only you can help save the earth
here’s what you’re going to build
start with a blank application
set up the grid for your page
add controls to your grid
use properties to change how the controls look
controls make the game work
you’ve set the stage for the game
what you’ll do next
add a method that does something
fill in the code for your method
finish the method and run your program
here’s what you’ve done so far
add timers to manage the gameplay
make the start button work
run the program to see your progress
add code to make your controls interact with the player
dragging humans onto enemies ends the game
your game is now playable
make your enemies look like aliens
add a splash screen and a tile
publish your app
use the remote debugger to sideload your app
start remote debugging
chapter 2 it’s all just code: under the hood
when you’re doing this...
...the ide does this
where programs come from
the ide helps you code
anatomy of a program
two classes can be in the same namespace
your programs use variables to work with data
c# uses familiar math symbols
use the debugger to see your variables change
loops perform an action over and over
if/else statements make decisions
build an app from the ground up
make each button do something
set up conditions and see if they’re true
windows desktop apps are easy to build
rebuild your app for windows desktop
your desktop app knows where to start
you can change your program’s entry point
when you change things in the ide, you’re also changing your code
chapter 3 objects: get oriented!: making code make sense
how mike thinks about his problems
how mike’s car navigation system thinks about his problems
mike’s navigator class has methods to set and modify routes
use what you’ve learned to build a program that uses a class
mike gets an idea
mike can use objects to solve his problem
you use a class to build an object
when you create a new object from a class, it’s called an instance of that class
a better solution...brought to you by objects!
an instance uses fields to keep track of things
let’s create some instances!
thanks for the memory
what’s on your program’s mind
you can use class and method names to make your code intuitive
give your classes a natural structure
class diagrams help you organize your classes so they make sense
build a class to work with some guys
create a project for your guys
build a form to interact with the guys
there’s an easier way to initialize objects
a few ideas for designing intuitive classes
chapter 4 types and references: it’s 10:00. do you know where your data is?
the variable’s type determines what kind of data it can store
a variable is like a data to-go cup
10 pounds of data in a 5-pound bag
even when a number is the right size, you can’t just assign it to any variable
when you cast a value that’s too big, c# will adjust it automatically
c# does some casting automatically
when you call a method, the arguments must be compatible with the types of the parameters
debug the mileage calculator
combining = with an operator
objects use variables, too
refer to your objects with reference variables
references are like labels for your object
if there aren’t any more references, your object gets garbage-collected
multiple references and their side effects
two references means two ways to change an object’s data
a special case: arrays
arrays can contain a bunch of reference variables, too
welcome to sloppy joe’s budget house o’ discount sandwiches!
objects use references to talk to each other
where no object has gone before
build a typing game
controls are objects, just like any other object
c# lab: a day at the races
chapter 5 encapsulation: keep your privates... private
kathleen is an event planner
what does the estimator do?
you’re going to build a program for kathleen
kathleen’s test drive
each option should be calculated individually
it’s easy to accidentally misuse your objects
encapsulation means keeping some of the data in a class private
use encapsulation to control access to your class’s methods and fields
but is the realname field really protected?
private fields and methods can only be accessed from inside the class
a few ideas for encapsulating classes
encapsulation keeps your data pristine
properties make encapsulation easier
build an application to test the farmer class
use automatic properties to finish the class
what if we want to change the feed multiplier?
use a constructor to initialize private fields
chapter 6 inheritance: your object’s family tree
kathleen does birthday parties, too
we need a birthdayparty class
build the party planner version 2.0
one more thing...can you add a $100 fee for parties over 12?
when your classes use inheritance, you only need to write your code once
build up your class model by starting general and getting more specific
how would you design a zoo simulator?
use inheritance to avoid duplicate code in subclasses
different animals make different noises
think about how to group the animals
create the class hierarchy
every subclass extends its base class
use a colon to inherit from a base class
we know that inheritance adds the base class fields, properties, and methods to the subclass...
a subclass can override methods to change or replace methods it inherited
any place where you can use a base class, you can use one of its subclasses instead
a subclass can hide methods in the superclass
use the override and virtual keywords to inherit behavior
a subclass can access its base class using the base keyword
when a base class has a constructor, your subclass needs one, too
now you’re ready to finish the job for kathleen!
build a beehive management system
how you’ll build the beehive management system
use inheritance to extend the bee management system
chapter 7 interfaces and abstract classes: making classes keep their promises
let’s get back to bee-sics
we can use inheritance to create classes for different types of bees
an interface tells a class that it must implement certain methods and properties
use the interface keyword to define an interface
now you can create an instance of nectarstinger that does both jobs
classes that implement interfaces have to include all of the interface’s methods
get a little practice using interfaces
you can’t instantiate an interface, but you can reference an interface
interface references work just like object references
you can find out if a class implements a certain interface with “is”
interfaces can inherit from other interfaces
the robobee 4000 can do a worker bee’s job without using valuable honey
is tells you what an object implements; as tells the compiler how to treat your object
a coffeemaker is also an appliance
upcasting works with both objects and interfaces
downcasting lets you turn your appliance back into a coffee maker
upcasting and downcasting work with interfaces, too
there’s more than just public and private
access modifiers change visibility
some classes should never be instantiated
an abstract class is like a cross between a class and an interface
like we said, some classes should never be instantiated
an abstract method doesn’t have a body
the deadly diamond of death!
polymorphism means that one object can take many different forms
chapter 8 enums and collections: storing lots of data
strings don’t always work for storing categories of data
enums let you work with a set of valid values
enums let you represent numbers with names
we could use an array to create a deck of cards...
arrays are hard to work with
lists make it easy to store collections of...anything
lists are more flexible than arrays
lists shrink and grow dynamically
generics can store any type
collection initializers are similar to object initializers
let’s create a list of ducks
lists are easy, but sorting can be tricky
icomparable helps your list sort its ducks
use icomparer to tell your list how to sort
create an instance of your comparer object
icomparer can do complex comparisons
overriding a tostring() method lets an object describe itself
update your foreach loops to let your ducks and cards print themselves
you can upcast an entire list using ienumerable
you can build your own overloaded methods
use a dictionary to store keys and values
the dictionary functionality rundown
build a program that uses a dictionary
and yet more collection types...
a queue is fifo—first in, first out
a stack is lifo—last in, first out
chapter 9 reading and writing files: save the last byte for me!
.net uses streams to read and write data
different streams read and write different things
a filestream reads and writes bytes to a file
write text to a file in three simple steps
the swindler launches another diabolical plan
reading and writing using two objects
data can go through more than one stream
use built-in objects to pop up standard dialog boxes
dialog boxes are just another winforms control
dialog boxes are objects, too
use the built-in file and directory classes to work with files and directories
use file dialogs to open and save files (all with just a few lines of code)
idisposable makes sure your objects are disposed of properly
avoid filesystem errors with using statements
trouble at work
writing files usually involves making a lot of decisions
use a switch statement to choose the right option
use a switch statement to let your deck of cards read from a file or write itself out to one
add an overloaded deck() constructor that reads a deck of cards in from a file
what happens to an object when it’s serialized?
but what exactly is an object’s state? what needs to be saved?
when an object is serialized, all of the objects it refers to get serialized, too...
serialization lets you read or write a whole object graph all at once
if you want your class to be serializable, mark it with the [serializable] attribute
let’s serialize and deserialize a deck of cards
.net uses unicode to store characters and text
c# can use byte arrays to move data around
use a binarywriter to write binary data
you can read and write serialized files manually, too
find where the files differ, and use that information to alter them
working with binary files can be tricky
use file streams to build a hex dumper
streamreader and streamwriter will do just fine (for now)
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
brian’s running windows 8
windows forms use an object graph set up by the ide
use the ide to explore the object graph
windows store apps use xaml to create ui objects
redesign the go fish! form as a windows store app page
page layout starts with controls
rows and columns can resize to match the page size
use the grid system to lay out app pages
data binding connects your xaml pages to your classes
xaml controls can contain text...and more
use data binding to build sloppy joe a better menu
use static resources to declare your objects in xaml
use a data template to display objects
inotifypropertychanged lets bound objects send updates
modify menumaker to notify you when the generateddate property changes
chapter 11 async, await, and data contract serialization: pardon the interruption
brian runs into file trouble
windows store apps use await to be more responsive
use the fileio class to read and write files
build a slightly less simple text editor
a data contract is an abstract definition of your object’s data
use async methods to find and open files
knownfolders helps you access high-profile folders
the whole object graph is serialized to xml
stream some guy objects to your app’s local folder
take your guy serializer for a test drive
use a task to call one async method from another
build brian a new excuse manager app
separate the page, excuse, and excuse manager
create the main page for the excuse manager
add the app bar to the main page
build the excusemanager class
add the code-behind for the page
chapter 12 exception handling: putting out fires gets old
brian needs his excuses to be mobile
brian’s code did something unexpected
all exception objects inherit from exception
the debugger helps you track down and prevent exceptions in your code
use the ide’s debugger to ferret out exactly what went wrong in the excuse manager
uh oh—the code’s still got problems...
handle exceptions with try and catch
what happens when a method you want to call is risky?
use the debugger to follow the try/catch flow
if you have code that always should run, use a finally block
use the exception object to get information about the problem
use more than one catch block to handle multiple types of exceptions
one class throws an exception that a method in another class can catch
bees need an outofhoney exception
an easy way to avoid a lot of problems: using gives you try and finally for free
exception avoidance: implement idisposable to do your own cleanup
the worst catch block ever: catch-all plus comments
temporary solutions are ok (temporarily)
a few simple ideas for exception handling
brian finally gets his vacation...
chapter 13 captain amazing the death of the object
your last chance to do something...your object’s finalizer
when exactly does a finalizer run?
dispose() works with using; finalizers work with garbage collection
finalizers can’t depend on stability
make an object serialize itself in its dispose()
a struct looks like an object...
...but isn’t an object
values get copied; references get assigned
structs are value types; objects are reference types
the stack vs. the heap: more on memory
use out parameters to make a method return more than one value
pass by reference using the ref modifier
use optional parameters to set default values
use nullable types when you need nonexistent values
nullable types help you make your programs more robust
“captain” amazing...not so much
extension methods add new behavior to existing classes
extending a fundamental type: string
chapter 14 querying data and building apps with linq: get control of your data
jimmy’s a captain amazing super-fan...
...but his collection’s all over the place
linq can pull data from multiple sources
.net collections are already set up for linq
linq makes queries easy
linq is simple, but your queries don’t have to be
jimmy could use some help
start building jimmy an app
use the new keyword to create anonymous types
linq is versatile
add the new queries to jimmy’s app
linq can combine your results into groups
combine jimmy’s values into groups
use join to combine two collections into one sequence
jimmy saved a bunch of dough
use semantic zoom to navigate your data
add semantic zoom to jimmy’s app
you made jimmy’s day
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
ever wish your objects could think for themselves?
but how does an object know to respond?
when an event occurs...objects listen
one object raises its event, others listen for it...
then, the other objects handle the event
connecting the dots
the ide generates event handlers for you automatically
generic eventhandlers let you define your own event types
windows forms use many different events
one event, multiple handlers
windows store apps use events for process lifetime management
add process lifetime management to jimmy’s comics
xaml controls use routed events
create an app to explore routed events
connecting event senders with event listeners
a delegate stands in for an actual method
delegates in action
an object can subscribe to an event...
use a callback to control who’s listening
a callback is just a way to use delegates
you can use callbacks with messagedialog commands
use delegates to use the windows settings charm
chapter 16 architecting apps with the mvvm pattern: great apps on the inside and outside
the head first basketball conference needs an app
but can they agree on how to build it?
do you design for binding or for working with data?
mvvm lets you design for binding and data
use the mvvm pattern to start building the basketball roster app
user controls let you create your own controls
the ref needs a stopwatch
mvvm means thinking about the state of the app
start building the stopwatch app’s model
events alert the rest of the app to state changes
build the view for a simple stopwatch
add the stopwatch viewmodel
finish the stopwatch app
converters automatically convert values for binding
converters can work with many different types
a style alters the appearance of a type of control
visual states make controls respond to changes
use doubleanimation to animate double values
use object animations to animate object values
build an analog stopwatch using the same viewmodel
ui controls can be instantiated with c# code, too
c# can build “real” animations, too
create a user control to animate a picture
make your bees fly around a page
use itemspaneltemplate to bind controls to a canvas
congratulations! (but you’re not done yet...)
c# lab: invaders
chapter 17 bonus project!: build a windows phone app
bee attack!
before you begin...
appendix leftovers: the top 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
#11. windows presentation foundation
did you know that c# and the .net framework can...
Author : Andrew stellman, jennifer greene
Publication : Oreilly
Isbn : 9789351103530
Store book number : 105
NRS 1400.00
|
 |
|
|
|
|
|
|
|
| |
|
|
