How about Data Access Application Block

[ad]

I want to develop DataBase application.

How about Data Access Application Block?
Is it useful?

 

[Peter Bromberg [MVP]]

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

 

[Ryan LaNeve]

I want to develop DataBase application.

How about Data Access Application Block?
Is it useful?

Definitely, and the newer "Enterprise Library" release is even better.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/entlib.asp

Good luck,
Ryan LaNeve

 

[ad]

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?

 

[Sean Hederman]

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?

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