Wiley 978-0-470-38137-3 Datasheet

The SharePoint 2007 Architecture SharePoint 2007 is an extension of ASP.NET and IIS. This chapter walks through the main architectural

Chapter 1: The SharePoint 2007 Architecture10Listing 1 - 3 (continued) < head runat=”server” > < title > Untitled Page < /title >

Chapter 1: The SharePoint 2007 Architecture11 < %@ Import Namespace=”System.Globalization” % > < !DOCTYPE html PUBLIC “-//W3C//DTD XHTM

Chapter 1: The SharePoint 2007 Architecture12 The following list describes some of the public properties of the SPWebApplication class: AllowAccess

Chapter 1: The SharePoint 2007 Architecture13 The following list presents the public methods of the SPWebApplication class: Delete. This deletes t

Chapter 1: The SharePoint 2007 Architecture14 The following code listing presents a web page that uses the SharePoint object model to display the name

Chapter 1: The SharePoint 2007 Architecture15 ApplicationPoolId. This gets or sets a string that contains the GUID that uniquely identifies the app

Chapter 1: The SharePoint 2007 Architecture16 The following code listing creates and provisions a new web application: < %@ Page Language=”C#” % &

Chapter 1: The SharePoint 2007 Architecture17 DefaultDatabaseInstance. This gets or sets a reference to the SPDatabaseServiceInstance object that r

Chapter 1: The SharePoint 2007 Architecture18 The following code listing iterates through the application pools for each web service and prints their

