Fundamental ASP.NET question

Tech-Archive recommends: Fix windows errors by optimizing your registry

I have a doubt regarding the architecture, and working of the ASP.NET
framework. I haven't been able to satisfy myself with any answer.

I do understand that for each request for a resource (let's talk page),
we have 1 HttpApplication object from a pool that is managed by
HttpApplicationFactory. My question is this. After all the objects
that are created to service 1 request, is the same dll referenced for 1
page.
Let's say 3 people are trying to access Page1.aspx. Each of their
requests will be handled by 3 separate HttpApplication objects, but
will all their requests be delegated to 1 dll corresponding to
Page1.aspx, or 3 separate dlls.
The reason I'm asking is because if there is only 1 dll being used, I
will think twice before using any static properties/fields, to avoid
synchronization issues, when the properties are read/write.

Thanks in advance.
Maneesh

.

Relevant Pages

  • Re: Fundamental ASP.NET question
    ... there's 1 HttpApplication object which serves as their "home". ... One assembly...unless you're not caching or unless the Cache dies before the next request. ... will think twice before using any static properties/fields, ... Anything that is static is stored in the heap, rather than the stack. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Fundamental ASP.NET question
    ... Your "Backend method" can access the appSettings or ConnectionStrings ... throughout the application, whenever I want to make a connection, ... I do understand that for each request for a resource, ... that are created to service 1 request, is the same dll referenced for 1 ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Fundamental ASP.NET question
    ... I usually try to have a backend class library ... I do understand that for each request for a resource, ... that are created to service 1 request, is the same dll referenced for 1 ... The reason I'm asking is because if there is only 1 dll being used, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Using C++ COM from c# web application
    ... compiled dll from c# application and everithing works ok. ... the current web request. ... If the application is impersonating ... Source Error: ...
    (microsoft.public.dotnet.languages.vc)
  • Using C++ COM from c# web application
    ... compiled dll from c# application and everithing works ok. ... the current web request. ... If the application is impersonating ... Source Error: ...
    (microsoft.public.dotnet.languages.vc)