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. How to avoid .Net exe from decompilation

How to avoid .Net exe from decompilation

Scheduled Pinned Locked Moved .NET (Core and Framework)
csharptutorialquestionworkspace
9 Posts 6 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.
  • G Offline
    G Offline
    GauravKP
    wrote on last edited by
    #1

    Hi, i am working on c# .net windows environment. While developing the application i realized that the application .exe that installs in Destination machine i.e C:\Program Files\Application Folder .. is easily DE-COMPILED By application like .Net Reflector. My question that is it possible to the Application .exe so that it can't decompiled by reflector (or other software).Is the procedure to make it possible is simple or requires some Special Practices. Thanks

    N L P 4 Replies Last reply
    0
    • G GauravKP

      Hi, i am working on c# .net windows environment. While developing the application i realized that the application .exe that installs in Destination machine i.e C:\Program Files\Application Folder .. is easily DE-COMPILED By application like .Net Reflector. My question that is it possible to the Application .exe so that it can't decompiled by reflector (or other software).Is the procedure to make it possible is simple or requires some Special Practices. Thanks

      N Offline
      N Offline
      Not Active
      wrote on last edited by
      #2

      The short answer to this very common question is no. You can't prevent a .net application or assembly from being decompiled. The best you can do is use an obfuscator to cloud the issue a bit.


      I know the language. I've read a book. - _Madmatt

      D 1 Reply Last reply
      0
      • N Not Active

        The short answer to this very common question is no. You can't prevent a .net application or assembly from being decompiled. The best you can do is use an obfuscator to cloud the issue a bit.


        I know the language. I've read a book. - _Madmatt

        D Offline
        D Offline
        Dimitri Witkowski
        wrote on last edited by
        #3

        In one of my projects I have used the following technique: some function bodies were encrypted, and the IL in it was decrypted on-the-fly, just before you enter into this function. You can implement something like it too, it's not too hard.

        Die Energie der Welt ist konstant. Die Entropie der Welt strebt einem Maximum zu.

        N 1 Reply Last reply
        0
        • G GauravKP

          Hi, i am working on c# .net windows environment. While developing the application i realized that the application .exe that installs in Destination machine i.e C:\Program Files\Application Folder .. is easily DE-COMPILED By application like .Net Reflector. My question that is it possible to the Application .exe so that it can't decompiled by reflector (or other software).Is the procedure to make it possible is simple or requires some Special Practices. Thanks

          L Offline
          L Offline
          Lost User
          wrote on last edited by
          #4

          You can also try using a type name longer than 4096 characters, it messes with some reversing tools..

          H 1 Reply Last reply
          0
          • D Dimitri Witkowski

            In one of my projects I have used the following technique: some function bodies were encrypted, and the IL in it was decrypted on-the-fly, just before you enter into this function. You can implement something like it too, it's not too hard.

            Die Energie der Welt ist konstant. Die Entropie der Welt strebt einem Maximum zu.

            N Offline
            N Offline
            Not Active
            wrote on last edited by
            #5

            Why don't you submit an article on this technique. I'm sure others would find it interesting.


            I know the language. I've read a book. - _Madmatt

            1 Reply Last reply
            0
            • G GauravKP

              Hi, i am working on c# .net windows environment. While developing the application i realized that the application .exe that installs in Destination machine i.e C:\Program Files\Application Folder .. is easily DE-COMPILED By application like .Net Reflector. My question that is it possible to the Application .exe so that it can't decompiled by reflector (or other software).Is the procedure to make it possible is simple or requires some Special Practices. Thanks

              P Offline
              P Offline
              PIEBALDconsult
              wrote on last edited by
              #6

              Trying is generally not worth the trouble.

              1 Reply Last reply
              0
              • L Lost User

                You can also try using a type name longer than 4096 characters, it messes with some reversing tools..

                H Offline
                H Offline
                hammerstein05
                wrote on last edited by
                #7

                Are you a developer I would fall out with? Types with names longer than 4096 characters. It wouldn't just be decompilers it would mess with.

                L 1 Reply Last reply
                0
                • H hammerstein05

                  Are you a developer I would fall out with? Types with names longer than 4096 characters. It wouldn't just be decompilers it would mess with.

                  L Offline
                  L Offline
                  Lost User
                  wrote on last edited by
                  #8

                  It wouldn't have to be in the source, just in the assembly And the C# compiler sets a maximum length of 512 characters anyway..

                  1 Reply Last reply
                  0
                  • G GauravKP

                    Hi, i am working on c# .net windows environment. While developing the application i realized that the application .exe that installs in Destination machine i.e C:\Program Files\Application Folder .. is easily DE-COMPILED By application like .Net Reflector. My question that is it possible to the Application .exe so that it can't decompiled by reflector (or other software).Is the procedure to make it possible is simple or requires some Special Practices. Thanks

                    L Offline
                    L Offline
                    Lost User
                    wrote on last edited by
                    #9

                    You can go for "WinLicense" software to protect and manage license of your .NET code. See details from following link. http://www.oreans.com/winlicense.php[^] Hope this will help!

                    Jinal Desai

                    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