Strange symbols ...

2 posts, 0 answers
  1. Dennis
    Dennis avatar
    1 posts
    Member since:
    Aug 2013

    Posted 28 Aug 2013 Link to this post


    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 =






    I really have no idea how to explain differently.

  2. Tsviatko Yovtchev
    Tsviatko Yovtchev avatar
    549 posts

    Posted 29 Aug 2013 Link to this post


    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.


    Tsviatko Yovtchev


    Tell us what you think about JustDecompile. Your opinion matters! You can use our forum, or our JustDecompile UserVoice website for feature requests.
Back to Top