- Series: Developer Reference
- Paperback: 992 pages
- Publisher: Microsoft Press; 1 edition (March 14, 2011)
- Language: English
- ISBN-10: 0735643385
- ISBN-13: 978-0735643383
- Product Dimensions: 7.4 x 1.6 x 9 inches
- Shipping Weight: 3.2 pounds (View shipping rates and policies)
- Average Customer Review: 3.8 out of 5 stars See all reviews (11 customer reviews)
- Amazon Best Sellers Rank: #1,200,358 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Programming Microsoft® ASP.NET 4 (Developer Reference) 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Frequently bought together
Customers who bought this item also bought
About the Author
Dino Esposito is a well-known ASP.NET and AJAX expert. He speaks at industry events, including DevConnections and Microsoft TechEd, contributes to MSDN® Magazine and other publications, and has written several popular Microsoft Press books, including Microsoft ASP.NET and AJAX: Architecting Web Applications.
Browse award-winning titles. See more
If you are a seller for this product, would you like to suggest updates through seller support?
Top Customer Reviews
This book covers all its material in-depth. A lot of the material is for advanced ASP.NET programmers. The author gives this warning at the beginning of the book.
The book has complete chapters on ASP.NET and IIS, Configuration, HTTP Handlers, Modules, and Routing, Core Server Controls, Input Forms, Data Binding, HTTP Request Context, State Management, Caching, Security, Ajax, and jQuery.
One of the things I did not like about the book is that it has cut the advanced aspects of ASP.NET and refers you to the author's previous book for those topics. This seems to be the new way publishers are saving money. Although I have seen some reviews that complained about all the previous material being included and bloating a book, I have seen 10x the amount of complaints about the removal of the material.
Another thing that annoyed me was the inclusion of material from one of the authors other books, Microsoft .NET: Architecting Applications for the Enterprise. It is not that the material is bad (actually it is great), is just is too limited to have an impact. It felt out of context. You should read that entire Architecting Applications for the Enterprise book, not just a few chapters from it. I would have preferred more technical ASP.NET information be included in its place.
The saving grace with respect to the two annoyances I listed above was that the author did not repeatedly refer to his other books. I have read some books that it seemed every five pages you were being told to go look something up in the author's other book before reading what they had written in their new one.
My favorite thing about this book is the level of detail the author goes into. He does a great job of providing the complete picture of all the topics he covers.
The chapter on security is great. It breaks down all the aspects of ASP.NET security including Where the Threats Come From, The ASP.NET Security Context, Forms Authentication, The Membership and Role Management API, Claims-Based Identity, and Security-Related Controls.
The code is very well organized and usable. It is all under one solution file.
I highly recommend this book to anyone doing advanced ASP.NET programming or doing .NET Software Architecture.
I have both the electronic and the hard copy version because I'm always loaning out the hard copy version to my work mates.
I think that this book might be the best 2013 technical book (although I'm keeping an open mind).
The contrast with other books on the close subject, like Java Script by Nocholas Zakas or MVC4 by John Galloway and other from WROX, is evident. You just read the material in these books and understand what those guys wanted to say. Here, with ASP.NET4, the situation is much worse.
I was even thinking about returning the book.