Books recommendations please

[John]

Hi

I need to develop winform database applications and wondering is these two
books will get me there;

Data Binding with Windows Forms 2.0: Programming Smart Client Data
Applications with .Net
http://www.amazon.co.uk/Data-Bindin...TF8&coliid=I2L84GECRS6E6P&colid=399925I1FY0N8

Windows Forms 2.0 Programming
http://www.amazon.co.uk/Windows-For...TF8&coliid=I1RY8RDOG4LBP1&colid=399925I1FY0N8

I already have Bill's 'Hitchhiker's guide to VS and SQL Server'.

Any additional recommendations would be appreciated too. Basically anything
that will get me off your backs.

Thanks

Regards

 

[cfps.Christian]

Didn't notice you cross posting this in the C# group, but these books
are both in C#.

So if you can't interpret C# to VB then I would recommend finding a
different book. So far I have not found a book that truly explains
how to program, the problem I've found is the authors generally treat
you as if you know nothing at all and you don't learn what you need to
know or the author assumes you know too much and you can't do what
they're showing you due to missing steps.

I personally enjoyed the wrox C# book and the VB one should be good as
well.
http://www.amazon.co.uk/Beginning-V...=sr_1_5?ie=UTF8&s=books&qid=1208801576&sr=1-5

 

[Mr. Arnold]

Any additional recommendations would be appreciated too. Basically
anything that will get me off your backs.

MODEL-VIEW-PRESENTER

http://www.polymorphicpodcast.com/

click 'Shows'

click 'Design Patterns Bootcamp: Model View * Patterns*

view parts 1-5

You can use Google to get more information about this or find books.

 

[Cor Ligthert[MVP]]

I've found is the authors generally treat
you as if you know nothing at all and you don't learn what you need to
know or the author assumes you know too much and you can't do what
they're showing you due to missing steps.

I don't know if you are married, but then does your wife always do what you
think that she should do?

What do you expect from the writters, make books which learns everybody what
they don't know yet and make that book after reading without sense?

In fact is that the complete problem, we don't have brainconnectors.
(Except Herfried of course).

Cor

 

[Cowboy \(Gregory A. Beamer\)]

So far I have not found a book that truly explains
how to program, the problem I've found is the authors generally treat
you as if you know nothing at all and you don't learn what you need to
know or the author assumes you know too much and you can't do what
they're showing you due to missing steps.

It is really hard to be an author. The payscale sucks. You spend months of
your time after work putting things together. Then Microsoft changes things
on you and you have to edit the entire manuscript. Next round, you try again
on a multi-author book. Less time, but even less pay.

In addition, you have to figure out what the book publisher will want to
attempt to sell, as the title "Learn How To Truly Program ASP.NET in C#" is
less sexy than "Building Mash-Ups Using ASP.NET MVC".

To further compound this, suppose you try an advanced book, but make sure
you cover the basics? You get bashed by the advanced guys, who feel you are
insulting your intelligence. In addition, you have just added a plethora of
pages to your plate, which take time to write, debug, etc.

Perhaps, you go the route of creating a complete application and surrounding
it with a book. If you do this correctly, you spend a month designing the
application before starting the book. That does not work, as the publisher
wants pages now. So, you write an app on the fly. Oops! Readers tag you for
not following standards, so your book sales suck.

In all reality, the only way to make any money or reputation off a book is
to tag upcoming, new and sexy technology and get the first book out there.
This generally gives the author about 18-24 weeks to complete the project.
And, in most cases, he is writing an intermediate book that assumes you know
the basics. It sucks, yes, but it is the nature of the publishing business
right now, as that is what is going to sell.

This means you, as the reader, generally have to choose between a book that
assumes you already know programming and want to learn the new X technology
or you have to pick up a beginner's book: "Step by Step", for example.

Should there be a book out there that fits more sizes? Possibly, but it is
generally either a) too time consuming or b) too niched. Either are a death
sentence for a book.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

Subscribe to my blog
http://gregorybeamer.spaces.live.com/lists/feed.rss

or just read it:
http://gregorybeamer.spaces.live.com/

*************************************************
| Think outside the box!
|
*************************************************