ASP.net class for common function

I vote 5 for Sandeep Mewara and parmar_punit@yahoo.co.in. The reason for vote 5 for parmar is because of its simplicity and works correctly. My vote of 5 for Sandeep Mewara is because his concept works great too. Following are the explanations.

Dictionary is a simple and nice idea, but what if some users add _sl.Add("@MyHeart", lovepulse);. If this should not happen then the caller should know the table structure prior . What a tight coupling?

But a object model gives a defined contract. Somebody misunderstood object model as single object and downvoted Sandeep's answer. Let us have a look at how paramar's and Sandeep's answer together helps in this situation.

Objects have a novel concept Encapsulation

Let us have an object model

 public Interface IInsertableObject
{
    public  SortedList<string,object>  getInsertData()
}
public class CommonObject:IInsertableObject
{
    public string FirstName{get;set;}
    public string LastName{get;set;}
    public int Age{get;set;} 
    public virtual SortedList<string,object> getInsertData()
    {
        // Here you will be having parmar's sorted list created based on the                 
        //object properties. Now this logic is encapsulated and no rubish                 
        //other than object properties are allowed
    }
}
public class ExtendedObjectBasedOnTable:CommonObject
{
    public DateTime birthDate{get;set;}
    public SexEnum Sex{get;set;}
        public overrides SortedList<string,object> getInsertData()
    {
        // Here you will be having parmar's sorted list created based on the                 
        //object properties. Now this logic is encapsulated and no rubish                 
        //other than object properties are allowed
    }
}

So your function will be like

public int Insert(IInsertableObject insertableObject)
{
    SortedList<string,object> insertData=insertableObject.getInsertData();
    //use the sorted list as shown by Parmar.
}
insert(new CommonObject{ set the properties here.....})
insert(new ExtendedObjectBasedOnTable{ set the properties here.....})

So Sandeep's modal (Encapsulation and delegation) + Parmar's logic gives a better solution. The caller doesn't worry about persistance logic, but only need to know which object it can choose to match the parameters it is having. An another layer of factory goes here. But let us not make things further complex for OP.

Good luck

What it sounds like you want to pass 1 to few parameters to a method for inserting data in database.

You need an object model. Create a class (Lets say personal Info). Add the proeprties like firstname, lastname, age, sex, etc to it. Use this object everywhere. Fill the data in it and pass it to the methods. handle the data in the method based on if present or not.

Try!

try this

public int Insert(string firstName, string lastName, int? age, DateTime? datetime, string sex)
    {
        if (!string.IsNullOrEmpty(firstName))
            dCmd.Parameters.AddWithValue("@firstName", firstName);
        if (!string.IsNullOrEmpty(lastName))
            dCmd.Parameters.AddWithValue("@lastName", lastName);
        if (age!=null)
            dCmd.Parameters.AddWithValue("@age", age);
        if(datetime!=null)
            dCmd.Parameters.AddWithValue("@datetime", datetime);
        if (!string.IsNullOrEmpty(sex))
            dCmd.Parameters.AddWithValue("@sex", sex);
    }
Insert("ABC", "", null, null, "");

Initialize all the parameter in the constructor.
Pass all the parameters to the stored procedure.
Call the function from the page creating object of the class, Remove all the parameter in the funtion Insert().
Write the properties in the class. and intialize the properties with the value you like to send.
For Eg. // please ignore syntax error check it in intellisense

public class Sample
{
 //Declare all the fields to be inserted in database
  private string firstName;
  private string lastName;
  private int age;

 public Sample()
 {
   InitFields();
 }

 public void InitFields()
 {
     firstName = string.Empty;
     lastName = string.Empty;
     age = 0;
 }

 public bool Insert()
 {
    SqlConnection conn = new SqlConnection(connStr);
    conn.Open();
    SqlCommand dCmd = new SqlCommand("InsertData", conn);
    dCmd.CommandType = CommandType.StoredProcedure;
    try
    {
         dCmd.Parameters.AddWithValue("@firstName", FirstName);
         dCmd.Parameters.AddWithValue("@lastName", LastName);
         dCmd.Parameters.AddWithValue("@age", Age);
         return dCmd.ExecuteNonQuery();
    }
    catch
    {
         throw;
    }
    finally
    {
         dCmd.Dispose();
         conn.Close();
         conn.Dispose();
    }
 }

  //Properties here
  public string FirstName
  {
        get{return firstName;}
        set{firstName = value;}
  }
  public string LastName
  {
        get{return lastName;}
        set{lastName = value;}
  }
  public int Age
  {
        get{return age;}
        set{age = value;}
  }
}

And from page suppose you do not want to send age you can do it like this on click event

//Create an object of class

Sample obj = new Sample();
obj.FirstName = "ABC";
obj.LastName = "XYZ";
obj.Insert();