Author: Peter Birkholm-Buch (Page 13 of 17)

To open and edit documents in the new Office 2007 OpenXML format in Office 2003 install the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats which can be found here:

 

 

This white paper provides information and guidelines for using Microsoft Office SharePoint Server 2007 in scenarios where content is managed across different languages. It details most of the functionality provided by Office SharePoint Server 2007 and suggests how to use it to manage multilingual scenarios. It also provides examples for creating custom Web Parts by using Microsoft Visual Studio 2005 and how to configure and manage them by using Microsoft Office SharePoint Designer 2007, the next generation of Web designer tools specifically designed for SharePoint sites. Microsoft Windows SharePoint Services 3.0 features and functionality, and how they add value to the end-user experience, are also described.

 

 

Highly recommended!

It turns out that [Today] and [Me] can’t be used in calculated fields in WSS lists.

 

However, there’s a bug (or feature) which allows us to use at least the [Today] any way.

 

In a list create a column with the name “Today”. It doesn’t matter but use the Date field type.

 

Now in a calculated field it’s possible to add the Today column and use it in a calculation like the age of something in years: =DATEDIF([Born];[Today],”d”)/365

 

Then delete the Today column – and now we’re set. WSS then replaces [Today] with the current date and the Age calculated field is filled with the Age in years.

 

Weird but true.

 

Here’s a some more reference information on calculated fields: http://office.microsoft.com/en-us/sharepointtechnology/HA101215881033.aspx

 

Link to Angus Logan’s Portals Blog : Free to download eBooks – Planning, Architecture & deployment (MOSS and Search) – 916 pages!

Go get it!

Using the SharePoint object model this is pretty easy, especially if you want to retrieve that list with code running in a web part. The WebPartManager property of the WebPart base class, gives you access to a collection of all the WebPartZones available on the page. Once you’ve got the zones, you can get the web part instances by using the WebParts property. The following web part code will display a small list of all the web parts found on the page, including the name of the web part class and the web parts zone:

 

using System;
using System.Runtime.InteropServices;
using System.Web.UI;
using System.Web.UI.WebControls.WebParts;
using Microsoft.SharePoint;
using System.Web.UI.WebControls;

namespace WebPartLister
{
  public class WebPartLister : System.Web.UI.WebControls.WebParts.WebPart
  {
    BulletedList list;

    protected override void CreateChildControls()
    {
      list = new BulletedList();
      WebPartZoneCollection zones = this.WebPartManager.Zones;
      foreach (WebPartZone zone in zones)
      {
        WebPartCollection webparts = zone.WebParts;
        foreach (WebPart webpart in webparts)
        {
          list.Items.Add(
          string.Format(“{0} ({1}), {2}”,
            webpart.Title, webpart.GetType().Name,
            zone.DisplayTitle));
        }
      }
      this.Controls.Add(list);
    }

    protected override void Render(HtmlTextWriter writer)
    {
      EnsureChildControls();
      list.RenderControl(writer);
    }
  }
}