I really have no idea how to explain differently.
1 Answer, 1 is accepted
answered on 29 Aug 2013, 08:47 AM
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.