Create Data layer Class

I did not give you any examples. I suggested that you read articles that explain how to create a complete DAL Class. As Mahesh indicates, it is not possible to create one class that will do everything; you need to somehow generate code that is customized for each table and for each query. The articles will explain how to use the tools that Microsoft has provided that makes it extremely easier than in the past. In the past, it would have required much more coding and required much more time and there was much more to learn. You still must learn though.

The answer is Yes and No.

No means, it's not a simple task. Every table has different name, column names, types and so on. So you can't just create a class that deals with all the tables.

YES! means, you can create a generic class called DBHelper that will execute SQL queries etc. So this class can have a method called ExecuteSQL that takes a SQL statement. In your code, you can create a SELECT statement, DELETE or UPDATE or any other SQL statements and call that statement using this class. 

I have also seen some code where all SQL statements are generated from XML files. You just have to update the XML but that's just too much!

Ok here is some thing i wrote regarding Login using store procedure remaining try your self

using System;
using System.Collections.Generic;
using System.Linq;
using System.Configuration;
using System.Text;
using System.Data.SqlClient;
using System.Data;
namespace DAO
{
    public class Login
    {
        private string m_strUserName;
        private string m_strPassword;
        private SqlCommand m_oCmd;
        private SqlDataReader m_oDR;
        private SqlConnection m_oConn;
        private DataSet m_oDataSet;
        private bool m_bFlag = false;

        public string UserName
        {
            get
            {
                return m_strUserName;
            }
            set
            {
                m_strUserName = value;
            }
        }

        public string Password
        {
            get
            {
                return m_strPassword;
            }
            set
            {
                m_strPassword = value;
            }
        }

        public Login()
        {
            this.m_oCmd = new SqlCommand();
            this.m_oConn = new SqlConnection();
            this.m_oDataSet = new DataSet();
        }

        public bool Authenticate()
        {
            m_bFlag = false;
            m_oConn = new SqlConnection(System.Configuration.ConfigurationManager.ConnectionStrings["LocalSqlServer"].ConnectionString);
            try
            {
                if (m_oConn.State != ConnectionState.Open)
                {
                    m_oConn.Open();
                }
                m_bFlag = false;
                m_oCmd = new SqlCommand("uspLogin", m_oConn);
                m_oCmd.Connection = m_oConn;
                m_oCmd.CommandType = CommandType.StoredProcedure;
                m_oCmd.Parameters.AddWithValue("@UserName", UserName);
                m_oCmd.Parameters.AddWithValue("@Password", Password);
                m_oDR = m_oCmd.ExecuteReader();

                if (m_oDR.Read())
                {
                    m_bFlag = true;
                }
            }
            catch (SqlException oSqlEx)
            {

            }
            finally
            {
                m_oConn.Close();
            }
            return m_bFlag;
        }

    }
}

In aspx page on button you should write like this

DAO.Login objLogin = new DAO.Login();

protected void btnLogin_Click(object sender, EventArgs e)
    {
        objLogin.UserName = txtUsername.Text;
        objLogin.Password = txtPassword.Text;

        if (objLogin.Authenticate())
        {
            Response.Redirect("User.aspx");
        }
        else
        {
            lblInvalid.Visible = true;
        }
    }

Thanks for the answer, it's good example but i need only an completed DAL Class that Depend on Stored procedure

Have a look at the articles in this web site. Look at the right side of this window for "Our recommended articles"; there are some good choices there, but there are many other articles that will help.

The "3 Tier Archtecture" is popular. Also using "Entites" is the new thing.