How to automatically encrypt asp.net project before publish

Question

1.00/5 (3 votes)

See more:

Hi guys
I'm developer and create web application with Asp.net MVC and use publish to upload project output in web server.
How to encrypt all dll files in bin folder before publish project

Posted 24-Jul-15 7:36am

mir5

Updated 24-Jul-15 7:37am

v2

Add a Solution

Comments

[no name] 24-Jul-15 13:47pm

What is it that you think encrypting DLLs on a web server are going to do for you? Before you could use them you would have decrypt them.....

Wendelius 24-Jul-15 14:06pm

That's an extremely good question.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2015-07-24T08:10:00

You can't encrypt executables - they need to be decrypted before they are loaded, so it just isn't practical, especially in a web environment.

You could obfuscate them - google will help you there - but it probably isn't needed provided your site security is up to scratch anyway. Remember that server code (and that includes all your DLL files) is executed on the server and never gets anywhere near the client. So you are much better off putting effort into ensuring that your server file system is well locked down - which you need anyway to protect the key you would have to use to decrypt the DLLs - rather than pending significant time protecting something that is not user accessible anyway.