ExceptionFinder for Reflector

Source code checked in, #15394

jasonrbock — Sat, 30 Aug 2008 19:16:30 GMT

got IsDocumented flag working

Source code checked in, #15354

jasonrbock — Thu, 28 Aug 2008 13:58:33 GMT

Adding finding exceptions in documentation (seems to have slowed down the stress test even more :( ), now need to update the flags

Source code checked in, #15342

jasonrbock — Thu, 28 Aug 2008 02:02:29 GMT

Got LeakedException in...now need to work on parsing Documentation and gettting IsDocumented populated...

Source code checked in, #15337

jasonrbock — Thu, 28 Aug 2008 00:21:45 GMT

Added a LeakedException type to track documented ones...

Source code checked in, #15334

jasonrbock — Thu, 28 Aug 2008 00:00:53 GMT

Working on a IsDocumented property feature for leaked exceptions...

Created Issue: Remove AnalyzerTests.cs

jasonrbock — Wed, 27 Aug 2008 16:30:17 GMT

These tests have direct dependencies on mscorlib. Test cases should go against code I generate. Remove this file and ensure code coverage is high and logic paths are hit.

Source code checked in, #15316

jasonrbock — Wed, 27 Aug 2008 02:03:26 GMT

Mostly bug fixes, like newobj IS a method call :). Still chugging along...

Source code checked in, #15301

jasonrbock — Tue, 26 Aug 2008 04:32:55 GMT

Added tests for removing exceptions from LeakedExceptionsCollection

Source code checked in, #15299

jasonrbock — Mon, 25 Aug 2008 23:10:45 GMT

Added tests to up the coverage a bit (it's around 83%)

Source code checked in, #15297

jasonrbock — Mon, 25 Aug 2008 21:31:21 GMT

Got more coverage around throwing exceptions from arguments and fixed a bug where NOPs were in between the throw opcode and the opcode that got the exception on the stack

Created Issue: Add Method Hyperlinks

jasonrbock — Mon, 25 Aug 2008 17:58:19 GMT

For each leaked exception, provide a way in the UI to let the user click on a node so they can go right to the method in the main Object Browser tree view.

Created Issue: Show Call Tree

jasonrbock — Mon, 25 Aug 2008 17:57:07 GMT

For each location where a leaked exception was found, provide a call tree node list that shows the call sequence that gets from the selected method to the place in code where the leaked exception is generated.

Created Feature: Bold Leaked Exceptions Reported in XML Comments

jasonrbock — Mon, 25 Aug 2008 17:55:48 GMT

XML comments allow a method to define <exception> sections. For all of the found leaked exceptions, bold those in the treeview that the method reports that could be thrown.

Source code checked in, #15291

jasonrbock — Mon, 25 Aug 2008 17:19:39 GMT

Fixed a bug where the wrong type was being reported as the exception (return type from a method that creates the exception was the problem).

Source code checked in, #15288

jasonrbock — Mon, 25 Aug 2008 14:15:45 GMT

Changed the UI to show exception and non-exception lists. Need to up the code coverage on tests now...

Source code checked in, #15275

jasonrbock — Sun, 24 Aug 2008 20:39:18 GMT

Working on getting the leaked exceptions broken out into lists: Exception-based and non-exception based. Need to review results...esp. for stress tests

Source code checked in, #15233

jasonrbock — Fri, 22 Aug 2008 16:37:05 GMT

Working on ensuring non-Exception types do not enter into the list (that's a serious analysis bug) and two tests are failing because of this change...but I didn't want to lose the work...fixes will be coming shortly...

Source code checked in, #15221

jasonrbock — Fri, 22 Aug 2008 00:27:07 GMT

Started work on stress tests - nice for ensuring core code runs against all methods in a well-known assembly (e.g. mscorlib.dll).

Source code checked in, #15220

jasonrbock — Fri, 22 Aug 2008 00:11:58 GMT

Updated the UI to be a little more friendly (doesn't auto-analyze on every method node selection), and started to mess with Test List Editor (for stress testing...)

Source code checked in, #14481

jasonrbock — Tue, 15 Jul 2008 15:48:42 GMT

Added assembly loading, was causing a problem with assemblies in another directory and not finding types w/in that assembly because .NET wasn't "aware" of them.