.NET Domain-Driven Design with C#: Problem - Design - Solution (Programmer to Programmer)
โ Scribed by Tim McCarthy
- Publisher
- Wrox
- Year
- 2008
- Tongue
- English
- Leaves
- 435
- Series
- Programmer to Programmer
- Category
- Library
No coin nor oath required. For personal study only.
โฆ Synopsis
There are some things I don't like.1. UnitOfWork is broken. What happens when someone adds entity to repository, and then removes it before commiting? The code will try to remove not existing objects from database and then it will add it!2. Handling of child objects. For example addresses. In any real world app deleting every child object and then adding it again whether there were changes or not would have no place. First performance. Second what If You have to keep history of changes of that child object? What if they have Id's in database and have other children? What if two users work with same objects? What about concurrency? These are problems I have to deal with every day and I would expect some good examples from book writer. Especially that has so many certificates.3. This book has a lot of repetitive text/code for every factory/repository/service clsss... I would like to have some discussion about problems I mentioned in p.24. WPF that nobody knows (yeah some know, but how many WPF have You seen?) shouldn't be used in book about DDD. Do it in WinForms, ASP.NET or even Console app. Why show us WPF? Hell You can't even build sources from this book without going to 3rd party for their GridControl. What's the point of using WPF?This book is good for someone that doesn't know much about DDD and is doing apps for one user. O
โฆ Table of Contents
.NET Domain-Driven Design with C#: Problem - Design - Solution......Page 1
About the Author......Page 8
Credits......Page 10
Contents......Page 12
Acknowledgments......Page 18
Who This Book Is For......Page 20
What This Book Covers......Page 21
What You Need to Use This Book......Page 22
p2p.wrox.com......Page 23
The Problem......Page 26
The Design......Page 29
The Solution......Page 31
Summary......Page 36
The Design......Page 38
The Solution......Page 43
Summary......Page 78
The Design......Page 80
The Solution......Page 90
Summary......Page 132
The Design......Page 134
The Solution......Page 144
Summary......Page 181
The Problem......Page 182
The Design......Page 183
The Solution......Page 189
Summary......Page 222
The Problem......Page 224
The Design......Page 225
The Solution......Page 232
Summary......Page 257
The Problem......Page 258
The Design......Page 259
The Solution......Page 267
Summary......Page 288
The Problem......Page 290
The Design......Page 291
The Solution......Page 296
Summary......Page 318
The Design......Page 320
The Solution......Page 325
Summary......Page 350
The Design......Page 352
The Solution......Page 358
Summary......Page 381
The Design......Page 382
The Solution......Page 384
Summary......Page 414
Index......Page 416
๐ SIMILAR VOLUMES
This book is not an MVC intro book. This book is building a non-trivial app MVC! In this book Nick Beradi and Al Katawazi is transferring Marco Bellinaso's classic The Beerhouse app to MVC. And they do an okay job. You need this book if you don't know how to build a non-trivial app MVC, at the time
Perfectly suited to the innovative Problem ? Design ? Solution approach, ASP.NET MVC is a new development model that separates code for the data, look, and business processes of a Web site. This nuts-and-bolts guide thoroughly covers creating a Web site with MVC and discusses solving the most common
A hands-on journey takes you through the development process of a Web application from concept to productionASP.NET MVC is a new Web development framework created by Microsoft as an alternative to ASP.NET web forms applications. MVC is well suited to testability, and Test Driven Development (TDD) af
I've read through many of the reviews on this site, both positive and negative. The main point is that if you are a beginner to ASP.NET, C#, or both then this book is NOT for you. However, if you have some experience with ASP.NET and C#.NET and would like to learn more about an N-Tier approach (es