Book recomendation?

[Scott Metzger]

Hi,

I am looking for a good book on C# and dot net.

I have 10 yrs programming experience. Mostly with C++, databases, and
GUI front ends in windows.
I don't have alot of money to buy a whole bunch of different books; nor
do I have alot of time to read a whole bunch of different books. So, I
am looking for one good tutorial book that will get me up and running
quickly. Any recommendations?

Thanks,
Scott Metzger

[Gawelek]

> Hi,

I am looking for a good book on C# and dot net.

I have 10 yrs programming experience. Mostly with C++, databases, and
GUI front ends in windows.
I don't have alot of money to buy a whole bunch of different books; nor
do I have alot of time to read a whole bunch of different books. So, I
am looking for one good tutorial book that will get me up and running
quickly. Any recommendations?

Andrew Troelsen, The best author, according to me.

Gawel

[Chris Tacke, eMVP]

I highly recommend Wrox's Beginning C# book

--
Chris Tacke, eMVP
Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

"Scott Metzger" <NO*****************@york.com> wrote in message
news:3F**************@york.com...

Hi,

I am looking for a good book on C# and dot net.

I have 10 yrs programming experience. Mostly with C++, databases, and
GUI front ends in windows.
I don't have alot of money to buy a whole bunch of different books; nor
do I have alot of time to read a whole bunch of different books. So, I
am looking for one good tutorial book that will get me up and running
quickly. Any recommendations?

Thanks,
Scott Metzger

[Martin Wallgren]

> I am looking for a good book on C# and dot net.

[snip snip]
Any recommendations?

I have the book C# Complete from Sybex, only $24.99 (says so on the
cover). About 1000 pages with samples how to use C#. Fairly good, I use
it as a reference.

http://www.amazon.com/exec/obidos/tg...217090-5542220
---
Martin

[Scott Metzger]

Thanks everyone, I have Andrew Troelsen's book on order. I am sure I'll
be back to post questions once I get started.

Thanks,
Scott Metzger

[Stu Banter]

Before you buy anything else, just try Kazaa (Klite, Kplusplus), search
documents for Csharp and download some ebooks for a quick peek and then be
good and buy the one that meets your needs best. Searching C# won't help you
much unfortunately, it yields anything with C in it... :)

Have a ball!

Quite some stuff to be found.....
"Scott Metzger" <NO*****************@york.com> wrote in message
news:3F**************@york.com...

Hi,

I am looking for a good book on C# and dot net.

I have 10 yrs programming experience. Mostly with C++, databases, and
GUI front ends in windows.
I don't have alot of money to buy a whole bunch of different books; nor
do I have alot of time to read a whole bunch of different books. So, I
am looking for one good tutorial book that will get me up and running
quickly. Any recommendations?

Thanks,
Scott Metzger

[warren]

If programming newbie, recommend Deitel book: C# how to program.

If already very familiar or have some knowledge with C/C# and Java,
C# is easy to pick up by reading the tutorial in MSDN alone.
Afterall, i regard C# as a combination of these 3 languages, mostly.

"Scott Metzger" <NO*****************@york.com> wrote in message
news:3F**************@york.com...

Thanks everyone, I have Andrew Troelsen's book on order. I am sure I'll
be back to post questions once I get started.

Thanks,
Scott Metzger

[Jesse Liberty]

There are a number of good ways to go about finding a good book on C# and
..NET. Of course, nothing substitutes for going to a large technical book
store and reading through a few candidate primers. Each of us write
differently, with a different emphasis and a different set of priorities.
You'll want to ask yourself a few questions while examining the various
candidates:

Do you like the author's writing style? Is it clear, easy to understand?
Will the author leave you with questions or does the author anticipate your
areas of confusion? Are you the target audience?

Are there enough (too few? too many?) examples? Are the examples simple and
clear? Is the complete source code provided so that you can try the program
yourself? Is there a web site with source code you can download? Every book,
no matter how carefully edited has errors. Is there an errata sheet you can
access on the web?

You want to be sure the C# book you buy is targeted at the current version
of C# (1.1)

I hope you will consider my book, Programming C# 3rd Edition (O'Reilly).
Programming C# is divided into three parts: Part I teaches the language,
Part II shows you how to build Windows and web applications as well as web
services and Part III explores the .NET framework.

It is my goal to provide a smooth transition from other programming
languages (notably C++, Java and VB) to C#. I did not set out to reproduce
the Microsoft documentation; but rather to tell the story of C# and how C#
is used to produce applications in .NET.

