Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. .NET (Core and Framework)
  4. .NET Reactor Code Protection

.NET Reactor Code Protection

Scheduled Pinned Locked Moved .NET (Core and Framework)
4 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    dybs
    wrote on last edited by
    #1

    I have some libraries and apps written in C++/CLI and C#, and I'd like to obfuscate/protect the source somehow. I've seen a lot of you say how it's a waste of time, and I know there's no silver bullet here. I'm not looking to make it impossible to decompile my software, just more difficult. In particular, I'd like my source to be un-viewable with .NET Reflector and other similar tools. Reflector makes it dead easy to decompile .NET apps, and any developer with 1/1000 of a brain could figure it out. If someone really wants to decompile my code, they should at least have 3/4 of a brain ;P I read a thread here awhile back about code protection and saw someone recommend .NET Reactor[^]. I've been experimenting with the trial and so far it seems to do what I want - I can't view the implementation of any functions, and the names of all my private members and functions come up as non-printable characters. However, I can still plainly see all the class and public function and property names (but not their implementations). I'd like to obfuscate everything, including all public information, but if I do that, then any app that tries to use the protected library throws a TypeLoad exception (or something like that). I tried emailing their support a couple of days ago, but I haven't heard back yet. Has anyone had any luck with .NET Reactor? Or, if anyone knows of a better tool with a decent price tag (free / open source is always great :) ), I'm open to alternatives. Thanks, Dybs

    G J 2 Replies Last reply
    0
    • D dybs

      I have some libraries and apps written in C++/CLI and C#, and I'd like to obfuscate/protect the source somehow. I've seen a lot of you say how it's a waste of time, and I know there's no silver bullet here. I'm not looking to make it impossible to decompile my software, just more difficult. In particular, I'd like my source to be un-viewable with .NET Reflector and other similar tools. Reflector makes it dead easy to decompile .NET apps, and any developer with 1/1000 of a brain could figure it out. If someone really wants to decompile my code, they should at least have 3/4 of a brain ;P I read a thread here awhile back about code protection and saw someone recommend .NET Reactor[^]. I've been experimenting with the trial and so far it seems to do what I want - I can't view the implementation of any functions, and the names of all my private members and functions come up as non-printable characters. However, I can still plainly see all the class and public function and property names (but not their implementations). I'd like to obfuscate everything, including all public information, but if I do that, then any app that tries to use the protected library throws a TypeLoad exception (or something like that). I tried emailing their support a couple of days ago, but I haven't heard back yet. Has anyone had any luck with .NET Reactor? Or, if anyone knows of a better tool with a decent price tag (free / open source is always great :) ), I'm open to alternatives. Thanks, Dybs

      G Offline
      G Offline
      Giorgi Dalakishvili
      wrote on last edited by
      #2

      Xenocode is nice.

      Giorgi Dalakishvili #region signature My Articles Asynchronous Registry Notification Using Strongly-typed WMI Classes in .NET [^] My blog #endregion

      D 1 Reply Last reply
      0
      • G Giorgi Dalakishvili

        Xenocode is nice.

        Giorgi Dalakishvili #region signature My Articles Asynchronous Registry Notification Using Strongly-typed WMI Classes in .NET [^] My blog #endregion

        D Offline
        D Offline
        dybs
        wrote on last edited by
        #3

        Xenocode definitely looks like a great tool (especially being able to integrate the .NET Framework components into the binary), but it's a bit pricey for us. If anyone knows of something under $1000, that would be great. It's hard to compete with .NET Reactor's price tag of only $280 for a company-wide license. Or is this a case of "you get what you pay for"? Thanks, Dybs

        1 Reply Last reply
        0
        • D dybs

          I have some libraries and apps written in C++/CLI and C#, and I'd like to obfuscate/protect the source somehow. I've seen a lot of you say how it's a waste of time, and I know there's no silver bullet here. I'm not looking to make it impossible to decompile my software, just more difficult. In particular, I'd like my source to be un-viewable with .NET Reflector and other similar tools. Reflector makes it dead easy to decompile .NET apps, and any developer with 1/1000 of a brain could figure it out. If someone really wants to decompile my code, they should at least have 3/4 of a brain ;P I read a thread here awhile back about code protection and saw someone recommend .NET Reactor[^]. I've been experimenting with the trial and so far it seems to do what I want - I can't view the implementation of any functions, and the names of all my private members and functions come up as non-printable characters. However, I can still plainly see all the class and public function and property names (but not their implementations). I'd like to obfuscate everything, including all public information, but if I do that, then any app that tries to use the protected library throws a TypeLoad exception (or something like that). I tried emailing their support a couple of days ago, but I haven't heard back yet. Has anyone had any luck with .NET Reactor? Or, if anyone knows of a better tool with a decent price tag (free / open source is always great :) ), I'm open to alternatives. Thanks, Dybs

          J Offline
          J Offline
          jmcc2k
          wrote on last edited by
          #4

          Crypto Obfuscator is a cost-effective and powerful alternative.

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups