Obfuscating enum names when enum is .ToString()'d

• 
  I'm sorry it looks like we had been totally unresponsive when dealing with this issue. I think the problem is that, behind the scenes, .NET uses Reflection voodoo to knock up a string representation of an enum, and SmartAssembly will usually blow the assembly metadata to bits as part of the obfuscation and I can see how this would be one side-effect.
  
  If you want the string representation of this enum to be ("X"), maybe telling the enum to derive from the type long and using ((long)MyEnum).ToString("X")

  Brian Donahue May 18, 2011 04:36

  - 0 +
• 
  I'd also like to add I could not reproduce the problem with the given code using obfuscation and pruning.

  using System;
  using System.Collections.Generic;
  using System.Text;
  
  namespace ConsoleApplication1
  {
      class Program
      {
          static void Main(string[] args)
          {
              Test t = new Test();
              t.GetCandy();
              Console.ReadLine();
          }
      }
      public class Test
      {
          enum Candy
          {
              JollyRancher = 0x01,
              ReesesPieces = 0x02
          }
          public void GetCandy()
          {
              Candy candy=Candy.JollyRancher;
              Console.WriteLine(candy.ToString());
          }
      }
  }
  

  However, from my miniscule understanding of the SmartAssembly code, I think you should be safe if you use the FlagsAttribute on the enum because there seems to be an exclusion in the SA obfuscation rules for that.

          [Flags]
          enum Candy
          {
              JollyRancher = 0x01,
              ReesesPieces = 0x02
          }
  

  Hopefully this works for you.

  Brian Donahue May 18, 2011 08:28

  - 0 +
• 

  Brian Donahue wrote:

  If you want the string representation of this enum to be ("X"), maybe telling the enum to derive from the type long and using ((long)MyEnum).ToString("X")

  
  That's exactly what I do to get SmartAssembly obfuscating the names properly.
  
  I have not tried the [Flags] attribute as an alternative fix.
  
  Thanks for the reply.

  CodeGuru May 18, 2011 11:30

  - 0 +
• 
  Did applying the "Flags" attribute fix the problem?

  Brian Donahue May 20, 2011 12:36

  - 0 +

Add comment

Please sign in to leave a comment.