Visual Studio has its own integrated ASP.NET Runtime engine, which helps to run any ASP.NET web application with in Visual Studio. While running application from Visual Studio, you must have seen a popup notification in System Tray (As shown in below image) , which is notification of ASP.NET Development Server.
This ASP.NET Development Server is nothing but a executable file (WebDev.WebServer) which used by Visual Studio to execute you web application when it’s running in the context of Visual Studio. You can find the executable file at <\Program Files (x86)\Common Files\microsoft shared\DevServer\10.0> . This folder contain two different executable
WebDev.WebServer20 is targeted to CLR 2.0, which means all the ASP.NET Application which are targeted till FW .NET 3.5 will be taking care by WebDev.WebServer20.EXE and WebDev.WebServer40.EXE for ASP.NET 4.0 based application.
Now, let’s see how we can use these executable to run an ASP.NET 4.0 Application with out using Visual Studio.
Yesterday I delivered 1 hour session on “ASP.NET Request Processing Internals” at Microsoft User Group Hyderabad (MUGH). This was an half day event and organized at Microsoft Campus , Building 3 MPR Halls , Gachibowli, Hyderabad. I delivered the first session on ASP.NET Request processing Internals where I talked about how request processing happens in IIS level to ASP.NET Application Level. In this presentation I talked about how ASP.NET Application runs with in VS IDE , then moving to IIS, Different Components of IIS like HTTP.SYS, SVCHOST, WWW Publishing Services, WAS along with there roles in ASP.NET Request processing. I have also covered the key concepts like Worker Process, Application Pool, Web farms and web garden. Then I talked about how requests flow from HTTP.Sys, to WWW Services, WAS and How things happens with Worker Process . I have also talked about HTTP Pipeline and ASP.NET Page life cycle was the last one.
Hyderabad .NET User Group organized monthly UG meet on this Saturday (26th Feb) at 9:30 A.M at Microsoft Campus , Building 3 MPR Halls , Gachibowli, Hyderabad.
It’s a half day event for both Developer and IT Pro. Track. I will be speaking on Internals of ASP.NET Request Processing. Below is the complete agenda for the event.
For more information MUGH Community Meet
Come and Join ! See you there !
Today I delivered an 1 hour session on “Caching Enhancement in ASP.NET 4.0” at Microsoft Virtual Tech days 2011. It was the Day 1 of Virtual Tech Days and I presented the 4th session on Developer Track 1, from 3.00 PM To 4.00 PM IST. Thanks to all of you for attending my session. In this session I have discussed about ASP.NET 4.0 Caching Enhancement . I started with fundamentals of ASP.NET Caching to make sure all the attends are in same page. In Caching Quick Tour section I have talked about why Caching ? What are the different types of caching ? How Caching works ? etc. Then I have discussed about New Object Caching API in .NET 4.0. In this section I have talked about new Memory Cache API, there Implementation using System.Runtime.Caching . I have also shown how we can use same set of API in an Winforms / WPF / Console Application. Followed by, I have explained how we can extend the Object Caching by implementing MemoryCache Class.
The 11th edition of Virtual TechDays – being held on 9th to 11th Feb 2011. I am glad to say that, I will present a session on “Caching enhancements in ASP.NET 4.0” on 9th Feb 2011 from 3 PM to 4PM (IST) . ASP.NET 4 introduced an extensibility on output caching where developers can create their own custom cache provider to store the cache data in out of process. Output-cache providers can use any storage mechanism like database, file system, cloud etc. to persist output cached content. In this session I will be discussing the enhancement of ASP.NET 4.0 Caching by creating different custom cache provider for different type of output caching.
This is an live meeting event. You can attend it from any where. To register for this event click here . Find all the details agenda from here .
Tune in for a demo filled session.