I provide extensive support for my books on my web site
(http://www.LibertyAssociates.com) where you will find a sample chapter,
Table of Contents and Index and where you can buy the book at a 30%
discount. You will also find that my site provides the complete source code,
a link to the errata, and a FAQ. Finally, I offer a private support
discussion center for questions that arise while reading my books.

Thanks and best of luck.

-j
--
Jesse Liberty, President
Liberty Associates, Inc.
http://www.LibertyAssociates.com
"Scott Metzger" <NO*****************@york.com> wrote in message
news:3F**************@york.com...

Hi,

I am looking for a good book on C# and dot net.

[Alvin Bruney]

are you the same liberty for programming C#, asp.net?
"Jesse Liberty" <jl******@libertyassociates.com> wrote in message
news:uD**************@TK2MSFTNGP09.phx.gbl...

There are a number of good ways to go about finding a good book on C# and
.NET. Of course, nothing substitutes for going to a large technical book
store and reading through a few candidate primers. Each of us write
differently, with a different emphasis and a different set of priorities.
You'll want to ask yourself a few questions while examining the various
candidates:

Do you like the author's writing style? Is it clear, easy to understand?
Will the author leave you with questions or does the author anticipate your areas of confusion? Are you the target audience?

Are there enough (too few? too many?) examples? Are the examples simple and clear? Is the complete source code provided so that you can try the program yourself? Is there a web site with source code you can download? Every book, no matter how carefully edited has errors. Is there an errata sheet you can access on the web?

You want to be sure the C# book you buy is targeted at the current version
of C# (1.1)

I hope you will consider my book, Programming C# 3rd Edition (O'Reilly).
Programming C# is divided into three parts: Part I teaches the language,
Part II shows you how to build Windows and web applications as well as web
services and Part III explores the .NET framework.

It is my goal to provide a smooth transition from other programming
languages (notably C++, Java and VB) to C#. I did not set out to reproduce
the Microsoft documentation; but rather to tell the story of C# and how C#
is used to produce applications in .NET.

I provide extensive support for my books on my web site
(http://www.LibertyAssociates.com) where you will find a sample chapter,
Table of Contents and Index and where you can buy the book at a 30%
discount. You will also find that my site provides the complete source code, a link to the errata, and a FAQ. Finally, I offer a private support
discussion center for questions that arise while reading my books.

Thanks and best of luck.

-j
--
Jesse Liberty, President
Liberty Associates, Inc.
http://www.LibertyAssociates.com
"Scott Metzger" <NO*****************@york.com> wrote in message
news:3F**************@york.com...

Hi,

I am looking for a good book on C# and dot net.

[Jesse Liberty]

Yes, as I say in the note you quoted, I wrote Programming C# and also a
number of other books.

Thanks.

-j

--
Jesse Liberty, President
Liberty Associates, Inc.
http://www.LibertyAssociates.com
"Alvin Bruney" <vapordan_spam_me_not@hotmail_no_spamhotmail.com > wrote in
message news:OI**************@TK2MSFTNGP10.phx.gbl...

are you the same liberty for programming C#, asp.net?

[Alvin Bruney]

i'd like to welcome you officially tehehehe
"Jesse Liberty" <jl******@libertyassociates.com> wrote in message
news:OS**************@TK2MSFTNGP09.phx.gbl...

Yes, as I say in the note you quoted, I wrote Programming C# and also a
number of other books.

Thanks.

-j

--
Jesse Liberty, President
Liberty Associates, Inc.
http://www.LibertyAssociates.com
"Alvin Bruney" <vapordan_spam_me_not@hotmail_no_spamhotmail.com > wrote in
message news:OI**************@TK2MSFTNGP10.phx.gbl...

are you the same liberty for programming C#, asp.net?

[mitch]

I recommend using Microsoft C# .net Core Refrence or Microsoft C# step by step.

Those two books have been pretty helpful to me.

[Jon Skeet [C# MVP]]

Jesse Liberty <jl******@libertyassociates.com> wrote:

There are a number of good ways to go about finding a good book on C# and
.NET. Of course, nothing substitutes for going to a large technical book
store and reading through a few candidate primers.

<snip>

Personally, I think of a few bits that I know about but which are often
misrepresented, and have a look for them. For instance, the first thing
I do is check whether or not the author claims that "objects are passed
by reference". If so, that's one strike. Seeing how well they can
describe the differences between reference types and value types is
another. I then often have a look at the GUI stuff - I don't know much
about GUI stuff, but when I want to know about it in detail, I'll want
to know about the details, not just how to drag things from one place
to another in VS.NET.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Jesse Liberty]

I won't argue the point with you (it becomes a matter of religion) but
depending on the audience, I often say that "objects are passed by
reference."

Yes, everything in C# is passed by value, and yes a copy of a reference to
the unnamed object in memory is passed, but that creates the semantics of
pass by reference and the effect is (nearly all the time) identical. The
distinction should be covered in a note, and then forgotten, as far as I'm
concerned.

Similarly, if I declare

Dog fido = new Dog("fido");

I will often refer to fido as a Dog, or as a Dog object or even as an
instance of a Dog, none of which is technically correct, because of course
fido is just a reference to an (unnamed) Dog object on the heap.

It is important in a primer to be correct, but it is also important to be
clear, and pointless legalistic distinctions often just get in the way.

Guess you'll hate my books <smile>.

-j

--
Jesse Liberty, President
Liberty Associates, Inc.
http://www.LibertyAssociates.com

Personally, I think of a few bits that I know about but which are often
misrepresented, and have a look for them. For instance, the first thing
I do is check whether or not the author claims that "objects are passed
by reference". If so, that's one strike.

[Jesse Liberty]

Thanks, but I've been hanging around this group, off and on for at least 3
years. (could it be that long?)

--
Jesse Liberty, President
Liberty Associates, Inc.
http://www.LibertyAssociates.com
"Alvin Bruney" <vapordan_spam_me_not@hotmail_no_spamhotmail.com > wrote in
message news:e6**************@TK2MSFTNGP12.phx.gbl...

i'd like to welcome you officially tehehehe

[Alvin Bruney]

yes, but then folk who read that book without the benefit of this
explanation now take up the mantra that objects are passed by reference
which isn't correct. i agree a primer shouldn't go this deep but as a matter
of nothing else but familiarity, the facts should be noted to prevent the
loss of souls.

"Jesse Liberty" <jl******@libertyassociates.com> wrote in message
news:O1**************@TK2MSFTNGP10.phx.gbl...

I won't argue the point with you (it becomes a matter of religion) but
depending on the audience, I often say that "objects are passed by
reference."

Yes, everything in C# is passed by value, and yes a copy of a reference to
the unnamed object in memory is passed, but that creates the semantics of
pass by reference and the effect is (nearly all the time) identical. The
distinction should be covered in a note, and then forgotten, as far as I'm
concerned.

Similarly, if I declare

Dog fido = new Dog("fido");

I will often refer to fido as a Dog, or as a Dog object or even as an
instance of a Dog, none of which is technically correct, because of course
fido is just a reference to an (unnamed) Dog object on the heap.

It is important in a primer to be correct, but it is also important to be
clear, and pointless legalistic distinctions often just get in the way.

Guess you'll hate my books <smile>.

-j

--
Jesse Liberty, President
Liberty Associates, Inc.
http://www.LibertyAssociates.com

Personally, I think of a few bits that I know about but which are often
misrepresented, and have a look for them. For instance, the first thing
I do is check whether or not the author claims that "objects are passed
by reference". If so, that's one strike.

[Stu Banter]

What a nice opportunity to thank you for writing it! As you may have seen
elsewhere here I have bought an older version 2nd hand, and judging the way
it looks now I bet the previous owner thoroughly used it too. A big thumbs
up from me to you!

Is there a lot of change in the 3d edition worth considering ? (I use VS
2002, .NET 1.0 still)
I'm not rich enough to buy new stuff every time unfortunately =(

Again thanks for writing a great book. And forgive me for having peeked the
e-version online first...

Best!,
Stu

[Jon Skeet [C# MVP]]

Jesse Liberty <jl******@libertyassociates.com> wrote:

I won't argue the point with you (it becomes a matter of religion) but
depending on the audience, I often say that "objects are passed by
reference."

Yes, everything in C# is passed by value, and yes a copy of a reference to
the unnamed object in memory is passed, but that creates the semantics of
pass by reference and the effect is (nearly all the time) identical. The
distinction should be covered in a note, and then forgotten, as far as I'm
concerned.
I disagree strongly (as I'm sure you'd guessed :) - I've seen lots of
people who've been confused precisely because people are inexact in
this kind of thing. You may not confuse people who don't actually know
what pass-by-reference semantics are in the first place, but you'll
certainly confuse those who do. If you really believe this inaccuracy
doesn't do any harm, I'm sure I can easily dig up a whole stack of
posts by people on both the Java and C# groups who've been confused by
this but have then been "unconfused" by the correct view. I've never
seen anyone (AFAICR) end up being confused by the correct view

It's not just that the semantics of pass-by-reference and pass-
reference-by-value are different when the parameter's value is changed
- it's that if you've got the right idea of references to start with,
passing a reference by value is actually a far more natural thing to
talk about anyway.

The difference between a reference and an object is absolutely vital to
understanding C#, and once that difference is understood, things like
assignment, parameter passing, garbage collection, reference identity
versus object equality etc are *so* much easier to understand. The idea
of passing an object by reference gets very strange when things like
nulls get involved, and certainly when you then *do* pass the reference
by reference things get even more complicated. Why choose the
complicated and technically inaccurate way of describing parameter
passing rather than the simple and technically accurate way?
Similarly, if I declare

Dog fido = new Dog("fido");

I will often refer to fido as a Dog, or as a Dog object or even as an
instance of a Dog, none of which is technically correct, because of course
fido is just a reference to an (unnamed) Dog object on the heap.
(In fact, fido is just a variable. The *value* of fido is a reference
to a Dog object on the heap. But never mind that...)

I hope that if you were talking about the topic of assignment itself,
you'd be accurate. It's okay (IMO) to be technically slightly
inaccurate when the point you're actually making is unrelated to the
technical inaccuracy. When you're actually trying to explain parameter
passing though, being inaccurate about parameter passing is a really
bad idea.
It is important in a primer to be correct, but it is also important to be
clear, and pointless legalistic distinctions often just get in the way.
Agreed - but bearing in mind the point above, I believe on this matter
it's easy to be correct *and* clear. At least, that's my experience
over the last few years of "crusading" to get this inaccuracy cleared
up - it's one of my pet peeves. Fortunately the C# books I've read have
tended to be much more accurate about this than the early Java books,
so there's less confusion out there this time around, although it still
happens.
Guess you'll hate my books <smile>.

Maybe I'll find out one of these days :)

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Jesse Liberty]

Thank you for the very kind words. If you are still using 1.0 then there is
no reason for you to go to the third edition. You can learn more about the
new book, however, and find supporting materials and a link to my private
support discussion group on my web site (
http://www.LibertyAssociates.com ) - click on books.

Thanks again.

--
Jesse Liberty, President
Liberty Associates, Inc.
http://www.LibertyAssociates.com
"Stu Banter" <x2**************@westerterp.com> wrote in message
news:3f***********************@news.xs4all.nl...

What a nice opportunity to thank you for writing it! As you may have seen
elsewhere here I have bought an older version 2nd hand, and judging the way it looks now I bet the previous owner thoroughly used it too. A big thumbs
up from me to you!

Is there a lot of change in the 3d edition worth considering ? (I use VS
2002, .NET 1.0 still)
I'm not rich enough to buy new stuff every time unfortunately =(

Again thanks for writing a great book. And forgive me for having peeked the e-version online first...

Best!,
Stu

[Jesse Liberty]

Your points are both well written and well taken. I do make the distinction
you urge in my book, I just don't get as worked up about it as you do;
though, again, I take your point.

-j

--
Jesse Liberty, President
Liberty Associates, Inc.
http://www.LibertyAssociates.com
"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message ...

I've seen lots of
people who've been confused precisely because people are inexact in
this kind of thing. ...> The difference between a reference and an object is absolutely vital to understanding C#, and once that difference is understood, things like
assignment, parameter passing, garbage collection, reference identity
versus object equality etc are *so* much easier to understand. The idea
of passing an object by reference gets very strange when things like
nulls get involved, and certainly when you then *do* pass the reference
by reference things get even more complicated. Why choose the
complicated and technically inaccurate way of describing parameter
passing rather than the simple and technically accurate way?

[Jon Skeet [C# MVP]]

Jesse Liberty <jl******@libertyassociates.com> wrote:

Your points are both well written and well taken. I do make the distinction
you urge in my book, I just don't get as worked up about it as you do;
though, again, I take your point.

Goodo. For what it's worth, I didn't used to get very worked up about
it either - but after you've answered the same question which is
inspired by bad wording in books/posts about 20 times, it's easy to get
worked up about it :)

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too