This is a migrated thread and some comments may be shown as answers.

Sometimes code says base.Method(...) when it should be this.Method(...)

1 Answer 20 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Michael E
Top achievements
Rank 1
Michael E asked on 28 Apr 2011, 10:19 PM
Nice work guys, looks like this tool is going to come along well.

Found the first bug though, the class System.Runtime.CompilerServices.ConditionalWeakTable doesn't really have a proper base class but the decompiled code wants to call it anyway, as you can see in the provided screenshot.

Sure it's just a little thing, so I was just worrying it might get overlooked. ;-)

1 Answer, 1 is accepted

Sort by
0
Accepted
Ricky
Telerik team
answered on 29 Apr 2011, 09:43 AM
Hi Michael,

Thanks again for sending the issue. Yes you right that there should not be a "base" keyword for  CreateEntry call since ConditionalWeakTable do not have a base class, therefore expect a fix for that in the coming build.

Should you find any more issues, please don't hesitate to write  us back.

Kind Regards,
Ricky
the Telerik team

Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>

Tags
General Discussions
Asked by
Michael E
Top achievements
Rank 1
Answers by
Ricky
Telerik team
Share this question
or