1) In a situation where you describe where you distribute the code to business objects for placement on your servers, this is more a legal problem than a technical one. While you can deter casual attacks and change the economies of serious ones, a determined attacker will not hold back even with the best obfuscation available to you.
2) Keep in mind that you may cause inconvenience to your genuine customers. Many .NET developers use a decompiler as part of their normal development workflow, and obfuscating a thread can have a performance impact.
3) If, after realizing this, you still feel that the main protection with closed doors is worth the Crypto Obfuscator , ASP.NET MVC may get confused.
source share