c# - Performance. Is it useful to define my own exception types? -


for example, have dll (helper.dll) contains methods working external system through provider library (provider.dll). provider.dll defines systemisdownexception , re-throw in helper.dll. also, have dll (service.dll) uses helper.dll , tons of others, must catch different types of exceptions , process them somehow. question is: affect performance if catch systemisdownexception (from provider.dll) in service.dll? or should define own exception types each exception provider.dll in helper.dll? sorry long question.

do must in logical terms, , don't care performance.

do not design exception types based in performance considerations. create them if find them meaningful , helpful helpfulness , clarity of library.


Comments

Popular posts from this blog

java - activate/deactivate sonar maven plugin by profile? -

python - TypeError: can only concatenate tuple (not "float") to tuple -

java - What is the difference between String. and String.this. ? -