is there any way of developing aspx pages in dreamweaver MX and converting it to dll/exe so that people cant modify the code on the local server(this local server can be opened by anyone coz there is no IT personnel for support)

any other way of protecting the pages on the local server so that no-one(including the administrator) can open or view the file/folder containing the pages.

i really dont want to use visual studio thats why ...

For proctecting the pages on the local server,deny permissions for the user accounts listed in the Security Tab.This way you can prevent them from opening the page or folder and modifying.

Please don't cross post. See this thread.

someone hacking the server is not the main issue ... every user on the network has equal access + the server is left logged in & open physically to anyones use 24/7 in administrator mode .. ..the server is remotely monitored and i cant make modifications on the users account .. i cant change any of the current user policies as any changes will have to go through lot of permissions seeking & paper-work crap from parent company hq'd in several other countries .. its made in such a way so that any user from any country plugged on to this network can access the server easily ... dont ask me why it is done like that coz i've absolutely no idea ...

i use the template management of dreamweaver extensively .. and so im used to making pages in dreamweaver .. as for compiling to dll's usin' vs.net isnt it sumthing like u have to make/design the aspx page in vs.net itself ??

PS: sorry abt the cross post .. but it was actually intended for general.net

Can you clarify what you want to protect? I'm clear from reading both topics whether you want to protect the ASPX source files, or you want to prevent users from doing certain things in the browser.

You do not need to use Visual Studio to build ANY .NET application. That's one of the greatest things about it, the .NET framework includes a command line compiler. You can write the whole thing in Notepad if you so choose.

I believe there is a way to compile the actual ASPX pages into the binary, then when the application is deployed, you deploy "stub pages" which are .ASPX files that don't contain anything (or very much at least). The framework handles everything for you. I don't recall the name of this process, or remember where I have seen it, so you'll need to do a bit of research. (Also, I hope I'm not getting confused with this feature in the 2.0 beta version of .NET. It may not exist in 1.0.)

i wanted to protect the aspx pages source from being modified or viewed by anyone .. the intranet server is open and anyone can do anything on it .. so what i want is a way of protecting the source from being modified(its ok if someone deletes files but modifying them can cause real problems).. and if possible protect them from being deleted by human errors or whatever .. :-)

if u can point me to anything solid regarding this it wud be helpful ... im not familiar with .net beta 2 .. so u'll havto be a bit more specific ...

so that wud be
1)protect aspx from being modified/edited by converting them to dlls/exes or whatever
2)stop people from deleting the folder/file of the aspx on WInNT server without making any changes to its user policies/logins
(I want both of the above)

Even if you have compiled the ASPX pages (code behind) into DLL's.. you can still mess with the ASPX stub pages and write anytihng in them you want.

If all users have all rights to the physical machine, you can't protect what's on it.

As with yor other thread- your can't protect files without changing access. THe users would need to be denied access to the folders through security rights.

If your company is associated/parented/located in the US- I'd be very concerned with how they have things set up. It's surely not SOX compliant.


Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee

talk abt compliance with anything ... such a huge company with a min of 369 networks .. each with atleast 15pcs(max 350) .. i dont know whats going on & they dont expect to help me either as i dont fall under their current it-department ... so im kind'f helpless & having all these out-of-the-norms qs ..

u told abt not being able to protect the aspx pages completely .. now what if i want to protect only the code for accessing my db & controlling access .. ?

Let's try this again: If users have "admin" access on the physical box you can't protect it. There is nothing to stop someone from opening up the .DLL or .EXE and editing that. AFter all, it's only in IL - which humans can read and modify.

The only way to stop it is to secure the folder using the Operating system rights. You need to do what you do and raise the issue with management and let them know of the risks. It's their problem then.


Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee