Comprehensive coverage to help experienced .NET developers create flexible, extensible enterprise application code
If you're an experienced Microsoft .NET developer, you'll find in this book a road map to the latest enterprise development methodologies. It covers the tools you will use in addition to Visual Studio, including Spring.NET and nUnit, and applies to development with ASP.NET, C#, VB, Office (VBA), and database.
You will find comprehensive coverage of the tools and practices that professional .NET developers need to master in order to build enterprise more flexible, testable, and extensible .NET applications with minimal upfront costs.
- Helps C#, VB.Net, and ASP.NET developers who wish to migrate both their applications and their own skillsets to newer, more flexible enterprise methodologies
- Describes each new pattern or feature along with its benefits, then outlines the pros and cons of its implementation
- Includes an introduction to enterprise development and a comprehensive overview of the differences between new enterprise patterns and older, traditional Microsoft programming
- Explains how to implement these patterns by upgrading an existing code base
- Covers benefits including flexibility, automated testing, extensibility, and separation; modular code; test-driven development, unit test, test automation, and refactoring; inversion of control; and object relational mapping
- Also covers enterprise design patterns: MVC including Ruby on Rails, Monorail, and ASP.NET MVC, MVP, observer, and more
- Contains a primer on object-oriented design
Professional Enterprise .NET focuses on the often-inevitable compromise between forward-thinking design and the needs of business, helping you build applications that serve both.
|Product dimensions:||7.30(w) x 9.20(h) x 1.10(d)|
About the Author
Scott Millett is the senior developer for wiggle.co.uk and a regular contributor to the asp.net forums.
Table of ContentsIntroduction.
Part I: Introduction to Practical Enterprise Development.
Chapter 1: What is Enterprise Design?
Chapter 2: The Enterprise Code.
Part II: The New Code -- Changing the Way You Build.
Chapter 3: Emancipate Your Classes.
Chapter 4: Test Driven Development.
Chapter 5: Make It Simple Again -- Inversion of Control.
Part III: Enterprise Design Patterns.
Chapter 6: Getting to the Middle of Things.
Chapter 7: Writing Your Own Middleware.
Chapter 8: "Mining" Your Own Business.
Chapter 9: Organizing Your Front End.
Chapter 10: Model-View-Presenter.
Chapter 11: The Model-View-Controller Pattern.
Chapter 12: Putting It All Together.
Appendix A: C#.NET Primer.
Most Helpful Customer Reviews
The first chapter of this book was basically an attack on Microsoft developers and their poor development habits (due to RAD). However, I was not offended; on the contrary, I was shocked that someone finally pointed these facts out. The authors made a statement, "...built applications for automation" which describes the typical MS developer's methodology. I agree with the entire observation. It's just a shame that most MS developers wont see this book because they are the ones who think they don't need it. The rest of the book was a great tour through the enterprise patterns and how to implement them. Unfortunately, the book did not provide anything that I haven't already read in about 20 other books; The difference with this book is that the authors do a great job of getting you to think about why you should consider the enterprise patterns and way of life. they cover both small and large project types and do not discriminate against either one which was refreshing. I was disappointed though about the shear number of grammatical errors in the first few chapters and more so later on. Even worse were the code samples in the Middleware chapters. Following the code right from the book is not a good idea. There were entire methods left out (by mistake, not on purpose) and errors in the code that look as if there was a copy/paste gone wrong. I don't understand why the authors would include intro sections to Linq to Sql, Entity Framework and NHibernate. I felt it was out of place and unnecessary to accomplish the goal of the chapter. My guess is that it is an attempt to get the reader to open up to new technologies? I do like the fact that the chapter focuses more on NHibernate than Linq to SQL and EF, even though I don't use it. Overall this was a great read and I recommend that any .NET developer read it for the sake of others who need to look at your code ;)