RE: .NET and keeping my source code to myself...

From: Kevin Yu [MSFT] (v-kevy_at_online.microsoft.com)
Date: 03/18/05


Date: Fri, 18 Mar 2005 02:58:40 GMT

Hi Mitchell,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you need to obfuscate your assembly to
prevent others disassembly into source code. If there is any
misunderstanding, please feel free to let me know.

Visual Studio .NET 2003 has provided us with a tool called Dotfuscator.
Dotfuscator is an obfuscator for .NET assemblies.

Dotfuscator is completely non-intrusive and requires no changes to your
source code, making it the most natural way to protect your intellectual
property on the .NET platform. In addition, many of the elements within the
Dotfuscator family of .NET packaging tools make unprecedented steps towards
smaller and faster .NET applications. Dotfuscator combines a mix of
well-known and novel algorithms to allow customers to produce the best .NET
applications possible.

For more information, please check the following link:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dotfuscator
/dotf3e5x.asp

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."



Relevant Pages

  • Re: sorry i didnt saw your reply :)
    ... which uses the SQL assemblies. ... What version of Dotfuscator are you using? ... "Are you trying to obfuscate the signed assembly SqlServerCe?" ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Obfuscation question
    ... Dotfuscator application where you can specify not to obfuscate namespaces ... If you don't specify not to rename that then other assembly referencing the ... shipping assemblies have been signed and obfuscated, ...
    (microsoft.public.dotnet.languages.csharp)
  • Dotfuscated DLLs
    ... the same run so they use the same symbol references and are therefore ... I obfuscate these assemblies just like ... AFAIK, however, Dotfuscator doesn't support this. ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: Dotfuscator and strong names
    ... You can't delaysign the assembly, obfuscate it, and then re-sign it? ... "Strong named assemblies are digitally signed. ... Since Dotfuscator modifies the assembly, it is essential that signing ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Dotfuscator disassociates derived class when base class is lin
    ... I tried Dotfuscator in the early days I think way back in .NET 1.1 and could ... never get it to behave and I think many other developers have found the same ... any dependency assemblies the input assembly is dependent on. ... obvioously this then defeats the purpose of obfuscation. ...
    (microsoft.public.dotnet.framework.compactframework)