Design MVC site such that UI developer can work without access to data tier? [closed]
Closed 10 years ago.
Design MVC site such that UI developer can work without access to data tier? [closed]
Closed 10 years ago.
Design MVC site such that UI developer can work without access to data tier? [closed]
Closed 10 years ago.
Design MVC site such that UI developer can work without access to data tier? [closed]
Closed 10 years ago.
Design MVC site such that UI developer can work without access to data tier? [closed]
Closed 10 years ago.
Design MVC site such that UI developer can work without access to data tier? [closed]
Closed 10 years ago.
Domain Services vs. Factories vs. Aggregate Roots
After dealing with DDD for months now, I’m still confused about the general purposes of domain services, factories and aggregate roots in relation to each other, e.g. where they overlap in their responsibility.
How to use data shaped by the UI from the ViewModel while keeping concerns separated?
I’m coming from a winforms background and trying to get ahold of MVVM and XAML. Right now I’m wondering how I can take advantage from a data-shaping control (either native or provided by a third party) while maintaining separation of concerns intact.
Is this a good practice or not?
I have a colleague who has come up with a way of ‘genericizing’ information from a database so that all his web application’s drop-down lists can share the same object in his MVC.NET C# code and Views, which can contain different data depending on what tables it is being used against.
Is this a good practice or not?
I have a colleague who has come up with a way of ‘genericizing’ information from a database so that all his web application’s drop-down lists can share the same object in his MVC.NET C# code and Views, which can contain different data depending on what tables it is being used against.