1. There is no absolute protection against both encryption and cracking.
2 developed with vs2002/2003/CodeOnly. dll and. aspx files can be deleted to achieve encryption.
To encrypt. aspx, you can write. aspx code to. CS.
Vs2005 beta1 can be packaged together with. aspx
3 but the DLL can also be decompiled, so the advanced one is to add obfuscators.
However, this is not an absolute way to decompile the obfuscator DLL.
Besides, obfuscation by obfuscators is not always a problem.
4. The ultimate solution is also the most advanced method I know.
Adding Code to the local CPU command is estimated that no one can decompile the local CPU command.
However, I don't think this is necessary, because you think the code is very advanced and someone else may be there n years ago.
How nice it is to come to csdn if you need to communicate with others
Only in this way can we bring a higher level !!!