Pro ASP.NET MVC 2 Framework, Second Edition Kindle Books Reviews
Pro ASP.NET MVC two Framework, Second Edition
Author Steven Sanderson has observed the ASP.NET MVC framework mature from the start off, his experience, combined with complete protection of all the new characteristics, including in the official MVC Toolkit gives the clearest knowledge of how these thrilling new framework can Improve its coding effectiveness. With this e-book you will gain valuable up-to-date understanding of security, deployment & interoperability issues.The Framework ASP.NET MVC 2 is the latest advancement in Microsoft ASP.NET web platform. It offers a radically new large-productivity programming model, promotes cleaner code architecture, test driven development & effective extensibility, combined with all the benefits of ASP.NET 3.five.In this b
List Value: $ 43.99
Value:
User Stories Utilized: For Agile Software program Growth
Agile needs: finding what your customers really want. With this guide you will discover: Versatile, fast & sensible requirements that function save time & create greater application, users needsGathering person stories met – even if you do never speak into consumer stories work usershow, & how they differ from use situations anticipated scenarios classic & demands leveraging person stories as component of the planning, scheduling, estimating, & testing excellent for Extreme Programming, Scrum, or any other agile approaches fully reviewed & eagerly agile by the community, presents Consumer Tales Applied a set of specifications process that saves time, eliminates rework, & leads immediately into greater application. The finest way into construct computer software applies,
Checklist Cost: $ 43.99
Price:
Related posts:
- New Perspectives on Microsoft Office 2007, First Course, Premium Video Edition, 1st Edition Kindle Books Reviews
- The Little SAS Book: A Primer, Fourth Edition Kindle Books Reviews
- Succeeding with Agile: Software Development Using Scrum Kindle Books Reviews
- The Jungle Book by Rudyard Kipling (w/ Active Table of Contents and Chapter Navigation) [KINDLE EDITION] Kindle Books Reviews
- Programming Collective Intelligence Kindle Books Reviews
- Getting to Yes: Negotiating Agreement Without Giving In; Second Edition Kindle Books Reviews
- CompTIA A+ Certification All-in-One Exam Guide, Seventh Edition (Exams 220-701 & 220-702) Kindle Books Reviews
- Data Analysis and Decision Making with Microsoft- Excel, Revised, 3rd Edition Kindle Books Reviews
Tags: ASP.NET, Books, Edition, Framework, Kindle, Reviews, Second
February 5th, 2011 at 5:52 am
Fantastic Book,
Every now and then you read a software development book that absolutely takes your breath away. This is one of those books.
This is an outstanding book for the professional developer who is looking to become an expert on ASP.NET MVC, and who wants to seriously “raise their game” when it comes to software development in general. Steve Sanderson (the author) has a fantastic writing style that is easy to read, and which flows very naturally.
The first 212 pages of the book are mostly spent building two applications (a party invite application and a sports e-commerce store) literally starting with File->New Project and walking you step-by-step through their creation (explaining all of the code keystrokes, C# language features, and Visual Studio steps required along the way). These provide a great set of tutorials that can help you understand how ASP.NET MVC works and can be applied to build common web scenarios.
Sanderson’s book avoids simply showing “the basic path” when it comes to building ASP.NET MVC applications, and instead takes the much bolder approach of teaching ASP.NET MVC in conjunction with Unit Testing, Test Driven Development (TDD), Dependency Injection, and Mocking. What makes the book so great is that he is able to make these concepts (which most books consider “advanced topics”) straight forward to comprehend and grasp. He introduces them early, explains the concepts behind them quickly, and then does a masterful job of immediately showing how you can apply and use them pragmatically within ASP.NET MVC applications. The result is that they feel natural, you really “get” the concepts behind them, and you are left knowing the exact mechanics and steps necessary to take advantage of them within your own ASP.NET MVC applications. He uses the free, open-source NUnit, Moq, and Ninject frameworks within the book – which work with all version of Visual Studio (including the free express editions).
The remaining 500 pages of the book then go into detail on all the core areas of ASP.NET MVC, and do a phenomenal job of explaining both all of the features – and more importantly how to take advantage of them. In addition to covering the built-in features of ASP.NET MVC, he covers how to implement common scenarios with it like implementing CAPTCHAs, how to take advantage of jQuery, use VS 2010′s new web deployment features, and more.
This book is a tour de force and absolutely stunning. It is a must-have for the bookshelf of any professional ASP.NET MVC developer.
Scott Guthrie
Corporate Vice President – Developer Division
Microsoft Corporation
Was this review helpful to you?
|February 5th, 2011 at 6:41 am
Excellent book for learning ASP.NET MVC 2,
I see Scott Guthrie has already recommended the book and gave it five stars. What other recommendation do you need? You should purchase this book! In case you want additional validation to purchase this book, here is my review. I have been an ASP.NET Webform developer since the first release. I have been listening to the buzz at conferences and in Scott Guthrie’s blogs about ASP.NET MVC and more recently MVC 2 and wanted to start my education so I purchased this book. This book is an excellent book for learning MVC 2.
The book starts off giving you an overview of what MVC is, how it’s different than Webforms and why it’s better. It also does a brief comparison to other similar products like Ruby on Rails and MonoRail. The next five chapters are dedicated to building a simple RSVP form and an eCommerce store using MVC 2. It doesn’t just give you a simple demo of MVC features but builds an actual working application that could be the beginnings of a real application. Building these applications gives you a great feeling for the language. But Mr. Sanderson isn’t content with just teaching you MVC, he also wants to teach you many of the best practices in software development. He covers test-driven (TDD) and behavior-driven development(BDD). I love the ShouldEqual() extension method for simplifying an assert. He covers Nunit, Moq and Specflow (Gherkin BDD language interpreter). He talks about unit testing versus integration testing. He uses Linq to SQL for database integration and Ninject for Dependency Injection. While you can download all of the source code for the applications from the apress.com web site, I typed in all of the samples from the book. I can honestly say I haven’t found one sample that didn’t work as expected. The book also uses CSS to keep the HTML clean.
Once you are done building the two applications and have a good understanding of how ASP.NET MVC actually works in practice, Part 2 of the book covers MVC features in detail. It covers URLs and URL routing, controllers and actions, extending controllers and the request processing pipeline, views, HTML helper methods, models with parameter binding and validation, user interface techniques and Ajax and client JavaScript including jQuery. The last few chapters deal with deployment strategies and understanding common security vulnerabilities and how to avoid them. There is also a section that talks about upgrading from webforms to MVC and even discusses how to combine the two technologies.
Even though I have a good understanding of many of the best practices introduced in the book, I found the book’s coverage of these topics the appropriate length and depth. Mr. Sanderson goes to great lengths to support Visual Studio 2008 and 2010 as well as ASP.NET 3.5 and 4.0. At the beginning I was worried the author was going to duplicate examples in both versions but to his credit he quickly transitioned to using ASP.NET 4.0 syntax but with appropriate callouts to bring attention to the differences and warning that there would be no further warnings.
One small criticism of the book was with the use of Linq to SQL. I would have preferred him covering the Entity Framework or nHibernate. Mr. Sanderson explained why he choose Linq to SQL and his reasons are valid. Another equally small criticism was with mixing CSS styles with HTML in the Shopping cart example. He took great pains in the rest of the application to use best practices but took the easy way on this sample. Obviously if these are the biggest criticisms I can give the book, the book is pretty amazing. I strongly recommend the book and is one of the best programming books I have purchased (and I have purchased many).
Was this review helpful to you?
|February 5th, 2011 at 7:21 am
Absolutely must-read,
Scott Guthrie wrote a review with enthusiastic recommendation – so I realize that anything I add isn’t going to be that helpful
The first version of the book was my favorite on MVC1, and I couldn’t wait to get MVC2 version. And it didn’t disappoint!
So, all my comments below shouldn’t dissuade you in any way from getting this book as soon as possible!
1. I read first version of this book after I went through Nerd Dinner tutorial. I think a “quicker-and-dirtier” example like Nerd Dinner would be helpful before you get into unit testing, dependency injection, and other advanced topics. Especially if your background is in WebForms! Unfortunately, Scott’s team seem to have taken extended vacation after MVC2 and VS2010 went live in April. All the tutorials are still covering MVC1 (as of mid-July 2010).
2. Just like somebody else noted, I would prefer to use EF over LINQ to SQL. I understand author’s arguments; I just disagree with them. Most developers are upgrading the tools very quickly (unlike OS or business applications the concern about backward compatibility just isn’t there). There are a lot of issues that are at intersection of EF4 and MVC2 – having example that use both would be just awesome! More generally, I think there is too much concern (and space) dedicated to VS2008 issues.
3. Author chose Ninject for DI examples… It feels from conversations that I had that Castle Windsor is more popular.
4. It seems to me that every MVC project is using T4MVC (and for good reason… magic strings are EVIL). Would be nice to see it incorporated in the book!
5. As I said, this is one of the best (if not the best) books on the topic. Would be nice to have a forum where the readers can discuss some topics, help each other, and maybe make suggestions or enhancement requests. If such forum exists – I couldn’t find it.
Was this review helpful to you?
|February 5th, 2011 at 8:08 am
The user story bible,
‘User Stories Applied’ was a book that long stood on my Amazon wish list with a ‘must have’ rating. I’m not disappointed. I loved the book. Now let me explain why.
First of all, running the planning aspect of an XP project, for example, well is essential for reaping the benefits of agile software development. Yet, relatively little has been written to guide practitioners in doing that. I, for example, have made all the mistakes Cohn enumerates in the chapters for guiding the user towards writing *good* user stories (usually more than once). These sorts of things make you realize you shouldn’t put the book on the shelf to gather dust! The author doesn’t cover just writing good user stories, but the whole spectrum from putting together the customer team to estimating stories to discussing the stories to writing acceptance tests for the stories.
Second, it’s a pleasure to read. The structure makes sense, each chapter is followed by a useful summary, and there’s a set of questions — along with answers — to make sure you understood what the chapter talked about. Usually these kinds of Q&A sections simply force me to skip them over. The questions in this book did not. I read each and every one of them and I think there was only one set of questions that I did ‘pass’ with the first try, usually having forgotten some rather important aspects to consider (concrete evidence of their usefulness to me). To finish, the last part of the book, an example project, nicely ties together all the threads.
As usual, there were some things I experienced not so well. I believe the chapter on applying user stories with Scrum could’ve been left out without breaking the plot. Also, I think a typical user wouldn’t have been bothered about dropping the appendix introducing Extreme Programming.
In summary, this is the book to get if you’re involved with user stories. I had to pause reading every few pages to scribble down some specific tips. I’m confident that you will too.
Was this review helpful to you?
|February 5th, 2011 at 8:13 am
Finally! Practical advice on writing user stories, and more,
This excellent book is a must-have for anyone on an agile team – developers, testers, business experts, analysts – and for anyone who struggles with requirements, planning, or estimating on any software project.
User Stories Applied is easy to read and digest. As the title suggests, its techniques are easy to apply and deliver huge value. Each chapter summarizes developer and customer responsibilities, and has questions whose answers are provided in an appendix. The book is full of real-life, concrete examples, allowing you to learn from the successes and failures of others.
This book will give you many tools to help your projects succeed. Just a few of the most valuable topics:
When are user stories too big, too small, too detailed, too general, too open ended, when are they not user stories, and how to correct all these.
Why use user stories.
How to handle requirements for infrastructure, performance, qualitative aspects, UI.
How to ask questions to elicit requirements.
How to cope when you don’t have `on-site customers’.
Practical ways to estimate stories.
Monitoring velocity and progress.
When to keep and when to discard artifacts.
Mike explores the differences between stories and other techniques for delivering requirements: IEEE 380, use cases, scenarios. He points out many positive side effects of user stories, such as encouraging participatory design and tacit knowledge accumulation.
I particularly like that the book emphasizes the team’s responsibility to successfully complete each iteration. I enjoy Mike’s illuminating bits of wisdom, such as the “everything takes 4 hours” example. I love the comprehensive example in Part IV. No matter what your level of experience, you’ll put the ideas in this book to immediate and productive use.
Was this review helpful to you?
|February 5th, 2011 at 8:26 am
For XP enthusiasts,
Writing user stories is one of the twelve practices of the XP software development methodology. User stories summarily describe features of the software that must be developed, from the point of view of the user. This means that no implementation detail is present on stories.
As with all the XP practices, the emphasis is on traveling light, producing only those artifacts that are absolutely necessary. Thus, user stories contain a brief description of the feature as a reminder, to the developers and to the customer, that sometime in the future they will need to meet and flesh out the details. This is in contrast to techniques like use cases, which might seem similar but are much more formal and rich.
User stories also play a fundamental role in the planning game, one of the other XP practices. During the planning game, the development team and the customer together discuss the stories, the developers estimate the time necessary to implement each story, in terms of story points and the customer prioritizes them. During the next iteration, developers will implement those stories that the customer deemed more urgent, up to a number whose total sum of points does not exceed the estimated team velocity.
All of this is explained in a couple of the XP series books, namely Extreme Programming Explained: Embrace Change and Planning Extreme Programming You’d better have already read at least the former of those before picking up Mike Cohn’s book.
User Stories Applied does a good job explaining in detail what user stories are, what goes into them -and what doesn’t -, how they should be estimated and what to do with them after the stories have been implemented.
There’s a lot of good sense advice in this book, which might induce someone to think that user stories and all other XP practices are just a bunch of generic suggestions that you might apply or not, as you wish. That’s certainly not true, as XP is a methodology whose effectiveness lies in the combined action of all the practices when they are taken to the limit. This takes determination and discipline and, in my experience, it’s just too easy to fall into the habit of following only some of them, say when you’re not under deadline pressure, and still pretend that you’re an XP shop.
I would have liked more real-life stories in this book, in order to spice it up a little. As it is, everything that is there sounds highly reasonable (at least to me) but it wouldn’t convince anyone who is skeptic of XP’s supposed benefits. The example at the end of the book sounds contrived and hollow.
On the other hand, if you have been already convinced by Kent Beck’s white book and want to start adopting XP, I can heartily recommend Mike Cohn’s book.
Was this review helpful to you?
|