Isn\'t it a violation of separation of concerns princi开发者_StackOverflow中文版ple when you use the RemoteAttribute on your model\'s property to indicate what action and controller to call? It makes
I\'ve recently read the article CQRS à la Greg Young and am still trying to get my head around CQRS.
In this application I\'m developing, the domain revolves around, say, electrical appliances. There are several specialized versions of this entity. Appliances can be submitted to the application, and
I\'ve inherited an asp.net web solution, which has business logic and data calls as seperate assemblies. In the busine开发者_StackOverflowss layer there are a small number of calls to get/set HttpCont
I have the following layers in my project Web/UI, Service, Repository, Common and some other that I don\'t think matter for this case.
As I understand it, a UnitOfWork class is meant to represent the concept of a business transaction in the domain. It\'s not directly supposed to represent a database transaction, which is a detail of
In my attempt to keep with a good Repository/IoC Design, I am trying to figure out the best approach the current problem.
How does Clojure approach Separation of Concerns ? Since code is data, functions can be passed as parameters and used as returns...
In asp.net mvc, when I 开发者_StackOverflowhave my custom validations and validation messages using dataannotations in Model, does it not violate separation of concerns? ie: the custom validation migh
I am currently开发者_如何学运维 using the ASP.NET MVC framework on a project (pretty much my first time)
加载中,请稍侯......