Chapter 1: The SharePoint 2007 Architecture19 Listing 1 - 4: The ProcessRequest method of ISAPI Runtime public int ProcessRequest(IntPtr ecb, int

Chapter 1: The SharePoint 2007 Architecture2which isolates HttpRuntime from the environment - specific aspects of the communications between HttpRunti

Chapter 1: The SharePoint 2007 Architecture20 It calls the GetApplicationInstance method of an ASP.NET class named HttpApplicationFactory to return a

Chapter 1: The SharePoint 2007 Architecture21generates on the fly from the content of the global.asax file. In other words, the GetApplicationInstance

Chapter 1: The SharePoint 2007 Architecture22obvious case is when you run a program such as an antivirus program that changes this timestamp even thou

Chapter 1: The SharePoint 2007 Architecture23 SharePoint uses the same approach to introduce a code - behind class named SPHttpApplication. This means

Chapter 1: The SharePoint 2007 Architecture24 Listing 1 - 8: The IHttpModule interface public interface IHttpModule{ void Dispose(); void Init(Ht

Chapter 1: The SharePoint 2007 Architecture25 Event Description PostRequestHandlerExecute Fires after ASP.NET executes the reques

Chapter 1: The SharePoint 2007 Architecture26named BuildSteps and ExecuteStage where the former creates these IExecutionStep objects and the latter ca

Chapter 1: The SharePoint 2007 Architecture27 Listing 1 - 9 presents the internal implementation of the SPHttpApplication class. Listing 1 - 9: T

Chapter 1: The SharePoint 2007 Architecture28Listing 1 - 9 (continued) { readerWriterLock.ReleaseWriterLock(); } } } public

Chapter 1: The SharePoint 2007 Architecture29the HTTP modules that are added first get to register their event handlers first. This means that when th

Chapter 1: The SharePoint 2007 Architecture3 Runtime Class The ASP.NET 2.0 Framework comes with two important runtime classes named ISAPIRuntime and

Chapter 1: The SharePoint 2007 Architecture30 Listing 1 - 11: The portion of the implementation of the Init method of the SP RequestModule public

Chapter 1: The SharePoint 2007 Architecture31request for any site page instance of the associated page template. If so, SharePoint loads the page temp

Chapter 1: The SharePoint 2007 Architecture32 Take these steps if you need to customize the behavior of the SPVirtualPathProvider: 1. Implement a

Chapter 1: The SharePoint 2007 Architecture33 Listing 1 - 13: The IHttpHandlerFactory interface public interface IHttpHandlerFactory{ IHttpHandler

Chapter 1: The SharePoint 2007 Architecture34 The Execute method of the IExecutionStep object associated with the MapRequestHandler event searches the

Chapter 1: The SharePoint 2007 Architecture35 Listing 1 - 15: The web.config file < configuration > < system.web > < httpHand

Chapter 1: The SharePoint 2007 Architecture36 Note that this HTTP handler implements the IHttpAsyncHandler interface, which in turn extends the standa

Chapter 1: The SharePoint 2007 Architecture37 Listing 1 - 18 presents the internal implementation of the BeginExecuteUrlForEntireResponse method.

Chapter 1: The SharePoint 2007 Architecture38 Next, it determines the authentication type: string authenticationType = context.User.Identity.Authentic

Chapter 1: The SharePoint 2007 Architecture39 As you can see, the DefaultHttpHandler HTTP handler provides a powerful approach to custom request proce

Chapter 1: The SharePoint 2007 Architecture4ISAPI extension module named aspnet_isapi.dll. This module, like any other ISAPI module, is a Win32 dynami

Chapter 1: The SharePoint 2007 Architecture40 { uint num; base.ExecuteUrlHeaders.Add(this.AuthModeHeader, “Forms”); if (SPSecurity.U

Chapter 1: The SharePoint 2007 Architecture41 Note that OverrideExecuteUrlPath also stores the authentication and authorization information into the E

Chapter 1: The SharePoint 2007 Architecture42 Developing Custom HTTP Handler Factories, HTTP Handlers, and HTTP Modules Deep integration of Sh

Chapter 1: The SharePoint 2007 Architecture43 Now introduce a compilation error and hit F5 to compile the page. You should get the page shown in Figur

Chapter 1: The SharePoint 2007 Architecture44 When you hit F5, the ASP.NET build environment performs these tasks: 1. Parses the MySimplePage.asp

Chapter 1: The SharePoint 2007 Architecture45 As you can see, this popup menu contains an entry for the ASP namespace. If you add a dot after ASP, you

Chapter 1: The SharePoint 2007 Architecture46 As mentioned, the ASP.NET build environment temporarily stores the source code for this dynamically gene

Chapter 1: The SharePoint 2007 Architecture47 You may be wondering why the Default class shown in Listing 1 - 23 implements the IRequiresSessionStat

Chapter 1: The SharePoint 2007 Architecture48 Notice that the directory whose content is shown on the right panel of the Windows Explorer shown in Fig

Chapter 1: The SharePoint 2007 Architecture49 Listing 1 - 26: The default.aspx.cdcab7d2 compiled file < ?xml version=”1.0” encoding=”utf-8”? &g

Chapter 1: The SharePoint 2007 Architecture5 The w3wp.exe executable is an IIS 6.0 - specific executable located in the following IIS - specific direc

Chapter 1: The SharePoint 2007 Architecture50 If the old assembly doesn ’ t contain any other classes, ASP.NET attempts to remove it from the ASP.NET

Chapter 1: The SharePoint 2007 Architecture51database. When a request for the home page of one of these sites arrives, the SPVirtualPathProvider loads

Chapter 1: The SharePoint 2007 Architecture52 When you provision a SharePoint web application, SharePoint automatically registers all standard ASP.NET

Chapter 1: The SharePoint 2007 Architecture6 IIS 6.0 introduces a new kernel - mode component named the HTTP Protocol Stack (http.sys) that eliminates

Chapter 1: The SharePoint 2007 Architecture7 Farm. This read - only property gets a reference to the SPFarm object that represents the SharePoint f

Chapter 1: The SharePoint 2007 Architecture8Listing 1 - 2 (continued) foreach (SPApplicationPool ap in apc) { Response.Write(ap.Name)

Chapter 1: The SharePoint 2007 Architecture9 ServerComment. This gets or sets a string that contains the display name of the IIS web site that the