 Trade In this Item for up to £3.95
Get an extra £5 when you trade in books worth £10 or more until June 30, 2012. Trade in NET Domain-Driven Design with C#: Problem, Design, Solution (Programmer to Programmer) for an Amazon.co.uk gift card of up to £3.95, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Frequently Bought Together
Product details
|
More About the Author
Product Description
Product Description
As the first technical book of its kind, this unique resource walks you through the process of building a real–world application using Domain–Driven Design implemented in C#. Based on a real application for an existing company, each chapter is broken down into specific modules so that you can identify the problem, decide what solution will provide the best results, and then execute that design to solve the problem. With each chapter, you′ll build a complete project from beginning to end.
From the Back Cover
.NET Domain–Driven Design with C# Problem Design Solution
As the first technical book of its kind, this unique resource walks you through the process of building a real–world application usingDomain–Driven Design implemented in C#. Based on a real application for an existing company, the project featured throughout the book focuses on the Domain Model and the framework that is being built to support it.
Each chapter is broken down into specific modules so that you can identify the problem, decide what solution will provide the best results, and then execute that design to solve the problem. With each chapter, you?ll build a complete project from beginning to end, offering you indispensable, hands–on practice at creating code that builds applications.
What you will learn from this book
- When, why, and how to use Domain–Driven Design
- How to design and build the initial Domain Model
- What to do to achieve ?Persistence Ignorance?
- Ways to build a Repository framework for the Domain Model
- Techniques for applying TDD to the Domain Model
- How to apply the Model–View–ViewModel Pattern
- How to build a client–side membership system
- What to do to synchronize the client application with the server
Who this book is for
This book is for experienced C# .NET developers who want to improve their techniques for writing applications that perform well and are highly scalable.
Wrox Problem – Design – Solution references give you solid, workable solutions to real–world development problems. Each is devoted to a single application, analyzing every problem, examining relevant design issues, and implementing the ideal solution.
Inside This Book
(Learn More)
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
Most Helpful Customer Reviews
6 of 6 people found the following review helpful
Format:Paperback
After buying this book I thought it would prove to be a good way to get acquainted with DDD using a real world example however this was spoilt by a number of items:
* Too much code examples detract away from the main DDD principles not sure why the author could not have leveraged more of the existing libraries out there already for things like IoC & persistence
* Most of the unit tests used I would class more as integration tests because they require the database to be present and to be in certain states
* Some of the object designs I did not agree with and found them to go against the S.O.L.I.D. principles and reduce testability
* Some of the source code examples included descriptions that were for the wrong pieces of code
* After downloading the source code from codeplex I could not get basic functionality to work without exceptions being thrown
* Once your passed the chapter 3 the next chapters until chapter 10 all have a sense of deja-vu
* Too much code examples detract away from the main DDD principles not sure why the author could not have leveraged more of the existing libraries out there already for things like IoC & persistence
* Most of the unit tests used I would class more as integration tests because they require the database to be present and to be in certain states
* Some of the object designs I did not agree with and found them to go against the S.O.L.I.D. principles and reduce testability
* Some of the source code examples included descriptions that were for the wrong pieces of code
* After downloading the source code from codeplex I could not get basic functionality to work without exceptions being thrown
* Once your passed the chapter 3 the next chapters until chapter 10 all have a sense of deja-vu
2 of 3 people found the following review helpful
Format:Paperback
After reading the seminal work by Eric Evans "Domain-Driven Design: Tackling Complexity in the Heart of Software" I immediately bought in to the DDD way of thinking, although it was all bit abstract and I didn't really know where to start to turn the ideas into an real application.
Then along came "Applying Domain-Driven Design and Patterns: With Examples in C# and .NET" by Jimmy Nilsson, which combined the ideas of Eric Evans with known Design Patterns. However it didn't provide an end to end implementation but suggested ways to architect an application.
Tim's book ".NET Domain-Driven Design with C#: Problem, Design, Solution" seems to be the logical end to the collection of DDD books out at the moment, you can see that the author has understood ideas from Evans and suggested techniques from Nilsson, along with widely known patterns of Fowler (Martin Fowler - Patterns of Enterprise Application Architecture).
In my opinion this is a great book which shows you how to make a solid DDD application that stays true to Evans's original work.
Top banana.
Then along came "Applying Domain-Driven Design and Patterns: With Examples in C# and .NET" by Jimmy Nilsson, which combined the ideas of Eric Evans with known Design Patterns. However it didn't provide an end to end implementation but suggested ways to architect an application.
Tim's book ".NET Domain-Driven Design with C#: Problem, Design, Solution" seems to be the logical end to the collection of DDD books out at the moment, you can see that the author has understood ideas from Evans and suggested techniques from Nilsson, along with widely known patterns of Fowler (Martin Fowler - Patterns of Enterprise Application Architecture).
In my opinion this is a great book which shows you how to make a solid DDD application that stays true to Evans's original work.
Top banana.
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com:
9 reviews
14 of 15 people found the following review helpful
Nice reference app for DDD
20 Jun 2008
Format:Paperback|Amazon Verified Purchase
I've been playing with Domain Driven Design off-and-on for about a year now. I've read the Evans book (Domain-Driven Design: Tackling Complexity in the Heart of Software), the Nillson book (Applying Domain-Driven Design and Patterns: With Examples in C# and .NET), and the Fowler book (Patterns of Enterprise Application Architecture (The Addison-Wesley Signature Series)), but what I really need is a real-world reference app to put all these concepts together.
That's what Tim McCarthy's book does. It presents an anotated reference application, a real estate construction management application built as a WPF smart client. McCarthy's writing is clear and to-the-point--he simply provides a running commentary on the reference app from a sequence-of-development perspective. He starts with a skeleton and builds out the app from there, discussing his refactorings as he goes. I find this very helpful as a template for developing my own DDD apps.
The reference app is written in C#, as are the book's code snippets. However, since most of the code discussed boils down to .NET calls, even VB users with only limited experience with C# may find it useful. As C# is my language of choice, it did not present any problem for me.
This is a really good book; the best I've bought in a while. I do not hesitate to recommend it to any developer learning DDD in C#.
That's what Tim McCarthy's book does. It presents an anotated reference application, a real estate construction management application built as a WPF smart client. McCarthy's writing is clear and to-the-point--he simply provides a running commentary on the reference app from a sequence-of-development perspective. He starts with a skeleton and builds out the app from there, discussing his refactorings as he goes. I find this very helpful as a template for developing my own DDD apps.
The reference app is written in C#, as are the book's code snippets. However, since most of the code discussed boils down to .NET calls, even VB users with only limited experience with C# may find it useful. As C# is my language of choice, it did not present any problem for me.
This is a really good book; the best I've bought in a while. I do not hesitate to recommend it to any developer learning DDD in C#.
3 of 3 people found the following review helpful
Useful, but irritating
29 July 2008
Format:Paperback
I find the book useful in the way it present a design the evolves as the authors attack new parts of the problem area. There are many interesting patterns and ways of dealing with problems that I can see myself using in my own projects.
My main objective is that it can get a bit repetitive. By accident I skipped from the middle of one chapter to the middle of the next. Because of the repetitiveness it took me a while to discover it. At the same time new aspects are constantly introduced so there are still value in the new chapters.
A big annoyance is all the textual errors. It is obvious that cut and paste has been a big part of writing this book, and many times the author has forgotten to update the copied text appriopriately. There is also evidence of the restructuring of the book gone bad, with reference to items not having been introduced yet. It all seems like a bit of a rush job.
Even so, I will give it a pretty high score for the content of the book and the way it can help developers approach their challenges in a good way
My main objective is that it can get a bit repetitive. By accident I skipped from the middle of one chapter to the middle of the next. Because of the repetitiveness it took me a while to discover it. At the same time new aspects are constantly introduced so there are still value in the new chapters.
A big annoyance is all the textual errors. It is obvious that cut and paste has been a big part of writing this book, and many times the author has forgotten to update the copied text appriopriately. There is also evidence of the restructuring of the book gone bad, with reference to items not having been introduced yet. It all seems like a bit of a rush job.
Even so, I will give it a pretty high score for the content of the book and the way it can help developers approach their challenges in a good way
1 of 1 people found the following review helpful
Great for reference
16 Oct 2009
Format:Paperback
This book was entirely describing the design and implementation of SmartCA application using domain-driven design pattern. The author put every detail of steps in building this application from class design classes, creating solution, configuration, writing unit test... I did not run sample code so I did not know if it actually worked. My focus was the design. The author also provides detail of MVC model for SmartCA application
About the topic, the design was very interesting to me. I used this approach in my past company ( about 10 years ago). However, the design in this book was much cleaner with the favor of .Net 3.5. I like the concept of "the domain model is ignorant of how its data is saved or retrieved from its underlying data store or stores" . The introduction of unitOfWork and Repository objects for each aggregate was good in the design. I think chapter 2 was most important chapter. This described the architecture design of the application, what layer needed, how they interacts with each other. This must be understood completely before moving down to the detail. Once the design pattern was clear, the later chapters provided detail implementations. The structure was similar exception each chapter focus on particular aggregate entity.
I think this book is definitely not for C# beginner. It can be a good reference for higher level.
About the topic, the design was very interesting to me. I used this approach in my past company ( about 10 years ago). However, the design in this book was much cleaner with the favor of .Net 3.5. I like the concept of "the domain model is ignorant of how its data is saved or retrieved from its underlying data store or stores" . The introduction of unitOfWork and Repository objects for each aggregate was good in the design. I think chapter 2 was most important chapter. This described the architecture design of the application, what layer needed, how they interacts with each other. This must be understood completely before moving down to the detail. Once the design pattern was clear, the later chapters provided detail implementations. The structure was similar exception each chapter focus on particular aggregate entity.
I think this book is definitely not for C# beginner. It can be a good reference for higher level.
Were these reviews helpful?
Let us know
Listmania!
|
|
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
