By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,853 Members | 1,563 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,853 IT Pros & Developers. It's quick & easy.

Why compile a Web Application

P: n/a
I've been working with a ASP.Net Web application project and it' ASP-NEt
pages and the classes that you create seems to work without compiling the
project. so my question is: why compile it? The whole thing is then reduced
to a .dll file and i don't wee how you're gonna be using that as a website.
Nov 18 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
If you don't pre-compile it then it just gets compiled on the fly the first
time the page is accesses. Nevertheless, it ALWAYS turns into compiled code
in a DLL. There is no interpreter engine like there was for legacy ASP.

"Jarod_24" <ja******@hotmail.com> wrote in message
news:e7******************************@news.teranew s.com...
I've been working with a ASP.Net Web application project and it' ASP-NEt
pages and the classes that you create seems to work without compiling the
project. so my question is: why compile it? The whole thing is then reduced to a .dll file and i don't wee how you're gonna be using that as a website.

Nov 18 '05 #2

P: n/a
Jos
"Jarod_24" <ja******@hotmail.com> wrote in message
news:e7******************************@news.teranew s.com...
I've been working with a ASP.Net Web application project and it' ASP-NEt
pages and the classes that you create seems to work without compiling the
project. so my question is: why compile it? The whole thing is then reduced to a .dll file and i don't wee how you're gonna be using that as a

website.

If you don't compile it, the web server will, and it will delay the first
request.

DLL's can be easily used in an ASP.NET website, you can just upload them
to the bin folder and it will work.

If you use codebehind, you can even omit the codebehind .vb or .cs
files once they have been compiled. Only the .aspx file and the dll are
needed on the server.
This also helps in keeping your code hidden from your customers.

If you really want to speed things up, you can create a native image
of your dll's with the NGEN utility.

--

Jos
Nov 18 '05 #3

P: n/a

"Jos" <jo***************@fastmail.fm> wrote in message
news:ur*************@TK2MSFTNGP11.phx.gbl...
"Jarod_24" <ja******@hotmail.com> wrote in message
news:e7******************************@news.teranew s.com...
I've been working with a ASP.Net Web application project and it' ASP-NEt
pages and the classes that you create seems to work without compiling the project. so my question is: why compile it? The whole thing is then reduced
to a .dll file and i don't wee how you're gonna be using that as a

website.

If you don't compile it, the web server will, and it will delay the first
request.

DLL's can be easily used in an ASP.NET website, you can just upload them
to the bin folder and it will work.

If you use codebehind, you can even omit the codebehind .vb or .cs
files once they have been compiled. Only the .aspx file and the dll are
needed on the server.
This also helps in keeping your code hidden from your customers.

codebehind?
If you really want to speed things up, you can create a native image
of your dll's with the NGEN utility.
NGEN ?


--

Jos

Nov 18 '05 #4

P: n/a
Jos
"Jarod_24" <ja******@hotmail.com> wrote in message
news:c1******************************@news.teranew s.com...

"Jos" <jo***************@fastmail.fm> wrote in message
news:ur*************@TK2MSFTNGP11.phx.gbl...
"Jarod_24" <ja******@hotmail.com> wrote in message
news:e7******************************@news.teranew s.com...
I've been working with a ASP.Net Web application project and it' ASP-NEt pages and the classes that you create seems to work without compiling the project. so my question is: why compile it? The whole thing is then

reduced
to a .dll file and i don't wee how you're gonna be using that as a

website.

If you don't compile it, the web server will, and it will delay the first request.

DLL's can be easily used in an ASP.NET website, you can just upload them
to the bin folder and it will work.

If you use codebehind, you can even omit the codebehind .vb or .cs
files once they have been compiled. Only the .aspx file and the dll are
needed on the server.
This also helps in keeping your code hidden from your customers.

codebehind?


Codebehind is the technique used by Visual Studio.NET, where the page
contains only the layout and a reference to a codebehind file.
This file (.vb or .cs) contains only the code.
This is as opposed to Web Matrix, which generates so-called inline code,
where the code sits in the aspx file between <script> tags.
If you really want to speed things up, you can create a native image
of your dll's with the NGEN utility.


NGEN ?


A utility that comes with the dotNET framework (the full version, not
the redistributable).

--

Jos
Nov 18 '05 #5

P: n/a
> If you really want to speed things up, you can create a native image
of your dll's with the NGEN utility.


Although you'll probably want to do the NGEN on identical hardware as the
server is using to ensure that you get all of the possible optimizations...

--
Thanks,

Eric Lawrence
Program Manager
Assistance and Worldwide Services

This posting is provided "AS IS" with no warranties, and confers no rights.
Nov 18 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.