I'm heading over to Newcastle for the SharePoint User Group tonight.

It's a whiteboard session on MOSS Architecture.

Newcastle SharePoint User Group

Hope to see you there if you are going.

 UPDATE....

Big thank you to John Timney (Cap Gemini), Brian English (Cap Gemini) and Phil Hunter (BT) for an excellent user group …

Working with SharePoint, sometimes you just have to install assemblies to the GAC. An example of this I have had to deal with recently was writing a webpart to access methods in the UserProfileManager class.

Debugging GAC installed assemblies can be a bit frustrating, hopefully the following steps will make it alot …

I've recently been investigating a rather curious problem we've been experiencing with deployment of the Digital Signature ActiveX Control from SharePoint 2007 to browsers.

First a little background: A number of workflows we've developed recently make use of the capability of InfoPath forms to incorporate sections that …

This is handy. SharePoint helpfully populates the meta data with the GUID of the list and the ID of the item a WF instance is associated with. These are stored in "ows_WorkflowListId" and "ows_WorkflowItemId" fields on the task list item.

 An example of using this is from an InfoPath form in the …

MOSS and WSS 3.0 handle user profiles differently. In MOSS, user profile information is stored centrally and can be shared across site collections. Profiles can be manipulated using the UserProfileManager class found in Microsoft.Office.Server.dll.

Life just isn't the same when working with WSS 3.0. When developing a …

Big thank you to Penny Coventry and Steve Smith for presenting at the SharePoint User Group UK Newcastle meeting on Wednesday night. Both were excellent sessions.

Penny gave an overview of SharePoint Designer, which if not already, will probably become your default tool for design and basic development of SharePoint …

SharePoint 2007 displays a nice "friendly" error message when anything goes wrong. This "friendly" error message usually provides no useful information about why the error has occurred (sometimes you get an HRESULT). It may be friendly but isn't usually very helpful, not for a developer.

You can …

The reason the Office Sharepoint Server Workflow Task is not visible is because it is assigned to a special group named "_Hidden" which precludes it from being displayed in the site collection content type view.

As it turns out content types are exposed and manipulable through the Sharepoint OM using the …

We have a workflow that is a mix of simple tasks and MOSS infopath forms server workflow tasks.

To that end we remove the TaskListContentTypeId from workflow.xml and use the CreateTaskWithContentType shape to manually set the content type on appropriate tasks. This works fine until we come to deploy on a fresh …