How can I protect / obfuscate / etc the source code of an ASP.NET MVC application during deployment?

I had a good experience recently developed using ASP.NET MVC, and I am considering using it for a project that appears at work. However, one important consideration: they sell source licenses separately, as a rule, and this is an application that we cannot really connect to our own hosting without cutting off a large chunk of the potential market.

Can I distribute an ASP.NET MVC application without source code? Or is there a pretty effective (obviously not perfect, but at least it doesn't β€œsteal me”) and a safe tool or method for obfuscating MVC applications? I tried a couple of obfuscators that supposedly work with ASP.NET, but they broke the application due to MVC depending on specific file / directory names.

+4
source share
1 answer

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.

+7
source

Source: https://habr.com/ru/post/1299595/


All Articles