Microsoft SharePoint Products and Technologies Infrastructure Update Released!

The Microsoft SharePoint Products and Technologies Infrastructure Update has been officially released. The update includes both improvements in core functional scenarios such as Office SharePoint Server Search with the introduction of S2 in addition to management enhancements resolving core customer issues such as scalability and performance improvements to support search incremental crawl (WSS), patch and upgrade of WSS server farms where a large number of host header-based site collections are implemented, support for Kerberos authentication to access SSP Web services, and more…


Download


Microsoft Office SharePoint Server 2007


x86 – http://www.microsoft.com/downloads/details.aspx?FamilyId=256CE3C3-6A42-4953-8E1B-E0BF27FD465B&displaylang=en


x64 – http://www.microsoft.com/downloads/details.aspx?FamilyId=6E4F31AB-AF25-47DF-9BF1-423E248FA6FC&displaylang=en


Windows SharePoint Services 3.0


x86 – http://www.microsoft.com/downloads/details.aspx?FamilyId=3811C371-0E83-47C8-976B-0B7F26A3B3C4&displaylang=en


x64 – http://www.microsoft.com/downloads/details.aspx?FamilyId=3A74E566-CB4A-4DB9-851C-E3FBBE5E6D6E&displaylang=en

Developing Web Parts, considerations on Microsoft SharePoint Products and Technologies

Background Information

Web Parts as defined by MSDN are an integrated set of controls for creating Web sites that enable end-users to modify the content, appearance, and behavior of Web pages in a browser.

In Windows SharePoint Services 3.0 Web Parts ultimately derive from the ASP.WebPart (System.Web.UI.WebControls.WebParts) base class; however, Windows SharePoint Services 3.0 also has a Web Part base class (Microsoft.SharePoint.WebPartPages.WebPart) derived from the ASP.WebPart class.  If you are developing Web Parts you can elect to derive from either the Asp.WebPart or WSS.WebPart; however you should carefully consider your approach before developing custom Web Parts for use with Windows SharePoint Services 3.0.  To help define the differences, we’ll examine each class and their respective pros and cons.

ASP.NET Web Parts

When deriving from the ASP.WebPart your Web Part derives directly from the ASP.WebPart class which does not have a dependency on Windows SharePoint Services 3.0 code so it can be used in both ASP.NET Web sites or a Windows SharePoint Services 3.0 site collection/Web.  To ensure the Web Part customization is sustainable you should consider using the ASP.WebParts.  ASP.WebParts are exportable using the .webpart extension, can be displayed in SPD using attribute markup and are persisted to the Windows SharePoint Services store in binary Web Part format.

Hybrid (ASP.NET 2.0 + Windows SharePoint Services Web Parts)

Hybrid Web Parts typically derive from the Wss.WebPart base class; however, adhere to the design guidelines for ASP.WebParts though the dependency on WSS.WebPart implies its use strictly in a Windows SharePoint Services 3.0 site collection/Web.  Hybrid Web Parts should be considered only where features provided in the WSS.WebParts class are required, for example, client-side connections.  Hybrid Web Parts can also be used in version to version upgrades where the existing legacy hybrid Web Part cannot be retired in favor of a ASP.WebPart.  Hybrid Web Parts are exportable using the .webpart extension, can be displayed in SPD using attribute markup and are persisted to the Windows SharePoint Services store in binary Web Part format.

Windows SharePoint Services Web Parts

WSS Web Parts derive from the WSS.Web Part base class and meet the guidelines as provided by the Windows SharePoint Services 2.0 Web Part design guidelines.  The WSS.WebPart class is obsolete and is retained solely for backwards compatibility.  Wss.WebParts are exportable using the .dwp extension, can be displayed in SPD using XML Markup and are persisted to the WSS store in a compressed XML format.

The bottom line is, if you are considering developing custom Web Parts you should consider deriving from the System.Web.UI.WebControls.WebParts.WebPart class and referencing the MSDN guidance on developing ASP.NET Web Parts to ensure the Web Parts to maximize interoperability and sustainability.

Resources

Working with ASP.NET 2.0 Web Parts and Windows SharePoint Services 3.0

http://msdn.microsoft.com/en-us/library/bb153523.aspx

Discover Significant Developer Improvements in SharePoint Services (Integration with ASP.NET 2.0 Web Parts)

http://msdn.microsoft.com/en-us/magazine/cc163578.aspx

Use Windows SharePoint Services as a Platform for Building Collaborative Apps, Part 2

http://msdn.microsoft.com/en-us/magazine/cc188713.aspx

Windows SharePoint Services Developer Center

http://msdn.microsoft.com/en-us/sharepoint/default.aspx

Developing Web Parts (Developer Center)

http://www.microsoft.com/click/SharePointDeveloper/

Windows SharePoint Services Version Comparison

http://office.microsoft.com/en-us/sharepointtechnology/FX101862291033.aspx?ofcresset=1&mode=print

Master Page Example

I used the sample master pages at http://office.microsoft.com/en-us/sharepointdesigner/HA102223711033.aspx in several Feature Stapling/Receiver demonstrations over the past year and was asked if I could provide the solution package I compiled using the Clarity master page (see image) in conjunction with a Feature Receiver to update the master page on both site collections and Webs.  I’ve finally gotten around to uploading the .wsp, so for those interested it can be downloaded here.

