Books for windows applications using C#

[Guest]

Hi All

I am a newbie to C# .I am currently developing windows application.Can anyone suggest good books or links for developing Windows Applications using C#.

 

[Patrick de Ridder]

On forms: MacDonald M. (2002) User interfaces in C#, Springer Verlag. Inc,
New York, NY, ISBN 1-59059-045-7
You will need a good introductory book as well. Liberty J. (2002) Learning
C#, O'Rreily, Cambridge etc, ISBN 0-596-00376-5

Don't buy a Deitel & Deitel book
Don't buy Joseph Mayo's C# Unleashed
Don't buy Erik Brown's Wndows Forms
They are a waste of money and time

Patrick de Ridder.

Hi All:

I am a newbie to C# .I am currently developing windows application.Can

anyone suggest good books or links for developing Windows Applications using
C#.

 

[Max Power]

Hi All:

I am a newbie to C# .I am currently developing windows application.Can
anyone suggest good books or links for developing Windows Applications
using C#.

The best that I have found is Windows Forms Programming in C# by Chris
Sells. The book Professional C# from Wrox is good too.

 

[Mark Broadbent]

I have to concur with this. Im currently working my way thru it and it is
very good.
Might I also suggest that (if you havent already done so) it is very useful
to first read up on the concepts and basics of the C# language itself since
I have found when going through this book that they can be very helpful in
understanding some of the WinForms methodologies e.g. adding controls to the
forms controls collection.

The best C# reference book Ive read so far if relatively old but called C#
The Complete Reference -by Herbert Shildt. Its the dogs b*******

and for Win Forms it has got to be Chris Sells' effort.

--

--

Br,
Mark Broadbent
mcdba , mcse+i
=============

 

[Mark Broadbent]

Max just on the off chance, since you bought Chris' book, just wondered
whether you bought Anders' book too (since they both were published around
the same time). If so is it any good?

--

--

Br,
Mark Broadbent
mcdba , mcse+i
=============

 

[Brad Williams]

You will need a good introductory book as well. Liberty J. (2002) Learning
C#, O'Rreily, Cambridge etc, ISBN 0-596-00376-5

I certainly wouldn't recommend Learning C# to anyone, newbie or not, it's a
slog that found it's way to my trash can. A Programmer's Introduction to C#
or C# Programmer's Reference are good fast intros to the language for anyone
who has some programming sense.

Brad Williams

 

[Roy Fine]

the Anders' is just a formatted reprint of the C# Language Specification
from MSDN.

If you like hard-copy, it's a great resource --

regards
roy fine

 

[Patrick de Ridder]

Hi Brad,

Well, that is really intelligent comment you have given.
The best choice of a textbook obviously depends on
prior experience and on how bright you are. I have
compared Learning C# (O'Reilly) with three other
textbooks on C#, and Learning C# covers the grounds
pretty well. The only thing that is missing, is some verbal
diarrhoea. So if it's is a lot of words you want, indeed,
chuck Learning C# it in the garbage can and spend a
lot of money on a book with half a million pages, there are
enough of them around.

Patrick.

 

[Julian Nicholls]

If you are serious about Schildt's book being good then he must have got a
clue very recently because almost all his C++ books are the worst kind of
garbage.

(see knowledgeable reviews here:
http://www.accu.org/bookreviews/public/reviews/0au/s.htm)

There is also a list of C# books reviewed at the same site.
http://www.accu.org/bookreviews/public/reviews/0ti/cs.htm

Best Regards
Julian N.

 

[Brad Williams]

Hi Brad,

Well, that is really intelligent comment you have given.

Um, there *is* actually some reasoning in my post (you know what "slog"
means?), whereas your first post amounted to "this good; these bad"!

Let me spell it out: Learning C# is a great book for learning C# ... for
the kind of person who should not be programming in the first place. It
contains too much verbose hand-holding for too long, and much of the
hand-holding is out-of-order (OO is discussed in chapter 3, if I remember,
and classes are introduced in chapter 8!) or downright confusing (the worst
explanation of delegates I have seen in print).

I bet any worthy beginner would be better off going straight to Liberty's
Professional C#, which gets great reviews though I haven't touched it. And
any professional programmer worth his or her salary can pick up the language
very quickly with A Programmer's Introduction to C#.

Brad Williams

 

[Patrick de Ridder]

Hi Brad,

I responded to a question about a good
initial C# book to read, just that, no more.
Apart from books that are a waste of
money, good / bad is rather personal.
It depends on how you study, your
experience, what your capabilities and
aptitudes are. I maintain that Jesse Liberty's
book - on average - is ok for starters.

Patrick.

 

[Mark Broadbent]

very surprised you said that. As far as the C# one goes it was the first
programming book (with exception of one VB one I read ..I think called Pure
VB) that explained and answered the questions and methodologies the way I
wanted them explained -but maybe thats just me.
As far as his c++ ones are concerned, I did a search on Amazon (.co.uk)
several days ago and a could have sworn that most of the comments were
excellent. I suppose what is good for one does not necessarily cut the
mustard for another.

--

--

Br,
Mark Broadbent
mcdba , mcse+i
=============

 

[Mark Broadbent]

personally I believe that there is not enough hand holding when learning and
reading up on languages. Too many times have I jumped almost straight in to
things as do most people. Once the basics have been learnt i.e. declaration,
logic control etc it is all too easy to start writing programs (and they are
usually very poorly written). This time with C# I decided to learn all the
methodologies from the ground up, not through trial and error and am
constantly being surprised how many wrong things I did in the past
(particularly with OOP).

Whether this puts me in the category of being "for the kind of person who
should not be programming in the first place" that's not for me to judge,
but I know when I am doing something correctly or poorly now -which is a
major improvement than before
--

--

Br,
Mark Broadbent
mcdba , mcse+i
=============

 

[Mark Broadbent]

Ah right thanks - thought it was slightly more than that. I'll stick with my
"soft" copy specification doc for now and use my pennies down the pub ;-D

Thanks
--

--

Br,
Mark Broadbent
mcdba , mcse+i
=============

 

[Joerg Jooss]

On forms: MacDonald M. (2002) User interfaces in C#, Springer Verlag.
Inc, New York, NY, ISBN 1-59059-045-7
You will need a good introductory book as well. Liberty J. (2002)
Learning C#, O'Rreily, Cambridge etc, ISBN 0-596-00376-5

Don't buy a Deitel & Deitel book
Don't buy Joseph Mayo's C# Unleashed
Don't buy Erik Brown's Wndows Forms
They are a waste of money and time

YMMV. I liked Erik Brown's book, and I think it's well suited for beginners.

Cheers,

 

[Gary Morris]

Hey, I learned from trial and error. One of the best pieces of advice I
ever got was "break down tasks as much as possible. You will soon
learn what OOP is about". And I did that with one of the first REAL
applications I ever programmed. It was a fairly simple application,
but it did me worlds of good, and I used (almost exclusively) the MSDN
docs that come with the SDK and framework. Now, I still have read
only two or three small books on the framework itself, NOT C# or VB.
Again, that did me worlds of good. There is no teacher like yourself!

Hi All:

I am a newbie to C# .I am currently developing windows application.Can

anyone suggest good books or links for developing Windows Applications using
C#.

 

[Scott]

usually very poorly written). This time with C# I decided to learn all the

methodologies from the ground up, not through trial and error and am
constantly being surprised how many wrong things I did in the past
(particularly with OOP).

I went through a similar realization while reading Programming .Net
Components by Juval Lowy. He tells you why .Net isn't really designed for
using OOP and how to use component based programming as .Net was designed
for. If what I'm saying sounds strange, I highly recommend Lowy's book.

Scott