Microsoft Windows SharePoint Services 3.0

By Ted Pattison

The next major version of Microsoft Windows SharePoint product and technology is planned to be released in 2006. This version includes Microsoft Windows SharePoint Services 3.0 and Microsoft Office Sharepoint Server 2007. This chapter covers new content for developers in Windows SharePoint Services 3.0. The developer-centric feature of Microsoft Office Sharepoint Server 2007 will be introduced in a later chapter.

Microsoft Windows SharePoint Services 3.0 is a free plug-in licensed for Windows 2003 operating system. In its kernel, Microsoft Windows SharePoint Services 3.0 plays the role of an upgradeable site construction engine, it solves the problem of creating and managing hundreds of web sites and being accessed by hundreds of thousands of users. Microsoft Windows SharePoint Services 3.0 is scalable by using the design structure of a Web server farm, this structure is based on a front-end web server group that relies on Microsoft SQL server to store content and other site-related data on the backend.

Similar to the previous version, Microsoft Windows SharePoint Services 3.0 supports out-of-the-box functions, allowing you to easily create and design collaboration features including shared calendars, contact lists, and document library sites. However, developers must understand that Microsoft Windows SharePoint Services 3.0 is considered to be more powerful than a user-Targeted collaboration tool. Microsoft Windows SharePoint Services 3.0 is an added ASP. net.

Microsoft Windows SharePoint Services 3.0 provides more value than ASP. the net2.0 development platform makes it easier to construct and store pages, lists, and document libraries. This structure can be driven by custom code or by user actions based on browser user interfaces, after the screen, Microsoft Windows SharePoint Services 3.0 automatically calculates how and where to store the content. Microsoft Windows SharePoint Services 3.0 also simulates monotonous task requests in many typical ASP. NET development because it generally supports user interface elements that allow users to add, view, and edit content.

Integration with ASP. NET 2.0

Microsoft Windows SharePoint Services 3.0 is constructed at the IIS web site level. Before you create your first Microsoft Windows SharePoint Services site, an individual must run an administrator program to expand the 3.0 feature on one or more IIS sites. In Microsoft Windows SharePoint Services 2.0, the term virtual server is used to describe an IIS Site extended by Microsoft Windows SharePoint Services. To avoid conflicts with another Microsoft product with the same name, microsoft Windows SharePoint Services 3.0 now calls an IIS Site extended by Microsoft Windows SharePoint Services as a web application.

Use Microsoft Windows SharePoint Services 2.0 to use an ISAPI to filter DLL and iis6.0 and ASP. NET 1.1 integration. This integration technology causes the routing request from IIS to SharePoint Services to be located in ASP. before, Windows SharePoint Services had the opportunity to use ASP for an inbound HTTP request. net content is controlled before it is correctly initialized. This routing is proven to be problematic under certain conditions.

Microsoft Windows SharePoint Services 3.0 and ASP. NET are completely redesigned. First, Microsoft Windows SharePoint Services 3.0 is built compared to ASP. NET 1.1 provides important improvements to ASP. in addition, Microsoft Windows SharePoint Services 2.0 and ASP. the integration between net2.0 is changed to ASP before Microsoft Windows SharePoint Services. net runtime routes inbound requests, Microsoft Windows SharePoint Services Team by removing the ISAPI filter and adding a standard web. config entries are directed to ASP. net registered HTTP module and HTTP processor to improve these routing structures, this means that the inbound HTTP requests always enter ASP before they are switched to the code written by the SharePoint Services team to implement the special process of SharePoint Services. The. Net runtime environment is fully initialized with ASP. NET content.

Note that when you expand an IIS web site to make it a Windows SharePoint Services web application, Microsoft Windows SharePoint Services 3.0 adds a wildcard for the application to the original IIS database, this application shadow wildcard pairs forward to ASP. any type of file requests, and forward requests to Windows SharePoint Services for processing is required.

Another issue related to the new structure is related to how the. ASPX page is parsed and compiled. The. ASPX page parsed using ASP. NET 1.1 can only work with the ASPX page that exists on the local file system. However, the Windows SharePoint Services structure depends on the. ASPX page that is stored in the SQL database. Windows SharePoint Services 2.0 depends on ASP. NET 1.1, Sharepoint Services team had to create their own. the ASPX page parser, unfortunately, Windows SharePoint Services 2.0 does not support many ASP.. net.

ASP. NET 2.0 introduces a new type of plug-in component called virtual path provider. Developers can write a custom component to retrieve it from any location including SQL databases. on the ASPX page, once a custom virtual path provider retrieves it again. ASPX page, which can then control it to exit ASP.. Net has managed resolution and compilation requests. ASP. NET also provides the virtual path provider with a good way to control how the. ASPX page is parsed and whether they are compiled or run in a non-compiled mode.