Geek asks and answers

Is it possible to implement trial restrictions in an ASP.net application?

I have an ASP.NET application that we provide to our customers for their deployment on our web server and use it. My concern is that all of my source code on the .aspx pages is open and our clients can open the .aspx / cs file and see the code in it.

I want to protect my code from a Windows application by complying with the trial version restrictions for 15-20 days. On the other hand, the source code must have some third-party DLL, so when they try to deploy a new assembly, it will be available only for a limited period of time.

Terms of payment with our client: first source code, and then payment. Therefore, I think that between them there is that faith on both sides remains as it is. How can i do this?

+5
source share
3 answers

Publish your web application so that all the code behind the files is compiled into a dll. Thus, they cannot easily see your code. However, they will be able to use reflection to see the code using tools like jetBrains dotPeeek.

The best option. Take the site yourself, but since this does not answer your question, here are some other options.

1st option

If the client insists on hosting the site because he agrees with the ownership of the data, then allow them to host the site and the database, but use the functionality from a centralized website that you control. You can even provide api.

- web.config, . :

  • -
  • ,
  • postsalt

- ssl.

- . , . , .

Google , -, google goi, .

- - , .

- - , .

, - , .

, , . , -.

, , .

web.config:

  • -,
  • .

, , .

Opion 2 3 -, .

=====================================

, , , , . , - .

+2

DotFuscator Community Edition - , , , .

. , Google. ( .)

0

.NET Reactor Intellilock..NET Reactor , aspx , , . Intellilock . , ASPX, , .

: http://www.eziriz.com/

0

More articles:


All Articles