DbHelper is class which have structure named 'parameters' inside of it,thats ok.

DbHelper.cs

public struct Parameters;

*************************Then pls explain about this block of code**********************

DBHelper oDBHelper = new DBHelper();

DBHelper.Parameters[] colParameters = null;

colParameters = new DBHelper.Parameters[] ;

{

       new  DBHelper.Parameters(parametrename, parametrevalue)),

      new  DBHelper.Parameters(parametrename1, parametrevalue2)),

    like this  we can add  any no .of parameters

}

*******************************************

my understanding is  'colParameter' is an array of type structure 'parameters',is it correct??

please expalin in detail about above code block.

what key word  'new' will do.

 Hi,

You are right  if you say

DBHelper.Parameters[] colParameters = null;

colParameters = new DBHelper.Parameters[] ;

That means  its collection of new DBHelper.Parameters[] ; .

When you say

new DBHelper.Parameters[] ;

It will create new object of type DBHelper.Parameters and store it in this collection.

to create new instance of an object we use new key work.

Hope this helps.

Hi sridharakrishna,

The reason for this may be:

Because structures are simply an inline area of memory, they cannot be null, and so the CLR has to be able to ensure that the area of memory is totally initialized rather than being partly garbage. For this reason, you'll often hear the 'constructors' on structures called (arguably more correctly) 'initializers' because they don't construct an object they just initialize an area of memory.

You can't define a default initializer because the CLR has an intrinsic understanding of structures and automatically zeroes out the required amount of memory for a default structure.

When you define a non-default initializer, C# requires you to set all fields because it skips the zeroing of memory and lets you initialize it.

--------------------------------------------------------------

Another way: Structures can be used without any constructors, but if all the public properties exposed by the structure have get methods only and no set methods, then you will need some mechanism to set its value, and constructors might be it.

Is struct really the right thing for this case?  Are you really expecting copy-by-value behavior for your Parameter objects?  From the code posted I would expect copy-by-reference behavior which indicates that the struct declaration could lead to confusion in the future.