The SDK updates in 1.4 include:

Installing the Adobe PDF Ifilter (V6) on MOSS 2007

Download the Adobe PDF IFilter 6.0 from here

Stop the IIS Admin service: Start > Run > Services.msc > Stop the IIS Admin Service

Run the Adobe PDF IFilter 6.0 Setup program (ifilter60.exe) to install the filter on the server.

Copy a GIF that you would like to use as an icon (16X16) in “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Images”.

Edit the file C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\Template\Xml\DOCICON.XML .

Add an entry for the .pdf extension.

Perform an

So if you need to perform maintenance on a farm, you “quiesce” it. IMHO, something like “Take Farm Offline” would have been a better choice.

Why should you use the quiesce feature?

Simply put, to prevent data loss.

How do you quiesce the farm?

1. From Central Administration, Operations, select “Quiesce Farm.”

2. Enter the number of minutes in which you want the farm to be fully quiesced and click “Start Quiescing.”

3. The page will display the quiescing status. [From Microsoft] “Quiescing has three states: normal, quiescing, and quiesced. Normal is the active state in which the farm handles all requests that come into it. Quiescing is the state in which the farm only handles requests from existing sessions, and quiesced is the state in which the farm does not allow any new sessions to start.”

How do you “un-quiesce” (reset) a farm:

1. From Central Administration, Operations, select “Quiesce Farm.”

2. Click “Reset Farm.” Why couldn't they have come up with an obscure word for “reset?”

You may already be aware of the recent RTM announcement of SQL Server 2008.

Office SharePoint Server 2007 SP1 & Windows SharePoint Services 3.0 SP1 now support SQL Server 2008.

The documentation has been updated to include support for SQL Server 2008.

Please refer to:

WSS 3.0
MOSS 2007

In the next few weeks, they will publish a TechNet article that describes the benefits of running SQL Server 2008 with SharePoint Products and Technologies.

Here, they

When you want to use the PeopleEditor control you need the correct refence in your custom SharePoint page.

<%
@Register TagPrefix="wssawc" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

Add a user to the picker (c#):

ArrayList list = new ArrayList();
list.Add(
    new PickerEntity()
    {
        Key = @"DOMAIN\User"
    }
);
userPicker.UpdateEntities(list);

Retrieve selected user(s)(c#):

PickerEntity pe = (PickerEntity)userPicker.Entities[0];
string username = pe.Key;
//or if the entities are resolved
PickerEntity pe = (PickerEntity)userPicker.ResolvedEntities[0];
string username = pe.Key;

that's it

It is very easy to add a breacrumb to your custom application page.

First of all you need to create an xml file in the
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\ folder.

Rename this new xml file like this
layouts.sitemap.*.xml where you can change * to any string you want.

then change the content of the XML file like this


parentUrl="/_layouts/settings.aspx" title="Custom Application Page"/>


finally use
STSADM -o copyappbincontent

Ton Stegeman [MVP] wrote a wonderful article about how to create a custom sharepoint page.

Article

However, when you are searching for the hidden

Microsoft.SharePoint.ApplicationPages.WebAdminPageBase assemby

stop searching!

It is NOT in the sharepoint.dll. You must add a new reference to the Microsoft.SharePoint.ApplicationPages.dll. You can find this dll here:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\CONFIG\BIN\Microsoft.SharePoint.ApplicationPages.dll

nice to know not?