|
-
May 12th, 2003, 08:56 AM
#1
Thread Starter
Member
code protection
Is it possible to protect your ASP.net code with a password, so other people cannot edit yor code even if they have VS.net?
So that over enthusiastic 'superusers' and 'system administrators can not edit my code, and cause a lot of errors and damage, I have to clean up eventually .
Krol
-
May 12th, 2003, 09:32 AM
#2
Hyperactive Member
Do you mean securing the ASPX pages? Since most of your business logic and secret code will
be in the DLL in the bin folder, there's no need to deploy the VB files.
This is similar to legacy ASP where developers would script their own DLLs as a way of hiding code.
-
May 12th, 2003, 09:47 AM
#3
Thread Starter
Member
Perhaps a stupid remark but, does the deployment program create this dll?, because all my code (secret code as you wish)
is in my aspx files.
Is the webdeployement program also
available in the standard edition?
Krol
-
May 12th, 2003, 10:14 AM
#4
Frenzied Member
Use code behind. The code will be compiled into a dll, so unless someone has your project files, they wont be able to edit your code.
-
May 12th, 2003, 10:14 AM
#5
PowerPoster
Re: code protection
Originally posted by krol
Is it possible to protect your ASP.net code with a password, so other people cannot edit yor code even if they have VS.net?
So that over enthusiastic 'superusers' and 'system administrators can not edit my code, and cause a lot of errors and damage, I have to clean up eventually .
Krol
Well, first, if you are talking pre-deployment, you can use something lik sourcesafe where you check in and out the source files to work on. I am pretty sure you can roll back any changes you need.
Next, you seem to be creating your asp.net apps the same way as old asp. By that I mean you are including your programming logic within the html of the page. You shouldn't really do this now that we have code behind files available to us. When you write your code in these code behind files, all your classes can be compiled into a dll and will be called when needed. It is faster because the dll will get further compiled after the first use, and there is no interpreting going on unless you still utilize late binding.
Should get you started going in the right direction:
http://www.4guysfromrolla.com/webtech/100500-1.shtml
-
May 12th, 2003, 10:22 AM
#6
Thread Starter
Member
thanks, I am going to studie the pages your hyperlink refers to.
I am realy learning a lot from this site!!!!
Thanks,
Krol
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|