1 No absolute protective encryption and cracks are relative
2 Remove the code for VS2002 / 2003 / development. CS / .vb file only. CS / .aspx can reach encryption to encrypt .aSPX can write .aspx code to write .csvs2005 beta1 can be connected .aspx
3 But the DLL can also be refused to compile, so advanced is to join the obfuscator but is not absolute or can be confused with the obfuser and confusing the obfuscator.
4 Ultimate Solution is also the most advanced method I know to add code to the local CPU instruction. No one can refactivate the local CPU instruction.
However, I don't think there is anything because you feel very high-profile code may have more people who will communicate with others. You need to come to 9CBS. How can you only bring a higher realm! ! !
