"The code in listing 1.16 issues a database request...'

References wrong listing I believe.

Jon:
Just started reading and am truly enjoying it. Love your writing style and the way you are introducing the various concepts so far is excellent. So often I see these new features in C#2 and 3 introduced in isolation (I'm looking at you Microsoft) and it just confuses people.

Really looking forward to reading the rest of it.

Cheers,
Dave

> "The code in listing 1.16 issues a database
> request...'
> References wrong listing I believe.

Good catch! I've just been revising chapters 1-3, and I still missed it. Fixed in the manuscript now, thanks very much.

> Jon:
> Just started reading and am truly enjoying it. Love
> your writing style and the way you are introducing
> the various concepts so far is excellent. So often I
> see these new features in C#2 and 3 introduced in
> isolation (I'm looking at you Microsoft) and it just
> confuses people.
>
> Really looking forward to reading the rest of it.

Cool - that's certainly what I like to hear
(I have to say though, the style changes significantly between chapters 1 and 2 and the rest of the book. Most of the time the features *are* isolated, but hopefully with enough context to make it useful

Jon

It's the little things that seem to jump out at me while at the same time I'll miss something glaring like 2+2=5

To clarify, by in isolation I mean doing things like this:

[begin example]
Here is an example of an extension method:

public static void WriteToConsole(this object o)
{
Console.WriteLine(o)
}
[end example]

I actually saw that in a Microsoft presentation.

I find that when I show people it's related to things like MyList.Where and illustrate that Where is implemented with an extension method, the lights immediately come on and there's that "Now I get it!" moment.

Here are a couple more minor things I noticed, right or wrong.

Section 1.1.5

"It’s important to understand that LINQ is flexible, too: you can write your own query translators."

Should the colon be a semi-colon?


Section 1.2.1

"the servlet API and JavaServer Pages"

Space between Java and Server. (I have no idea if there should be or not)

Section 1.2.4

"The last collection of items in this somewhat potted history is .NET 3.5, C# 3, VB9 and Visual Studio
2008. (Still to be written as they’re released…)"

Alrighty then, get to work.

Dave

<snip>

> Here are a couple more minor things I noticed, right
> or wrong.
>
> Section 1.1.5
>
> "It’s important to understand that LINQ is flexible,
> too: you can write your own query translators."
>
> Should the colon be a semi-colon?

Not really - it's explaining the manner of the flexibility.

> Section 1.2.1
>
> "the servlet API and JavaServer Pages"
>
> Space between Java and Server. (I have no idea if
> there should be or not)

Strangely enough, that *is* correct (I think I had to check at the time). See
http://java.sun.com/products/jsp/

> Section 1.2.4
>
> "The last collection of items in this somewhat potted
> history is .NET 3.5, C# 3, VB9 and Visual Studio
> 2008. (Still to be written as they’re released…)"
>
> Alrighty then, get to work.

I think I fixed that a little while ago - it's possible that the MEAP edition has just added the new chapters rather than being updated with the revisions of the old chapters.

But yes, I haven't got that kind of thing in there any more!

Jon

> I think I fixed that a little while ago - it's
> possible that the MEAP edition has just added the new
> chapters rather than being updated with the revisions
> of the old chapters.

Most likely, I am reading the latest MEAP drop that was released to me on Friday.

Into chapter 2 now and still enjoying it.

Cheers
dave