Global.asax - Code Behind or Inline?
 

Hi All,

I've just noticed that there seem to be two ways of setting up a global.asax
file.

At http://www.csharphelp.com/archives/archive206.html the global.asax
example has Application_Start etc within <script runat="server"> ...
</script> tags, whereas VS.Net creates a global.asax.cs file that is
presumably pre-compiled like a .aspx.cs file.

Am I correct in assuming that global.asax works just like a .aspx, ie there
is a Code Behind model and an Inline model, and the programmer has an open
choice between the two, depending on a trade-off between speed (compiled
Code Behind) versus the maintainability of not having to recompile after
changes (Inline)?

And presumably, as with inline .aspx pages, does an inline global.asax get
compiled when the first page of the application is hit?

TIA,

JON

RE: Global.asax - Code Behind or Inline?
 

hi ,
yes you are right global.asax can be both inline and codebehind .

regards
ansil

"Jon Maz" wrote:

> Hi All,
>
> I've just noticed that there seem to be two ways of setting up a global.asax
> file.
>
> At http://www.csharphelp.com/archives/archive206.html the global.asax
> example has Application_Start etc within <script runat="server"> ...
> </script> tags, whereas VS.Net creates a global.asax.cs file that is
> presumably pre-compiled like a .aspx.cs file.
>
> Am I correct in assuming that global.asax works just like a .aspx, ie there
> is a Code Behind model and an Inline model, and the programmer has an open
> choice between the two, depending on a trade-off between speed (compiled
> Code Behind) versus the maintainability of not having to recompile after
> changes (Inline)?
>
> And presumably, as with inline .aspx pages, does an inline global.asax get
> compiled when the first page of the application is hit?
>
> TIA,
>
> JON
>
>
>
>

Re: Global.asax - Code Behind or Inline?
 

With advantages / disadavantages exactly as with Code Behind / Inline for an
..aspx?

J

Re: Global.asax - Code Behind or Inline?
 

Yes, same advantages disadvantages. The runtime will compile
global.asax with inline code when the application spins up. At that
point, there really is no runtime performance diff of the code in
global.asax versus code compiled in the code behind.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Wed, 13 Oct 2004 14:17:00 +0100, "Jon Maz" <jonmaz@surfeuNOSPAM.de>
wrote:

>With advantages / disadavantages exactly as with Code Behind / Inline for an
>.aspx?
>
>J
>