throw e basically destroys the call stack, while throw maintains it. throw essentially forwards the current exception.
Unless you want to erase previous stack trace and exception information, you should use throw instead of throw e.
Use throw e only when you're creating a new exception that optionally wraps the original e. E.g.
throw new YourOwnAppException("Something went terribly wrong", e);
Cheers,
Imar
---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of
ASP.NET 2.0 Instant Results and
Beginning Dreamweaver MX / MX 2004
Want to be my colleague? Then check out this post.