In response to the

last post
,
Rod Howarth
brought up the related topic of
source code obfuscation
for a .NET assembly. He says:

Reflector is certainly a useful tool, and it’s good to delve into both your own code and other namespaces. It can greatly assist
with understanding code and also disaster recovery, in the case of lost source files.

A related topic is
obfuscation,
as the first thing that one thinks about when you realize that your DLL file is easily convertible back to source code is the
possible loss of intellectual property.

Codecall

and the

Microsoft .NET Support Team

have quick tutorials about dotfuscator, which comes with Visual Studio. There are also a number of 3rd party tools.

Xenocode Postbuild

and

CodeVeil

are a couple of names I’ve heard used.


Comments

2 responses to “Obfuscation”

  1. Here’s the post I wrote when I looked into this (nearly) a couple of years ago – things may have changed since, of course.
    http://through-the-interface.typepad.com/through_the_interface/2007/01/more_on_ip_prot.html
    Kean

  2. Hi Kean,
    Thank you for the pointer, and glad to see you are having a look now and then!
    Jeremy

Leave a Reply

Discover more from Autodesk Developer Blog

Subscribe now to keep reading and get access to the full archive.

Continue reading