2

Hoora! Finally it's finished... and now I'm going to sell it to some customers...

However, as you know, published view files are completely visible. Things get worse about our .js external code files, and indeed the .dll file of the project itself.

I know that one good approach is to use tools like Smart Assembly, However can I use those tools for ASP.NET MVC projects and files? Is there a better approach?

Majid
  • 13,097
  • 15
  • 74
  • 110
Amin Saqi
  • 17,857
  • 7
  • 47
  • 69

1 Answers1

1

Once you package up your files and give them to a customer, what happens to these files is out of your control. Just about anything you can do could be reverse engineered, decompiled or unencrypted.

Your best bet is to protect your assets legally by producing a robust license agreement between your company and your customers. You can then make your customers aware in the terms and conditions that any reproduction or modification of your work is illegal, you can then later pursue them legally for damages.

Other than that, obfuscating your code and compiling your views would help a bit.

Adrian Thompson Phillips
  • 6,573
  • 6
  • 35
  • 63