We are building a LOB Thick WPF Client / WCF Server application. I need to create an architecture that allows \"pluggable\" workflows on the Client side, to facilitate a business selling point of per
My ORM is generating objects reflecting the database table structure. This objects are extensible, so I\'m able to add new properties and methods. This objects do not contains any persistence logic,so
Our web application is deployed in a web farm (more than 20 servers). The site has a huge traffic (millions of page viewsper day).
Since ADO.Net uses a \'disconnected\' model where the data available to a single program is just a copy of what i开发者_JS百科s in the database, what is the normal way to handle multiple programs need
Scenario: * A user uploads an image and enters some information about that image * Information and image get uploaded (to all servers)
I have some entities like: Customers, Orders, Invoices. For each one of them I grouped their CRUD operations and few other in interfaces like: ISvcCustomerMgmt, ISvcOrderMgmt, ISvcInvoicesMgmt, ISvc
I know that domain logic should be placed into domain objects. But what if my domain logic needs data from the database ? (e.g. checking unique value, computed values.. etc ) I think injecting reposit
If you were going to reimplement SO now, what technologies would you use?What technologies would you use if you were restricted to Java technologies开发者_运维技巧.And here\'s the answer I was writing
We are in the process of choosing a way to isolate our .NET client applications from a SQLServer database and we are leaning toward the DevForce ORM.
So I\'ve got a solution that contains a few big projects, which I\'m trying to break down into smaller projects with more isolated responsibilities. This is a game, but I\'m mainly a LOB developer and
加载中,请稍侯......