How about Data Access Application Block

  • Thread starter Thread starter ad
  • Start date Start date
A

ad

I want to develop DataBase application.

How about Data Access Application Block?
Is it useful?
 
Why don't you try it out? I use it for most all data access. Also helps to
standardize coding style across multiple developers.
My 2 cents!
Peter
 
I have tried it, it is some great!
I have a question:
When we use ADO.NET, we must open a connection before use
Command.ExecuteReader() to get a DataReader, and then close the conneciton
after go throught the DataReader.
When we use Data Access Application Block, we can use
SqlHelper.ExecuteReader to get a DataReader.
Do we need to close a connection after that?
 
ad said:
I have tried it, it is some great!
I have a question:
When we use ADO.NET, we must open a connection before use
Command.ExecuteReader() to get a DataReader, and then close the conneciton
after go throught the DataReader.
When we use Data Access Application Block, we can use
SqlHelper.ExecuteReader to get a DataReader.
Do we need to close a connection after that?
Click to expand...

You don't have to close the connection in either case, but it is good
practise if you're using connection pooling
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

DataTable load is blocking application 6
Caching block from multiple domains 4
Application Blocks 5
How to use EMAB in n tier Application 2
Advice on Buying book for Enterprise Library - January 2006 release 1
DAAB 2.0 Vs DAAB in Enterprise Application blocks 3
Data Access Application Block with C# 3
Fugaku supercomputer develops superior covid faceshield. 3

Back
Top