I had a client ask for advice building a simple WPF LOB application the other day. They basically want a CRUD application for a database, with main purpose being as a WPF training project.
So as I understand it with good loose coupling I should be able to swap out my DAL with a couple lines of code at the application root.
We can speed up a hibernate app easyly with 2nd level cache using infinispan or ehcache/开发者_如何学编程terracotta,... but ibatis only have a simple interface to implement for caching. And hibernate
In my SOA architecture, I have several WCF services. All of my services need to access the database. Should I create a specialized WCF service in charge of all the database access ?
I currently have an asp.net web application which is using seperate assemblies for the data access, the business logic,
Can anyone suggest a simple Data Acces开发者_JAVA百科s Layer (C# .NET)? Not keen on using the Microsoft Application Data Access block, seems very bloated and overkill. Also don\'t want to use LINQ to
Given a stored procedure, is there a way 开发者_Go百科to auto generate a Data access layer? I understand that this can be done using Codesmith by creating cs templates, but was wondering if there\'s a
I would like to ask whether or not is a good practice, to hold the CRUD operations for business objects, in 开发者_开发百科a single domain service class. Should we provide a domain service class for e
Suppose we are developing class which implements simple CRUD operations for working with DB. This class also maintain cache for increasing performance.
If I use ADO.NET Entity Framework in our project and we depend on a 3-layer architecture pattern that we have ( presentation layer - business layer - data access layer ) a project for each layer.
加载中,请稍侯......