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

Strange symbols ...

1 Answer 15 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Dennis
Top achievements
Rank 1
Dennis asked on 28 Aug 2013, 02:31 PM

 

Howdy,
When decompiled I am occasionally getting these kind of thingees:

 

FamilyDataService._Closureu0024__1192 $VB$Closure_ClosureVariable_4ED_B0 = null;

 

FamilyDataService._Closureu0024__1189 $VB$Closure_ClosureVariable_4B4_C4 =

 

null;

 

 

 

I really have no idea how to explain differently.
dennis

1 Answer, 1 is accepted

Sort by
0
Tsviatko Yovtchev
Telerik team
answered on 29 Aug 2013, 08:47 AM

Hello,

The VB compiler (and all other .NET compilers we are aware of for that matter) generates it's own classes and methods to implement certain language features. These types and methods do not follow the naming rules of the highl level .NET language. They follow MSIL naming rules.

Now, in most of the occasions JustDecompile will be able to recognize why these were created and it will replace them with the .NET language statement taht generated them. Sometimes, however, that will not be possible. Then you'll see these. Also, there's the "Show compiler generated types and members" setting that will make JustDecompile show some of these even if they are correctly replaced with high level code.

Regards,

Tsviatko Yovtchev

Telerik

Tell us what you think about JustDecompile. Your opinion matters! You can use our forum, or our JustDecompile UserVoice website for feature requests.
Tags
General Discussions
Asked by
Dennis
Top achievements
Rank 1
Answers by
Tsviatko Yovtchev
Telerik team
Share this question
or