@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.
|Tech Off||Which OOP books would you recommend to read, to better understand the concept?||12||Jul 27, 2006 at 10:16AM|
|Coffeehouse||Vista "Basic" UI update... whyyy??||9||Jul 20, 2006 at 9:31AM|
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.
I think its because of the load it would put on the server, hosting the code. And for most debugging you would not need to look into the .net source code so I understand their choice.
I would however hope you can enable it always loading with the download version that is going to come out.