Protect ASP.NET source code (aspx)

Asked

Viewed 1,140 times

4

I have a question regarding ASP.NET:

In the case of PHP when an application is placed on the server means to put the source code of the same. In the case of ASP.NET, (specifically C# with pages in .aspx), there is some form of use without exposure of the source code?

If the application is only in C# it is possible to generate the executable, but in the case of ASP.NET, it is possible to separate the working application (in the client, suppose) from the source code?

  • You can generate a Solution Publish.

  • In this case I am using free tools (Visual Studio). Is there this option? - I’ve actually already programmed in C# and I’m thinking about starting (would be a return) with ASP.NET.

  • I think so. Right click on top of your project. If it is Pusblish Web Site

  • You use Web Forms, correct?

  • Are you still starting a project or already have one ready/in progress? If you start, I suggest evaluating the use of MVC with ASP.NET, so all your logic is in the controllers that are in the DLL, only HTML content and little source code is available, in the case feathers if, for, foreach and no business logic.

2 answers

1

To host an ASP.NET application you must publish it first. During publication the source code is compiled and the . Cs files transformed into DLL’s. Therefore, the source code is not exposed as in PHP.

Take a look at how to make a publication here.

  • Excellent response!

0

Is your source code in a separate file . Cs (Code Behind) or is it embedded in Aspx ? In any case, as already mentioned, Visualstudio generates a DLL per page . aspx, carrying its source code is supposedly safe.

I say supposedly because it is possible to decompile the bytecode of the DLL to generate source code in C#, VB.Net etc

If you need an extra level of security, look for shuffle solutions from dll . Net

https://en.wikipedia.org/wiki/List_of_obfuscators_for_.NET

Browser other questions tagged

You are not signed in. Login or sign up in order to post.