I\'ve just discovered extension methods and I love th开发者_Go百科em so much that I\'m scared about their good use...
There are so many tutorials that teach us to use for example some ORM directly with database, but in real life i cant remember a big project that was working directly with database and not with servic
Please help on choosing the right way to use the entities in n-tier web application. At the present moment I have the following assembleis in it:
We have a couple of different services for our different apps that are all hosted on the same server. For a solution we are trying to implement now - we want to reuse some code (or methods actually) f
I need to create n-tier application with the following parts: Data server Business logic server Lightweight client with custom features for each customer
I\'m looking for architectural patterns of server-side software, particularly web apps, that have been used for good reason in the real world. Here are some I can think of:
I have a 3 tier ASP.NET MVC开发者_Python百科 3 project that has a data layer, service layer then a presentation layer which calls upon the service layer to get data. I\'m actually using the doFactory
I\'m currently writing an N-Tier architected ASP.NET system with a relatively normalised SQL data开发者_JS百科base backend, but I\'m struggling to get my head around how lookup values should be repres
What are some questions I can ask myself about our design to identify if we should use DTOs or Self-Tracking Entities in our application?
I\'m working on a referral system - the formula is exactly like the pyramid/ponzi scheme. The system works like this:
加载中,请稍侯......