[ssamiev]

I have been using C# not so a long time when I found that a code compiled using MSIL would be easily disassembled
in Visual Studio 2008 Professional Edition using it's Tools like ildasm.exe (it stands for Intergrated Language Disassembler). When I compiled my dll and deployed my application, a friend of mine asked me how did I wrote my
code there and told me to optimize my algorithms. Then I asked him when did he get my source codes ? And he asked :
I cracked!
Finally after googling I found that it's easy to decompile .NET assemblies as they do not generate specific CPU
instructions but MSIL code that then with help of Jet Compiler will be translated into specific platform. Then I decided search for .NET security and found Preemptive DotFuscator that obfuscate .NET assemblies.

And my Visual Studio 2008 comes with a trial version of Preemtive Dotfuscator and I wanted to obfuscate my application during building of my project it echoes an error and says smth like this;

Error ildasm.exe returned 1

Has anyone used dotfuscator b4 and I like to know your experience in this issue please!

Please share you experience on securing .NET assemblies...

Thank you all in advance

[FlashM]

So you're saying that it is possible to decompile an assebly and get a code like:

public void SomeMethod(int a, int B)
{
    int result = a + b;
    MessageBox(result);
}

[ssamiev]

Exactly!
When you use DotFuscator it then obfuscates your app and makes it not human readable and also safe for recompiling !

[FlashM]

I didn't know this is possible... I did use ildasm before, but it doesn't give you the complete code... Will have to try this :-)

[ssamiev]

Try Preemtive Dotfuscator!!!

[IvanFerrer]

I had the same problem (ilasm returned 1) and it was because I was trying to obfuscate a pre-obfuscated exe.
I mean: once I obfuscated the exe file for the first time, I copied it to his project folder to test it in his context.
After that, I changed some Dotfuscator options and Generated again. This second time it was trying to obfuscate the previously obfuscated exe at the project folder.
My fail, of course.