I have purchased a few .net books and I'm sure not as many as some of you all have, but I do have some annoying beefs with some of them.
#1. Supporting a company first, you second
Microsoft does this the most. I go to buy a book on OOP and Components and a requirement on it is SQL Server 2000! It doesn't say SQL Server 2000 or MSDE, just SQL Server 2000.
Its not a book on databases, but its an assumption that if you want to program componants or OOP in VB.Net you have a $2000 piece of software laying around.
Now at some point in this book (which uses a running example) they introduce SQL Server 2000. As its a running example, you cna't go on unless you have it. You can't skip the chapter because the next chapter built on the SQL Server 2000 stuff you just did.
It just seems like they purposefully set up the example to make it like this, so you'll need the extra software.
#2. Page Fluffing with ASP.Net
One example was the same book as above with OOP and Componants. I have a few other books like this.
I buy a book about VB.Net, a specific topic, databases, etc. Then randomly there are entire chapters on the basics of the subject and asp.net.
Why? Two reasons I can think of. First is page fluffing. Wow, its soo thick! Too bad 1/4th of it is on a subject you don't want. Second would be to get you to read the basics, then tell you "welp, there isn't enough room to cover more than the basics of ASP.Net, buy our ASP.Net book on this subject"
Every time I get one of these books, I look over at ASP.Net chapters, then over at my ASP.Net books and shake my head. I swear I have "the basics of ASP.net" enough times over that I think I could fit another 5 (hefty sized) books on the shelf if I cut out those dead weight pages.
[/Rant]
#1. Supporting a company first, you second
Microsoft does this the most. I go to buy a book on OOP and Components and a requirement on it is SQL Server 2000! It doesn't say SQL Server 2000 or MSDE, just SQL Server 2000.
Its not a book on databases, but its an assumption that if you want to program componants or OOP in VB.Net you have a $2000 piece of software laying around.
Now at some point in this book (which uses a running example) they introduce SQL Server 2000. As its a running example, you cna't go on unless you have it. You can't skip the chapter because the next chapter built on the SQL Server 2000 stuff you just did.
It just seems like they purposefully set up the example to make it like this, so you'll need the extra software.
#2. Page Fluffing with ASP.Net
One example was the same book as above with OOP and Componants. I have a few other books like this.
I buy a book about VB.Net, a specific topic, databases, etc. Then randomly there are entire chapters on the basics of the subject and asp.net.
Why? Two reasons I can think of. First is page fluffing. Wow, its soo thick! Too bad 1/4th of it is on a subject you don't want. Second would be to get you to read the basics, then tell you "welp, there isn't enough room to cover more than the basics of ASP.Net, buy our ASP.Net book on this subject"
Every time I get one of these books, I look over at ASP.Net chapters, then over at my ASP.Net books and shake my head. I swear I have "the basics of ASP.net" enough times over that I think I could fit another 5 (hefty sized) books on the shelf if I cut out those dead weight pages.
[/Rant]