Validating input parameters

[sourabh]

Hi
I have a basic qus. I am writing a middle-tier component. I have constructor
which takes 3 inputs, here's how it looks
internal ClassName(Datab ase dbToUse, Int64 pk,DateTime Date)

{

}

Now , i want to know should I validate all the inputs before i start using
them, and if so in case of an invalid error whats the best way to report
error. Here on invalid input if I dont initialize the object and return, it
would return a object without any valid fields / memebrs.

Whats th general practice for these type of implementations . Is it feasible
to throw an exception?

-Sourabh

[Benny Mathew]

Throw the exception and catch it outside of the object.

-benny

sourabh wrote:

Hi
I have a basic qus. I am writing a middle-tier component. I have constructor
which takes 3 inputs, here's how it looks
internal ClassName(Datab ase dbToUse, Int64 pk,DateTime Date)

{

}

Now , i want to know should I validate all the inputs before i start using
them, and if so in case of an invalid error whats the best way to report
error. Here on invalid input if I dont initialize the object and return, it
would return a object without any valid fields / memebrs.

Whats th general practice for these type of implementations . Is it feasible
to throw an exception?

-Sourabh

[Kristofer Gafvert]

If the parameters were not what you expected them to be, throw an exception.
Yes, you should validate the parameters, unless you really know that they
will always be what you expect them to be.

--
Regards,
Kristofer Gafvert - IIS MVP
http://www.ilopia.com - When you need help!
"sourabh" <so************ @induslogic.com > wrote in message
news:eG******** ******@TK2MSFTN GP10.phx.gbl...

Hi
I have a basic qus. I am writing a middle-tier component. I have constructor which takes 3 inputs, here's how it looks
internal ClassName(Datab ase dbToUse, Int64 pk,DateTime Date)

{

}

Now , i want to know should I validate all the inputs before i start using
them, and if so in case of an invalid error whats the best way to report
error. Here on invalid input if I dont initialize the object and return, it would return a object without any valid fields / memebrs.

Whats th general practice for these type of implementations . Is it feasible to throw an exception?

-Sourabh

[sourabh]

Thanks
"Kristofer Gafvert" <kg******@NEWSi lopia.com> wrote in message
news:ei******** ********@TK2MSF TNGP10.phx.gbl. ..

If the parameters were not what you expected them to be, throw an exception. Yes, you should validate the parameters, unless you really know that they
will always be what you expect them to be.

--
Regards,
Kristofer Gafvert - IIS MVP
http://www.ilopia.com - When you need help!
"sourabh" <so************ @induslogic.com > wrote in message
news:eG******** ******@TK2MSFTN GP10.phx.gbl...

Hi
I have a basic qus. I am writing a middle-tier component. I have

constructor

which takes 3 inputs, here's how it looks
internal ClassName(Datab ase dbToUse, Int64 pk,DateTime Date)

{

}

Now , i want to know should I validate all the inputs before i start using them, and if so in case of an invalid error whats the best way to report
error. Here on invalid input if I dont initialize the object and return,

it

would return a object without any valid fields / memebrs.

Whats th general practice for these type of implementations . Is it

feasible

to throw an exception?

-Sourabh

[Daniel Jin]

I think that if you are developing with a layered architecture, it's always best to do validation when data is collected. my middle tier typically assumes that data would be valid coming in. however, you definitely should but in debug or trace assertions to test the validity of data, so if a problem occurs, you can quickly pinpoint where the problem is

----- sourabh wrote: ----

H
I have a basic qus. I am writing a middle-tier component. I have constructo
which takes 3 inputs, here's how it look
internal ClassName(Datab ase dbToUse, Int64 pk,DateTime Date

Now , i want to know should I validate all the inputs before i start usin
them, and if so in case of an invalid error whats the best way to repor
error. Here on invalid input if I dont initialize the object and return, i
would return a object without any valid fields / memebrs

Whats th general practice for these type of implementations . Is it feasibl
to throw an exception

-Sourab

[Ben Dewey]

When validating parameters of this kind the convention is to use.

either:
ArgumentExcepti on
ArgumentNullExc eption
or
ArgumentOutOfRa ngeException

"sourabh" <so************ @induslogic.com > wrote in message
news:eG******** ******@TK2MSFTN GP10.phx.gbl...

Hi
I have a basic qus. I am writing a middle-tier component. I have constructor which takes 3 inputs, here's how it looks
internal ClassName(Datab ase dbToUse, Int64 pk,DateTime Date)

{

}

Now , i want to know should I validate all the inputs before i start using
them, and if so in case of an invalid error whats the best way to report
error. Here on invalid input if I dont initialize the object and return, it would return a object without any valid fields / memebrs.

Whats th general practice for these type of implementations . Is it feasible to throw an exception?

-Sourabh