How to encrypt source code before releasing the Application to the public

Question

5.00/5 (1 vote)

See more:

I have just completed developing an application in ASP.NET. i want to release it for the public used.However i don't want the user to view my code and make changes to it. So What is the standard procedure that should be done to the application source code before i release it.

Posted 3-Mar-10 20:37pm

Wanlambok

Add a Solution

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)

Samer Aburabie · Accepted Answer · 2010-03-03T21:17:00

As you are publishing this on ASP.NET I think that your application is an ASP.NET application, therefore I think you copy and paste your application on the IIS with the source code, also this works but it exposes the code to the server users, you should publish your application, right click on your web project and click publish, of which it will generate dlls instead of source code use.

Keep in mind that any .NET application (Web or non-Web) can be reverse engineered, but you can only make it harder to the cracker to reverse it, the process is called obfuscating, of which it encrypts the reverse engineered .NET dlls so the cracker won't understand pretty much of it.