A critic of the book on Amazon.com writes:

"...the book presents a lot of bad designs. Where is the multi-tier design? Some chapters in the book show how to put those SQL queries right in aspx pages where only user interface code should be in. Some chapters show how to spit datasets out of business logics. Well it is quick, but should you want to expand or fix things, you would have to redesign and code all over again..."

"Parameterized sql query and stored procedure are so little talked about. These allow you to avoid SQL injection attacks 100% even you don't validate user inputs!"

"Consideration of performance gains and hits of their designs are not discussed at all. The book says you can spawn this and that in matter of minutes, but it doesn't tell you that you'll pay the cost later to support more visitors."

I've just purchased your book, and I can't tell whether I should be worried, or not. What is your response to these accusations? Does this person make some fair points?

Hi there,

I don't agree, but that's hardly a surprise since I wrote more than half of the book ;)

However, I don't agree for a reason. The book is not aimed at highly experienced developers. It's targeted somewhere between Beginning ASP.NET 2.0 and Professional ASP.NET 2.0

As such it features different designs that serve different people. Not everyone understands or appreciates complex, multi layer designs when they just start out with ASP.NET. For those readers, the book features a number of "flat designs" that allow you to focus on other important ASP.NET elements. If you're more experienced, you'll find other chapters that give you a more detailed look into different designs. And once you get the hang of it, you can look at chapters like the Wrox BugBase (chapter 12) for a clean separation between different layers.

In addition, many of the chapters use stored procedures to avoid SQL injection attacks (and for many other reasons). In fact, at least half of the chapters in the book use sprocs, including popular chapters like the Wrox CMS, the WebShop, the Customer Support application, the Appointment Booking application and the BugBase. It looks like the reader didn't read the second, more advanced half of the book.

So, all in all, I think you'll find a lot of useful stuff in this book. To see what other readers think about it, just browse through this book's forum.

Have fun with the book; you'll know where to go to if you need help.

Cheers,

Imar

---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004

Imar,

Thanks for the response. I'll try and apply the multi-tiered approach of the latter projects when working with the earlier projects. I appreciate that it's necessity to start slow to teach relatively inexperienced users--like me.

You're welcome.

Have fun with the book.

Imar

---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004