Code security

[~Phil~]

Is there a way to encrypt/hide the source content of the code element of the XXXX.aspx.vb ASP.NET project when deploying on a customers web server?

[anupam kant]

While deploying the asp.net application you do not need to give .vb file, you only need to give .aspx pages, js files, images etc and an assembly. (i.e. before deploying the application, build the solution in visual studio .net IDE, this will create application assembly in project's bin folder, now deploy all the files but .vb/ .cs files)


hope this helps :)

[~Phil~]

anupam,
Thanks for your help I understand now.
Cheers Phil

[TheCPUWizard]

Well...There are pros and cons to using a pre-compiled code-behind [aka DLL]

Pro: You do not need to give out the source

Con: If you need to replace the DLL once the site is running, all sessions will be immediately terminated without prejudice as soon as you copy the new DLL in. [If you deploy the source level and make a minor tweak to the aspx page, then you can upgrade the source and sessions will begin to use it as they are created.

This can be an important detail for sites that need 100% uptime and do not have any idle time for doing upgrades..


ps: 99%+ of the time deploying the DLL is the way to go, but it is NOT an absolute!