-
Back to the problem at hand, I'm working through the first of my use cases and have had an 'aha' moment of sorts. To spare you from scrolling up and re-reading the use case, I've repeated it here: The first use case is to retrieve and display a list of assessments that a user needs to complete. This will be displayed when the user first
-
Let me clarify because I sense confusion. I used the term 'entity' in the DDD sense which is all about encapsulating Domain Logic (Business Logic) in the Domain Layer and, in DDD terms, an Entity is an object that has Identity. I realize that in the world of Entity Framework, etc. that the term can also be applied to more of a table-driven design
-
I am trying to make the jump from data-centric design and development into more of a DDD approach (using CSLA for my domain objects, of course!) and have read Evans and Nillson but am still having trouble wrapping my head around how I should structure my Domain Layer. I'm sure the nature of my current project isn't helping! A little background
-
I could use a little help wrapping my head around the approach I should use to model a specific requirement a set of recurring activities that are used by my application. Think of it as a Preventative Maintenance schedule. Each item in my system is assigned one of a set of PM schedules. Each schedule defines how often the PM must occur and how much
-
This is probably a re-hash of an old topic, but most of what i found searching the forum is quite old so I thought a refresher might be in order. I have a project that requires me to integrate data from three separate databases. Two are SQL Server while the third is DB2. The DB2 database is closed to changes as it houses the company's financial
-
Wrt CSL, I agree. I get the feeling that neither of you are too concerned about post-deployment configuration changes? One of my concerns is using IoC to make the application extensible - meaning that I have multiple implementations that can be "plugged in" to customize the application's behavior. It has always seemed to me that XML configuration
-
Yea, I've looked at the Common Service Locator project and have started down that path even before that but am on the fence with that regard. As I see it, to abstract the container, you have to code to the lowest common denominator which means you lose what makes each framework unique. For instance, I know Windsor has a nice fluent interface for
-
I am looking to implement an Inversion of Control (IoC) framework with my current client and thought I'd do some homework to make sure I use the best solution for the problem. I have prior experience with Spring.NET, Unity and Castle Windsor but have also been reading up on StructureMap and, most recently, Ninject. My problem with the IoC "community"
-
FYI - we are still looking...
-
I've been trying to resolve a design problem for a while now and find myself getting nowhere with other forums, blogs posts, articles, etc. so I am turning to my trusted source for guidance... I am designing an application that uses Workflow Foundation to define the processing logic for a series of transactions. One goal is to support multiple UIs that