1

how to encrypt published dll and ViewFiles to deny End user to convert output files to source files

ahmad khalil
  • 51
  • 7
  • The answer is - `dotfuscate` your files if they go to your end user's hands. But even then, sophisticated user can reflect on them. I wouldn't worry too much because even if user decompiles them, there will still be plenty of work before it can be compiled into working end product. If you deploying it yourself and user only uses your app than don't worry. But definitely sign your assemblies so that someone can't substitute your assembly with the custom one. – T.S. Jan 04 '15 at 04:47

2 Answers2

0

For protecting dlls you can obfuscate them. Obfuscation is the process of renaming this meta-data in an Assembly so that it is no longer useful to a hacker but remains usable to the machine for executing the intended operations. It does not modify the actual instructions or mask them from observation by a hacker. Here is List of obfuscators for .NET and see .NET obfuscation tools/strategy.

Community
  • 1
  • 1
Mohsen Esmailpour
  • 10,476
  • 2
  • 39
  • 64
0

Use Obfuscation as mentioned above. You should also Precompile the web site or embed your views as resources inside the DLL. See ASP NET MVC Embedded Resource Views for more info on that.

Scope Creep
  • 612
  • 5
  • 13