C
CBN Media
Hi,
We have a ASP.NET application with most of the business logic in stored
procedures, and custom components etc.
We're looking of some way to protect this code when we deploy our
application on the client's server. I remember I read somewhere about
wraping your application in one (or more) DLLs that you install so the
client doesn't actually has access to the code. What happens to the aspx
pages? The client still have access to his web server = he has access to the
aspx pages.
Now, I try to keep everything in CodeBehind pages but can those be
protected, wrap in a DLL?
Any suggestions or references very appreciated,
Thank you,
Cezar
We have a ASP.NET application with most of the business logic in stored
procedures, and custom components etc.
We're looking of some way to protect this code when we deploy our
application on the client's server. I remember I read somewhere about
wraping your application in one (or more) DLLs that you install so the
client doesn't actually has access to the code. What happens to the aspx
pages? The client still have access to his web server = he has access to the
aspx pages.
Now, I try to keep everything in CodeBehind pages but can those be
protected, wrap in a DLL?
Any suggestions or references very appreciated,
Thank you,
Cezar