ASP. Net Programmers Reference

Rating:
Summary: Incredibly Mediocre
Review: A reference? It seems like the authors don't even understand the material. Paragraphs are copied (very obviously) from the .NET framework reference, portions are marked "unavailable at the time of writing" (check the System.Web.Services.Description namespace), and the English is, in a nutshell... bad. The only good content seems to have been copied from "Professional ASP.NET" (a much better book, although with its own problems), and there are blatant omissions of important information which render some of the more technical class reference essentially useless.

If you want this book, just print out the .NET class library reference.

Rating:
Summary: Good reference, not too imaginative...
Review: But I guess a reference book really isn't the place to get imaginitive thinking.

If you want to build a very quick web application, skip to "System.Web.UI.WebControls". They're easy to use and you'll get started right away.

If you want to build a more complete web application, you need to understand the base classes better, so start in "System.Web" and "System.Web.UI", which will get you thinking a little more about code (and page) reuse.

Fairly good info on security, XML, and Web Services as well.

Rating:
Summary: Some useful information, but more errors and ommisions
Review: I bought this book because I needed an ASP.NET reference. This book seems a bit schizophrenic. Part of it is tutorial and parts are reference. I haven't used it as much as I had hoped because I have run into several major errors.

Examples

Lists System.Data.ODBC when in fact this should be

Microsoft.Data.ODBC
Also forgot to mention the part about having to download it from MS website.

Lots of errors in ADO sections in general. I have tried several pieces of code from the book that simply don't work.

I certainly don't recommend this book.

Rating:
Summary: Some useful information, but more errors and ommisions
Review: I'm afraid I'll have to call this book a failure. I feel that if I buy a "programmers reference" book it should be just that. If I go to System.Web.UI.WebControls I want to see a list off all the web controls and a concise breakdown of all the parameters of each. I don't want a story about the control and a "let's make a web page with this control" exercise. I long for the days of my C++ BIBLE.

Rating:
Summary: What ever happened to the REAL programmers reference books?
Review: I'm afraid I'll have to call this book a failure. I feel that if I buy a "programmers reference" book it should be just that. If I go to System.Web.UI.WebControls I want to see a list off all the web controls and a concise breakdown of all the parameters of each. I don't want a story about the control and a "let's make a web page with this control" exercise. I long for the days of my C++ BIBLE.

Rating:
Summary: Great dog-eared, coffee-stained reference
Review: This book is ideal for intermediate programmers developing web applications with Microsoft's Visual Studio .NET. It works best as a reference for those simply looking for ways to "make stuff work" who don't need the hand-holding of step-by-step instructions, but aren't ready for simple, austere object definitions. Using an appropriate number of examples in both C# and VB.NET, the authors have successfully put together a book that has helped my shop overcome several hurdles in the month we've been using it.
In the new .NET paradigm, ASP exists only as a descriptive name applied to collections of objects that "make stuff work" on the web. Powered by C#, VB.NET, or almost any language you chose, the .NET framework Intermediate Language and Just-In-Time compilation has made an understanding of how "classic" Active Server Pages work obsolete.

However, the name ASP seems to be maintained to provide familiarity to those of us making the transition from ASP 3.0 to "any-web-application-built-with-.NET." This book fulfils that calling by giving the right mix of definitions, examples, and background information without using excess space or time.

The majority of the chapters cover most of the collections of objects (namespaces) that give an application functionality on the web. Without question, we used these sections the most. For those of us making the transition to C# at the same time we're getting used to .NET web development, these chapters were a life-saver. They gave all the answers we couldn't find in any C# reference manual tailored specifically for the types of web applications we were creating. Since we adopted .NET a few months ago, for the first time we were able to concetrate on functionality instead of C# as a frustrating language. I'm not sure how VB 6.0 programmers will look at it, but they seem to be getting the better reference books in the marketplace so far, so it was a relief to find every example done in both C# and VB.NET.

While this book would be key for beginning .NET developers ready for more robust applications or intermediate programmers moving from another language, I suspect that advanced programmers will be disappointed. For example, XML and Mobile Devices get chapters, but they don't conatain enough information for real development. You would need to have a much better background in either subject to actually develop. However, if you had that background, these sections wouldn't tell you anything you didn't already know.

The strength of this book is not as a "front-to-back" read, but as the dog-eared, coffee-stained reference that allows an intermediate level programmer to produce web applications that work--and work well. While not an expert, I've used ASP.NET Programmer's Reference to give myself a solid base of knowledge. By the time I master the material, I'll be well-prepared to tackle some of the more obscure .NET namespaces and cutting edge web technologies. ---Reviewed By Jay L.

