Overlapping identifiers for attributes, methods and enums of a class

• 
  .NET Reflector only ever generates names for local variables. It tries to infer their names from usage or their types, so I'd say it's unlikely for it to generate names like "a", "b", "c". Names of namespaces, enums (and their fields), classes, fields, properties, methods (and their parameters), local functions (and their parameters) are always contained in assembly's metadata. We simply read them from the assembly, they're never generated.
  
  Is the assembly obfuscated?
  

  Russell D August 07, 2020 11:58

  - 0 +
• 
  Hi, actually it does generate this code. Is there any way for me to analyze this more in detail?

  pkess August 11, 2020 11:33

  - 0 +
• 
  I think that shared names are invalid in C# code but valid in compiled metadata, so it sounds like the assembly was post processed (obfuscated) by some application. Reflector unfortunately just produces code with names taken from the metadata.
  
  Are you able provide us some examples? 
  

  Russell D August 12, 2020 13:35

  - 0 +
• 
  I think it will not be possible to post those assemblies here. If there is any way to have a look in those metadata i can inspect it for you.

  pkess August 12, 2020 13:43

  - 0 +
• 
  Hi, 
  A support ticket has been created for you.  Via the support ticket, I will send an email message to you with a URL link for you to upload the requested assemblies for us to inspect.
  
  Many Thanks
  Eddie

  Eddie D August 26, 2020 11:46

  - 0 +
• 
  Thank you for uploading your dll file for us to investigate.  We will update this post once we have further information to pass to you.
  
  Many Thanks
  Eddie

  Eddie D August 27, 2020 10:04

  - 0 +

Add comment

Please sign in to leave a comment.