@Tanjoodo: I think he means it's good practice to be a bit more specific about the exceptions you want to catch and let other exceptions throw, as the code is right now, a unexpected exception would just be swollowed in the catch.
when we do testing we test a class at a time, so all external stuff is either stubbed or mocked so that you just test the functionality of the single class instead of doing system wide testing that are a nightmare to maintain. and if you test every single
layer and it behaves as you expect while testing than everything should be good atleast from the code standpoint.
I can see alot of places where we can use this while doing ASP.NET at least.