Rating:
Summary: Great dog-eared, coffee-stained reference
Review: This book is ideal for intermediate programmers developing web applications with Microsoft's Visual Studio .NET. It works best as a reference for those simply looking for ways to "make stuff work" who don't need the hand-holding of step-by-step instructions, but aren't ready for simple, austere object definitions. Using an appropriate number of examples in both C# and VB.NET, the authors have successfully put together a book that has helped my shop overcome several hurdles in the month we've been using it.
In the new .NET paradigm, ASP exists only as a descriptive name applied to collections of objects that "make stuff work" on the web. Powered by C#, VB.NET, or almost any language you chose, the .NET framework Intermediate Language and Just-In-Time compilation has made an understanding of how "classic" Active Server Pages work obsolete.

However, the name ASP seems to be maintained to provide familiarity to those of us making the transition from ASP 3.0 to "any-web-application-built-with-.NET." This book fulfils that calling by giving the right mix of definitions, examples, and background information without using excess space or time.

The majority of the chapters cover most of the collections of objects (namespaces) that give an application functionality on the web. Without question, we used these sections the most. For those of us making the transition to C# at the same time we're getting used to .NET web development, these chapters were a life-saver. They gave all the answers we couldn't find in any C# reference manual tailored specifically for the types of web applications we were creating. Since we adopted .NET a few months ago, for the first time we were able to concetrate on functionality instead of C# as a frustrating language. I'm not sure how VB 6.0 programmers will look at it, but they seem to be getting the better reference books in the marketplace so far, so it was a relief to find every example done in both C# and VB.NET.

While this book would be key for beginning .NET developers ready for more robust applications or intermediate programmers moving from another language, I suspect that advanced programmers will be disappointed. For example, XML and Mobile Devices get chapters, but they don't conatain enough information for real development. You would need to have a much better background in either subject to actually develop. However, if you had that background, these sections wouldn't tell you anything you didn't already know.

The strength of this book is not as a "front-to-back" read, but as the dog-eared, coffee-stained reference that allows an intermediate level programmer to produce web applications that work--and work well. While not an expert, I've used ASP.NET Programmer's Reference to give myself a solid base of knowledge. By the time I master the material, I'll be well-prepared to tackle some of the more obscure .NET namespaces and cutting edge web technologies. ---Reviewed By Jay L.

Rating:
Summary: Excellent book as a reference !
Review: This book tricked me into believing that all the code was going to be in c# and vb.net. The first two chapters had examples in both languages. Then, as soon as you hit Chapter 3, it drops the dual language examples. As a Java developer having to do a .net project quickly, I would NOT recommend this book. I guess I'll try again.

Rating:
Summary: Half-baked intro with a decent namespace reference
Review: What this book covers: web controls, HTML controls, mobile internet toolkit, caching, configuration, security, xml, data and quite a few chapters on web services. Add a chapter (intro) on ASP.NET and you have the entire book summed up. Now the review:

I used to love Wrox. From a programmer's standpoint, they used to have the best books, bar none. Unfortuantely, they seem to be more interested in being the first to market these days rather than being the best.

On the plus side, Wrox's books always have plenty of sample code. This book is no exception. The problem I have is the book tries to be both an intro and a namespace reference, and it does neither exceptionally well, although it does better as a namespace reference. For this reason, I will keep this book in my normal reference library until something else comes along, but a more complete reference on the .NET Framework would be a wonderful addition (hint! hint!).

The book starts out as an intro to ASP.NET. Since ASP.NET is more of a technology than a language or product, this is a tough row to hoe. ANd, the book falls a bit flat. In previous ASP books, this was a much easier task, as ASP was thought of more as a language (due to the overwhelming adoption of VBScript for server side code) than a technology.

The book then begins to go through various .NET Framework namespaces that you will use with ASP.NET. While I believe a more full reference is in order, the namespaces covered are those you are more likely to use in your web work. The book tools along for awhile and then takes a sudden break with mobile controls. While I believe these are useful for web work, the placement of this chapter in the middle of the book is a bit confusing (must be the multiple author problem). The other confusing chapter is called Useful .NET namespaces - since almost every chapter deals with a namespace, why stop in the middle to generically single some out?

The book is not bad, and it is certainly worth the (price). I guess I have just come to expect so much more from a Wrox Reference. As they become heftier, they are less useful as a book to carry to a client site. And, as they become more a teaching book (which they are not doing well at here) and less a reference, it becomes harder to justify the expenditure.

In Summary: If you need a reference to learn a bit more about the .NET Framework namespaces, as they relate to ASP.NET, this is a good addition to your library. If you want to learn ASP.NET, look elsewhere.