Linked Questions

Is it better to do this: try { ... } catch (Exception ex) { ... throw; } Or this: try { ... } catch (Exception ex) { ... throw ex; } Do they do the same thing? Is one better ...

I'm wondering what the correct way is to pass on an exception from one method to another. I'm working on a project that is divided into Presentation (web), Business and Logic layers, and errors (e.g. ...

Given the following statements: try { ... some code ... } catch { ... some cleanup code ... throw; } and try { ... some code ... } catch (Exception ex) { ... some cleanup code ......

I have a query handler decorator which logs any exceptions: public class QueryHandlerLogDecorator<TQuery, TResult> : IQueryHandler<TQuery, TResult> where TQuery : IQuery<TResult>...

I'm curious to find out what the best practice is for caught exceptions that aren't used. The irony is that this is going against best practice in the first place. I've found myself in a position to ...

I am developing a program for my final project of college that consists of taking several SQL scripts from a fixed folder and executing them. In a meeting with my project supervisor he said that it ...

Possible Duplicate: .NET - Throwing Exceptions best practices Hi, I have seen people re-throwing exceptions as given below. which one is optimal? Why one mechanism is optimal than the other one. ...

What are key words from throw exeption like this? public void methodOne() throw SomeExeption { try{ doSomething(); catch(SomeExeption se) { throw se; } } public void ...

I am calling, through reflection, a method which may cause an exception. How can I pass the exception to my caller without the wrapper reflection puts around it? I am rethrowing the InnerException, ...

while maintaining my colleague's code from even someone who claims to be a senior developer, I often see the following code: try { //do something } catch { //Do nothing } or sometimes they write ...

What is the difference between try { ... } catch{ throw } and try{ ... } catch(Exception e) {throw new Exception(e.message) } regardless that the second shows a message.

This is a follow-up question to Is there a difference between “throw” and “throw ex”? is there a way to extract a new error handling method without resetting the stack trace? [EDIT] I will be trying ...

I've got a class that calls a SOAP interface, and gets an array of data back. However, if this request times out, it throws an exception. This is good. However, I want my program to attempt to make ...

We have a service which will log unhandled exceptions at the app domain level (via Log4net). We logged: 2014-01-28 16:49:19,636 ERROR [49] FeedWrapperService - unhandled System....

internal static string ReadCSVFile(string filePath) { try { ... ... } catch(FileNotFoundException ex) { throw ex; } catch(Exception ex) { ...