Browse by Tags
All Tags »
Level 300 (
RSS)
Vorbei sind die Zeiten grauer, langweiliger Webanwendungen die hauptsächlich aus einer Ansammlung von Texten und Links bestanden. Der aktuelle Trend geht zu interaktiven, reichhaltigen Anwendungen welche die Features und Funktionalitäten traditioneller Desktopanwendungen in einer Webanwendung im Browser zur Verfügung stellen. Ermöglicht wurde dieser Trend u.a. durch ein Programmiermodell welches heute unter dem Namen Ajax (Asynchronous JavaScript and XML) in aller Munde ist und die inzwischen zahlreichen Ajax Frameworks, welche die Entwicklung komplexer Anwendungen deutlich erleichtern. Dieser TechTalk gibt einen Überblick über das ASP.NET Ajax Framework von Microsoft. Daniel Walzenbach, Developer Evangelist der Microsoft Deutschland GmbH, vermittelt...
Hi Everyone, Welcome back!!! As mentioned yesterday, today we will be wrapping up with the discussion about the ASP.Net 2.0 compilation machinery with the discussion about virtual path providers. Virtual Path Providers: Before the advent of ASP.NET 2.0, a source ASP.NET page could be only an .aspx file deployed on the server and located in a particular folder. A one-to-one correspondence is required between .aspx resources and files on disk. In ASP.NET 2.0, the virtual path provider mechanism allows you to virtualize a bunch of files and even a structure of directories. You can abstract web content away from the physical structure of the file system. Created to serve the needs of SharePoint (the next version of SharePoint when ASP.Net 2.0 was...
Hi Everyone, Welcome back!!! Yeah, we skipped a few days again, just got a bit busy with my cases. As mentioned earlier, today we will be taking up the discussion about ASP.Net 2.0 Build Providers. Build Providers: In ASP.NET 1.x, only a few file types are dynamically compiled into assemblies—ASP.NET pages, user controls, ASP.NET Web services, and custom HTTP handlers. In ASP.NET 2.0, compilation model is extended to virtually any file type that you use in your application. In ASP.NET 2.0, commonly used file types are bound to a special breed of component—the build provider—which communicates with the ASP.NET infrastructure and provides the code representation of the contents of the specified file. Hence the build provider registered to process...
Hi Everyone, Welcome back!!! Let's continue the discussions around the ASP.Net compilation mechanisms. We discussed the overall dynamic compilation concepts (what happens when resources get updated) and pre-compilation (techniques to avoid first hit delay and preserving intellectual property by hiding source code), however whenever any kind of compilation happens for any resource of an ASP.Net site, there is a machinery that gets triggered behind the scenes which does the job of actually compiling the resources from their source files. That's what we will look into today. Building Blocks of ASP.NET Compilation: The ASP.NET compilation machinery involves two main manager classes and a family of components named "build providers". The two classes...
Hi Everyone, Welcome back!!! Let's continue the discussion about ASP.Net site pre-compilation. We talked about in-place pre-compilation yesterday; another flavor of pre-compilation is deployment pre-compilation. Pre-compilation for deployment: Pre-compilation for deployment pursues different goals than in-place pre-compilation. Conceptually, it tends to transform the ASP.NET application into a closed executable that preserves intellectual property by hiding source code (possibly both markup and classes). Pre-compilation generates a file representation of the site made of assemblies, static files, and configuration files that can be later packaged into a CAB, ZIP, or MSI file for actual deployment. As a pleasant side effect, it also saves your...
Hi Everyone, Welcome back!!! Again, continuing to discuss the automatic dynamic page compilation further. Now we have been saying all the while that ASP.Net will detect automatically at runtime when ASP.Net resources change and will dynamically create new assemblies. Let's see how this replacement of assemblies happens. How ASP.NET Replaces Page Assemblies: We already mentioned that ASP.Net puts in place a file change notification mechanism and that is what tells ASP.net that a resource got updated and a new assembly is built for that. When a new assembly is created for a page as the result of an update, ASP.NET verifies whether the old assembly can be deleted. If the assembly containing the old page class contains only that page class, ASP...
Hi Everyone, Welcome back!!! Again, continuing to discuss the automatic dynamic page compilation further. Let's understand how is the page assembly generated with respect to what files are involved. Generating an assembly for a particular .aspx resource is a 2 step process. First, a class file is created that fully represents the markup of the .aspx file. Second, the dynamically generated class is compiled into an assembly and cached in the "Temporary ASP.Net Files" folder. There will be a distinct folder for this for each installed version of ASP.Net. Let's understand this "Temporary ASP.Net Files" folder a bit more: The Temporary ASP.Net Files folder has one child directory for each application ever executed. The name of the subfolder matches...
Hi Everyone, Welcome back!!! As mentioned, we are continuing to discuss the automatic dynamic page compilation further. Now, if you notice the way the final page class gets prepared is a bit different in ASP.Net 2.0 compared to how it happened in ASP.Net 1.x, this is typically because of the introduction of partial classes. Partial classes are a new feature introduced in C# 2.0 and ASP.Net 2.0 leverages it. We will not discuss much about partial classes here. For those interested please refer here . In ASP.Net 1.x, the page class inherits from the code-behind class you created with Visual Studio. In ASP.Net 2.0, the page class still inherits from the class that represents the code. But the class that represents the code is a completed version...
Hi Everyone, Welcome back!!! As mentioned, we are continuing to discuss the automatic dynamic page compilation further. Now, if you notice the way the final page class gets prepared is a bit different in ASP.Net 2.0 compared to how it happened in ASP.Net 1.x, this is typically because of the introduction of partial classes. Partial classes are a new feature introduced in C# 2.0 and ASP.Net 2.0 leverages it. We will not discuss much about partial classes here. For those interested please refer here . In ASP.Net 1.x, the page class inherits from the code-behind class you created with Visual Studio. In ASP.Net 2.0, the page class still inherits from the class that represents the code. But the class that represents the code is a completed version...
Hi Everyone, Welcome back!!! Today and in next few days we will discuss the automatic dynamic page compilation. Each web application has its own copy of the Http runtime and runs in a separate AppDomain. The runtime object creates the Http context for the request, and it initializes the cache and the file system monitor used to detect changes in the application files. The worker process (either aspnet_wp or aspnet_isapi inside w3wp) activates the HTTP pipeline by creating a new instance of the HttpRuntime class and then calling its ProcessRequest method. As mentioned earlier the ultimate goal of the HTTP pipeline is finding in the current AppDomain a managed class that fully represents the requested ASP.Net resource. For pages, this class derives...
More Posts
Next page »