asp.net sqlhelper data Access Layer Use _ Practical skills

This article mainly introduces the use of SqlHelper.
Every project needs to use the data access layer, I do is no exception, but I make the data access layer into a stand-alone project, there is no great purpose, the data access layer, just do data access, does not contain any logic.

Why use the data access layer?
If you do not use the data access layer, then your code will appear a lot of SqlConnection, SqlCommand, SqlDataReader, Open, close ... These classes and methods, and the amount of code is very large, let you annoying, and the code written, in fact, are physically active, no technical content. So we need to encapsulate the data access layer for easy reuse. Microsoft has done the work for us, that is sqlhelper, the following diagram is the SqlHelper class diagram:

Here's how I use this.

Executes a stored procedure that has no return value:
create proc P_delete@id int
As
Delete table1 where id= @id

This is a stored procedure that deletes data, and only one sentence is invoked: Sqlhelper.executenonquery (Sqlhelper.conn, "P_delete", id); The ID here is type int, Rather than the SqlParameter type. The call is the public static int ExecuteNonQuery (string connectionString, string spname, params object[] parametervalues) method that is invoked. Analogy Returns a DataSet type: SqlHelper.ExecuteDataset (Sqlhelper.conn, Pro, parameter list); parameters are also passed directly without constructing SqlParameter ... Well, this article is mainly to introduce a small skill, is params object[] use method, let the master laughed at