I\'d like to use DTO\'s in my view models in lieu of my domain objects, however I\'m having a hard time justifying the maintenance overhead of having to maintain two sets of properties for each domain
I am at the moment creating a project large enough in my opinion to separate carefully the well-known layers in its architecture.
I have an architectural question concerning custom fields in a view for an object. Let\'s say you have a User Object with some basic information like firstname, lastname, ... that can be used by all c
Using VS2010, .NET4.0, MVC3, EF4.1 Code-First I have this POCO entities: public class XBLContent { [Key] [StringLength(36, ErrorMessage=\"Must have 36 characters\")]
I created a modular application where each module only communicates through the other one with strong interfaces.Recently I found that we failed to separate the modules completely because there is a s
Closed. This question is seeking recommendations for books, tools, software libraries, and more. It does not meet Stack Overflow guidelines. It is not currently accepting answers.
Just wanted to know if i am going in the right direction or not. I am implementing Request-Reply (Request-Response) pattern in which every operation sends a request object and gets response object ba
If I have an app that consists of multiple layers, defined as multiple projects in a solution, is it ok to have a layer reference the layer directly above/below it? Or, should one use dependency injec
XCode 3.2.4 on OSX 10.6 (upgraded from 10.5), using GCC 4.2, tells me it can\'t find . I know it\'s located under \"/Developer/SDKs/MacOSX.4u.sdk/usr/include/c++/4.0.0/i686-apple-darwin8/bits/c++conf
If I were to write assembly code for large integer calculations (e.g. prime factoring, modulo calculat开发者_如何学Pythonions, etc.) with a focus on speed, which architecture would be best suited for