c# - What exception should be thrown when validation fails? -


we have create operation runs validation on entity passed in. if entity not valid, exception should thrown?

initially, going throw applicationexception, after research seems incorrect: (from article on msdn):

x not throw or derive applicationexception.

should create custom exception , inherit applicationexception?

is there exception exists in .net framework should using?

or maybe, should not throw exception @ all?

i not sure...

some more detail:

in specific case, create method create address change request. business rules state there can 1 address change request @ time. validation error can come 1 of 2 scenarios:

  1. a property of entity not set, or set incorrect value

  2. an address change request exists.

you should throw invalidargumentexception


Comments

Post a Comment

Popular posts from this blog

Java sticky instances of class com.mysql.jdbc.Field aggregating -

i noticed (via jmap+jhat) app leaking storing many instances com.mysql.jdbc.field  class - double checked code make sure closing preparedstatements, find few missing didn't change outcome. - preparedstatement created , closed right away - several others created @ start , reused many times - using org.apache.tomcat.jdbc.pool.datasource connection pool what can cause type of behavior? are closing of preparedstatements / result sets using: preparedstatement stmt (possible assignment here); try { // work prepared statement resultset rs; try { while (rs.next()) ... // process results } { rs.close(); } } { stmt.close(); } so guarantee result sets closed when finished (regardless of exceptions) , statements closed (regardless of exceptions)? there other ways write that, idea same. if you're doing of properly, unless have many references it's taking inordinate amount of memory, it's ok , nothing needs done it.
Read more