Best practice for n-tier data access in .NET 2.0

  • Thread starter Thread starter Paul Aspinall
  • Start date Start date
P

Paul Aspinall

Hi
I've previously constucted my .NET 1.1 data access, via a Data Access Layer
(DAL), that was all in code.

Now that I have access to the DataSet control in .NET 2.0, I'm looking for
opinions or pointers into how to implement a DAL under .NET 2.0. Is it best
to use controls or code?? Are there any best practice code samples around?

Thanks


Paul
 
Hello Paul,

You need to find differences between ADO 1.1 and ADO 2.0 that allow to impove
you DAL
see http://www.dotnetbips.com/articles/displayarticle.aspx?id=47 and http://msdn.microsoft.com/msdnmag/issues/05/04/ADONET/default.aspx

BTW, there are no changes in building DAL components with .net 2.0, all changes
are specific to language (for example using generic to create type-safe collection,
dataset binary seriliazation and etc)


PA> Hi
PA> I've previously constucted my .NET 1.1 data access, via a Data
PA> Access Layer
PA> (DAL), that was all in code.
PA> Now that I have access to the DataSet control in .NET 2.0, I'm
PA> looking for opinions or pointers into how to implement a DAL under
PA> .NET 2.0. Is it best to use controls or code?? Are there any best
PA> practice code samples around?
PA>
PA> Thanks
PA>
PA> Paul
PA>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch
 
Paul,

In fact there is in mainlines nothing changed. If you had used in 1.1 the
component to create your DAL with a strongly typed dataset, than you would
have had almost the same effect as is now with 2.0, which does that
automaticly for you.

A pity was that all documentation in 1.1 was showing to do it direct on the
form instead on that so nice component in 1.1.

Just my thought,

Cor
 
Back
Top