Databases
StackOverflow2013
Postsdbo
POWay to automatically see which functions can potentially return exception in c#
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWay to automatically see which functions can potentially return exception in c#
    primarykey
    data
    text
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USToad
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWay to automatically see which functions can potentially return exception in c#
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWay to automatically see which functions can potentially return exception in c#
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWay to automatically see which functions can potentially return exception in c#
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe link from dariom with the interview of Anders Hejlsberg contained an interesting quote exactly explaining my point: "But that said, there's certainly tremendous value in knowing what exceptions can get thrown, and having some sort of tool that checks. I don't think we can construct hard and fast rules down to, it is either a compiler error or not. But I think we can certainly do a lot with analysis tools that detect suspicious code, including uncaught exceptions, and points out those potential holes to you"
      singulars
      1. POWay to automatically see which functions can potentially return exception in c#
      1. USToad
    2. COFxCop is such a tool, but afaik it doesn't warn you about uncaught exceptions.. quite contrary: http://blogs.msdn.com/fxcop/archive/2006/06/14/631923.aspx
      singulars
      1. POWay to automatically see which functions can potentially return exception in c#
      1. USVVS
    3. COthe article you link too talks about general exception clauses: catch(Exception e) and try to handle it generally. They make the point of specifying the exceptions you want to deal with and let the rest flow. I agree totally, but my point still stands: please point out which exceptions I've missed and actually do not handling. The exception hunter tool seems to do exactly what I need though. I'll have a play with it tomorrow to see what kind of analysis it does and report back here.
      singulars
      1. POWay to automatically see which functions can potentially return exception in c#
      1. USToad
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload