One Issue on FxCop
One rule about catching exceptions is that you should catch a specific exception rather than a general one such as Exception or SystemException. With this rule, FxCop will show a critical error if you catch an Exception or a SystemException.
I'd like to catch an Exception in one case. If I write try/catch blocks, I first try to catch specific exceptions. In some cases, I'm not sure if my specific exceptions cover all the exceptions and I don't want that an uncovered exception faults out the method. In that kind of cases, I catch an Exception as my final catch. Breaking the rule like this is very useful if my method is in an infinite loop.
I'd like to see that FxCop treats my cases differently. If FxCop finds an Exception or SystemException, then it should check if a specific exception is catched before the general catching. If it does, then FxCop should display a warning instead of a critical error.
1 Comments:
montre pas cher, moncler outlet, moncler, karen millen, moncler, supra shoes, ugg pas cher, wedding dresses, swarovski, moncler, sac louis vuitton pas cher, doudoune canada goose, moncler, louis vuitton, pandora charms, canada goose, ugg,uggs,uggs canada, swarovski crystal, marc jacobs, hollister, moncler, toms shoes, louis vuitton, ugg boots uk, louis vuitton, canada goose uk, coach outlet, louis vuitton, moncler, canada goose, pandora charms, links of london, moncler, canada goose, canada goose outlet, pandora jewelry, juicy couture outlet, canada goose, thomas sabo, juicy couture outlet, pandora jewelry, bottes ugg, canada goose outlet, ugg,ugg australia,ugg italia, replica watches
Post a Comment
<< Home