C# Decompiler - Is it possible !!!
-
Hi, We all know that Java can be decompiled back to source, is the same going to happen for C# too. How is MS going to prevent this("Is it necessary" is a different qn). Is there gonnu be a obfusticator for .NET too. Any ideas. Cheers KayKa
-
Uh... Is there anything that prevents 'people' from ripping my code? How good does the decompiled stuff look - how much of the original is retained? e.g. All internal function names & arguments? decompiling optimized C++ code creates rather obfuscated 'sources'. But if you get 'readable' sources back - woudln't this drive most companies away from developing for .NET? At least, drive them away from using .NET for desktop applications. (I still doubt the Internet is ALL the future
-
Uh... Is there anything that prevents 'people' from ripping my code? How good does the decompiled stuff look - how much of the original is retained? e.g. All internal function names & arguments? decompiling optimized C++ code creates rather obfuscated 'sources'. But if you get 'readable' sources back - woudln't this drive most companies away from developing for .NET? At least, drive them away from using .NET for desktop applications. (I still doubt the Internet is ALL the future
I think the 'decompiler' Chris is talking about is the ILDASM tool which decompiles your managed code to IL. I've looked at IL and it's like glorified assembly so if you're not worried about someone reading your code in assembly then I'm not sure you have to sweat IL.
-
I think the 'decompiler' Chris is talking about is the ILDASM tool which decompiles your managed code to IL. I've looked at IL and it's like glorified assembly so if you're not worried about someone reading your code in assembly then I'm not sure you have to sweat IL.
Hello! There has been very live discussions about this topis at DeveloperMentor DOTNET maillist. See at the following threads... "Protecting assemblies from reverse-engineering" (http://discuss.develop.com/archives/wa.exe?A2=ind0009a&L=dotnet&F=&S=&P=25833) Intellectual Property? http://discuss.develop.com/archives/wa.exe?A2=ind0009d&L=dotnet&F=&S=&P=839 "Legality of ILDASM" http://discuss.develop.com/archives/wa.exe?A2=ind0009e&L=dotnet&F=&S=&P=3783 IL is on more high level than x86 assembler and reverse engineering code from IL is really should be no big deal. There is good decompilers from Java jvm bytecode, so there will be (no doubt) decompilers from IL to C# or to VB.Net, too. One of possible solution is good obsfucator... Or MS will add some kind of encryption... It seems that this is big issue for creators of commercial components or libraries. Slavo
-
Hi, We all know that Java can be decompiled back to source, is the same going to happen for C# too. How is MS going to prevent this("Is it necessary" is a different qn). Is there gonnu be a obfusticator for .NET too. Any ideas. Cheers KayKa
I would imagine that there will eventually be some kind of decomplier. But since all the new MS languages (with the exception of unmanaged C++) compile down to the same IL(theoretically), who knows what it will decompile to? My guess is that it will be more of a dissasembler that breaks the IL down into something human more readable, but probably not source code. -Mik