Being accustomed to using services and the concise calls they provide to interfact with the business layer, I\'ve been wondering if this approach can be applied to the user interface.
I\'m using OpenRasta to create a Survey application. I have a SurveyResource that is accessible at /surveys/{id} and editable at /surveys/{id}/edit
We are having a \"discussion\" about what should be placed in the facade layer and how many calls the facade layer should make to the underlying layers.
I\'m analyzing a fellow developer\'s SQL code and I could be totally wrong, but something they\'ve done doesn\'t seem good to me.
I am looking Sharp Architecture alternative which use Entity Framework code first as ORM. Is there any mature project like Sharp Architecturewith EF c开发者_运维百科ode first ?Architecture is a bluepr
I\'m working my way through \'head first design patterns\' and want to use this in practice immediately.
Looking for suggestions on how to approach this problem and to understand if Do开发者_开发知识库main Driven Design is really the best pattern here.
Imagine a list with some items. Each item is a movie and includes: the title a ranking with stars (1-5)
I have an interface for a Service object that looks something like the following (simplified for brevity):
I have a class that needs to be sortable in a couple of different ways, many of which break the equals() contract, so I need to have a bunch of different Comparator classes. The question I have is whe
加载中,请稍侯......