G
Guest
It seems like, the way ASP.NET 2.0 works, I should be able to build a
pre-compiled version of my site so that none of the code of the site would be
accessible by the people for whom I developed it.
If I've built a site in VS 2005 that has lots of ASPX files, a few ASCX
files, both with .CS code-behinds, and a bunch of class files in the APP_CODE
directory, is there a way to "build" the site and obscure it's files and
parts as much as possible?
My primary desire is to pre-compile all of the .CS code-behind files and
APP_CODE class files. But I'd even like it if the ASPX files themselves were
somehow pulled in. From what I've read, the objects that are JIT compiled in
ASP.NET do actually include the body of the ASPX HTML as well, right? So is
there a way to "deploy" the site without even including the ASPX text files?
Alex
pre-compiled version of my site so that none of the code of the site would be
accessible by the people for whom I developed it.
If I've built a site in VS 2005 that has lots of ASPX files, a few ASCX
files, both with .CS code-behinds, and a bunch of class files in the APP_CODE
directory, is there a way to "build" the site and obscure it's files and
parts as much as possible?
My primary desire is to pre-compile all of the .CS code-behind files and
APP_CODE class files. But I'd even like it if the ASPX files themselves were
somehow pulled in. From what I've read, the objects that are JIT compiled in
ASP.NET do actually include the body of the ASPX HTML as well, right? So is
there a way to "deploy" the site without even including the ASPX text files?
Alex