Usage:

Copy the Clarity Master Page.wsp to a location on a Web front-end computer.

Open a Command Prompt and change directories to %commonprogramfiles%Microsoft SharedWeb Server Extensions12BIN.

Run STSADM -o addsolution -filename "<path>Clarity Master Page.wsp" and wait for the operation to complete.

Run STSADM -o deploysolution -name "Clarity Master Page.wsp" -immediate -force -allowGacDeployment and wait for the operation to complete.

Run STSADM -o execadmsvcjobs and wait for the operation to complete.

NOTE Existing site collections will not be affected and can be modified either through SPD or the SharePoint UI.

Newly created site collections and Webs will receive the Clarity master page.

Microsoft Windows Server 2008 as a Host Operating System for Microsoft Virtual Server 2005

Suppose you would like to use Windows Server 2008 as your host operating system, but the system does not provide support for Hyper-V.  The good news is that Microsoft Virtual Server 2005 will install and run under Windows Server 2008 providing the following conditions are met (including the Virtual Server Administration Web site):  see notes http://support.microsoft.com/kb/948515.



  1. You need to run Virtual Server 2005 R2 SP1

  2. You must have KB948515 applied to enable Windows Server 2008 host operating system support (http://www.microsoft.com/downloads/details.aspx?FamilyID=a79bcf9b-59f7-480b-a4b8-fb56f42e3348&displaylang=en)

  3. Internet Information Services 7.0 is configured to support the Virtual Server Administration Web site

Obtaining Virtual Server 2005 R2 Service Pack 1


Microsoft Virtual Server 2005 R2 Service Pack 1 (SP1) QFE contains the latest software updates for Virtual Server 2005 R2 SP1.


Download Microsoft Virtual Server 2005 R2 Service Pack 1 – http://technet.microsoft.com/en-us/evalcenter/bb738033.aspx


Release notes for Virtual Server 2005 R2 Service Pack 1 – http://technet2.microsoft.com/windowsserver/en/library/60009f7c-9a6b-472c-949a-4f047e791dd21033.mspx?mfr=true


Obtaining KB948515


This update for Microsoft Virtual Server R2 SP1 includes support for the following additional Host and Guest Operating Systems


Additional Guest Operating System support:
Windows Vista® Ultimate Edition with Service Pack 1 (SP1)
Windows Vista® Business Edition with Service Pack 1 (SP1)
Windows Vista® Enterprise Edition with Service Pack 1 (SP1)
Windows Server® 2008 Core
Windows Server® 2008 Standard
Windows Server® 2008 Datacenter
Windows Server® 2008 Enterprise
Windows Server® 2008 Small Business Server
Windows XP Professional with Service Pack 3


Additional Host Operating System support:
Windows Vista® Ultimate Edition with Service Pack 1 (SP1) (non-production use only)
Windows Vista® Business Edition with Service Pack 1 (SP1) (non-production use only)
Windows Vista® Enterprise Edition with Service Pack 1 (SP1)(non-production use only)
Windows Server® 2008 Core
Windows Server® 2008 Standard
Windows Server® 2008 Datacenter
Windows Server® 2008 Enterprise
Windows Server® 2008 Small Business Server
Windows XP Professional with Service Pack 3 (non-production use only)


Download details:  Virtual Server 2005 R2 Service Pack 1 Update – http://www.microsoft.com/downloads/details.aspx?FamilyID=a79bcf9b-59f7-480b-a4b8-fb56f42e3348&displaylang=en


Configuring Internet Information Services 7.0


To enable the Virtual Server Administration Web site on Windows Server 2008, Internet Information Services 7.0 should be configured as provided in the steps below:


On the host machine click Start and select Server Manager.


Click Roles.


Click Add Roles (see illustration).


image


On the Add Roles Wizard click Next >.


Select Web Server (IIS) from the list of available Roles.  Click Add Required Features on the Add features required for Web Server (IIS) page if prompted and then click Next >.


Click Next > on the Web Server (IIS) page.


On the Select Role Services page select the checkbox labeled CGI under Application Development.


On the Select Role Services page select the checkbox labeled Windows Authentication under Security.


On the Select Role Services page select the checkbox labeled IIS 6 Metabase Compatibility under Management Tools | IIS 6 Manageability Compatibility.


Accept the remaining default values and click Next > on the Select Role Services page.


Click Install on the Confirm Installation Selections page.


Click Close on the Installation results page.


The Web Server Role Services should appear similar to those as provided in the illustration below:


image


NOTES


If presented with a 401.2 error when browsing the Virtual Server Web application, ensure Windows Authentication is enabled both at the Web server and Web site levels, if the error persists, enable Anonymous Authentication for the Web site.  Authentication models can be configured in the Internet Information Services (IIS) Manager.


The Virtual Server Administration Web site requires scripting to be enabled for navigation.  To enable scripting, either add the Virtual Server Administration Web site to the Trusted Sites zone or optionally disable Internet Explorer Enhanced Security Configuration.


To configure Virtual Server settings using the Virtual Server Administration Web site you must run Internet Explorer as an Administrator in Windows Server 2008.


In the event an access denied-type message is presented when browsing the Virtual Server Administration Web site after performing the previous steps, reinstall Microsoft Virtual Server 2005 R2 Service Pack 1 after configuring Internet Information Services 7.0 as specified above.