Public properties of merged DLLs don't get obfuscated

• 
  Could you have any of these properties labelled as "internals-visible-to "?

  Chris.Allen April 30, 2014 06:16

  - 0 +
• 
  No, they aren't labelled that way.

  claus.net April 30, 2014 06:25

  - 0 +
• 
  Put smartassembly in debug mode and we can inspect the resulting log. It shouls tell us why it has excluded anything form obfuscation.
  
  
  http://documentation.red-gate.com/displ ... rtAssembly

  Chris.Allen April 30, 2014 08:26

  - 0 +
• 
  I generated the log.
  
  The relevant properties aren't listed in the log file.
  
  
  The only entries for a relevant class (as an example) I could find in the log are the following:
  
  2014-04-30 15:19:05,045 TRACE SmartAssembly.ObfuscationAnalyzer: Method [NAMESPACE]NAMESPACE.Accommodation::instance System.Void .ctor(valuetype [mscorlib]System.Guid) excluded from obfuscation: RtSpecialName
  
  2014-04-30 15:19:05,045 TRACE SmartAssembly.ObfuscationAnalyzer: Method [NAMESPACE]NAMESPACE.Accommodation::instance System.Void .ctor() excluded from obfuscation: RtSpecialName
  
  The properties of "Accommodation" stay public and don't get obfuscated.

  claus.net April 30, 2014 10:41

  - 0 +
• 
  So, my reading of this is that smartassemlby has excluded this from processing simply because it has been labelled with rtspecialname- indicating it has significance at the global level.
  
  If you look at the IL for that method- has it been labelled with rtspecialname?

  Chris.Allen May 01, 2014 08:50

  - 0 +
• 
  Yes, the two constructors are labelled with "rtspecialname".
  
  Nothing else in the class, though.

  claus.net May 05, 2014 08:11

  - 0 +
• 
  Are there any updates on this? We're having the exact same issue, our merged assembly is still marked as public.

  RobotGizmo May 26, 2014 14:18

  - 0 +

Add comment

Please sign in to leave a comment.