.NET Framework Bookmark and Share   
 index > Common Language Runtime > Prevent Decompile
 

Prevent Decompile

Hi all,
I have a application that written with C#. I know that there are some tools to decompile DLL, EXE file. How to prevent decompiling for security. What's the way to protect source code in .NET.
Please help me. Thank you very much.
quocvuong2005

.NET FrameworkSDKdoesn't include obfuscator tool. There's a dotfuscator community editionshipped as part of Visual Studion (2003, 2005 and 2008), but it is most probably part only of commercialVisual Studioversions and not part of Express versions.

You can try to search ".NET obfuscator free" in your favourite search engine (http://search.live.com/results.aspx?q=.NET+obfuscator+free)

There are 2 interestinglists of obfuscators for .NET I know about:

Karel Zikmund
Run this Google query.
nobugz
Thank you for your reply.
I have found some tools to protect source code, but we have to pay money for these tools.
Are there a way to protect source code by .NET code ?

quocvuong2005

.NET FrameworkSDKdoesn't include obfuscator tool. There's a dotfuscator community editionshipped as part of Visual Studion (2003, 2005 and 2008), but it is most probably part only of commercialVisual Studioversions and not part of Express versions.

You can try to search ".NET obfuscator free" in your favourite search engine (http://search.live.com/results.aspx?q=.NET+obfuscator+free)

There are 2 interestinglists of obfuscators for .NET I know about:

Karel Zikmund
Thank you for your reply
quocvuong2005
Why you want your code should n't be seen by some one?
does it contain some terrorist messages ;)
Santhosh V

You can use google to search for other answers

Custom Search

More Threads

• Some basic questions on .NET
• making CAB archive
• Defining an enum the hard way
• Clipboard Viewer
• Properties.Settings: Where are they saved?
• Unhandled w32 exception in multithreading
• String by ref i C++ old syntax
• need API or .NET function to get current user access level
• VS 2008 Beta 2: Loaded assembly is ignored and AssemblyResolve isn't invoked
• Reflection and security issues