This link has been bookmarked by 76 people . It was first bookmarked on 25 Oct 2006, by someone privately.
-
03 Oct 10
-
23 Dec 08
-
30 Nov 07
-
29 Oct 07
-
04 Oct 07
-
12 Sep 07
-
07 Sep 07
-
31 Aug 07
-
22 Aug 07
-
27 Jul 07
-
26 Jul 07
-
20 Jul 07
-
If you can spend 90% less time (yes, I said "90% less time") on developing data access code, then quality time can be spent improving the domain model and tuning performance
-
control over all aspects of data-loading behavior
-
proper amount of judicious, architectural forethought, NHibernate is quite possibly the most maintainable solution
-
the domain and data layers could be placed into physically separate assemblies; e.g., Project.Core and Project.Data, respectively. The domain layer (the Project.Core assembly) would contain domain objects and DAO interfaces. The data layer (the Project.Data assembly) would contain concrete implementations of the DAO interfaces defined in the domain layer.
-
pag
-
-
15 Jul 07
brianschroerThis article describes best practices for leveraging the benefits of NHibernate 1.2, ASP.NET, generics, and unit testing together.
-
11 Jul 07
-
05 Jul 07
-
28 Jun 07
-
07 Jun 07
-
29 May 07
-
12 May 07
-
04 May 07
-
03 May 07
-
15 Apr 07
-
14 Apr 07
-
10 Apr 07
Jose M AragonThis article describes best practices for leveraging the benefits of NHibernate 1.2, ASP.NET, generics, and unit testing together.
-
09 Apr 07
-
07 Apr 07
-
04 Apr 07
-
29 Mar 07
-
27 Mar 07
-
19 Mar 07
-
15 Feb 07
-
29 Jan 07
-
21 Dec 06
-
12 Nov 06
-
08 Nov 06
-
25 Oct 06
-
18 Oct 06
-
11 Sep 06
-
02 Aug 06
-
05 Jun 06
-
24 May 06
-
28 Apr 06
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.