Archive for January, 2010

WSSv3 and MOSS 2007 December 2009 Cumulative Updates

January 20, 2010

The latest server packages containing the WSSv3 and MOSS 2007 December 2009 Cumulative Updates have arrived. They were release last month actually.

For WSSv3: KB977027  The full server package for WSS;EN-US;977027

For MOSS2007: KB977026 The full server package for MOSS;EN-US;977026

Installation information:

After applying these updates, run the SharePoint Products and Technologies Configuration Wizard. You can also run “psconfig –cmd upgrade –inplace b2b -wait” in command line. This needs to be done on every server in the farm with SharePoint installed.

System Center Operations Manager Management Packs for SharePoint Server 2010

January 20, 2010

System Center Operations Manager will have proper SP2010 support. Just announced at the Microsoft SharePoint Team Blog:

Management Packs allow users to monitor SharePoint 2010 with System Center Operations Manager. SharePoint Foundation Management Pack and SharePoint Server 2010 Management Pack enables monitoring of SharePoint Foundation 2010, SharePoint Server 2010, Search Server 2010 (These is separate management pack for FAST search), Project Server 2010 and Office Web Apps. Once management pack is imported to System Center console, based on console configuration it automatically discovers what SharePoint bits or servers are installed in the environment that is being monitored and start monitoring those components.

These 2010 management packs will be released to System Center Operations manager catalog and will also be released to web along with SharePoint 2010 RTM.

View the blogpost here.

Adobe released a x64 PDF iFilter

January 20, 2010

Not only interresting for MOSS 2007 but also SharePoint 2010: Adobe finally release a x64 pdf iFilter.

In response to customer requests, Adobe is releasing Adobe PDF iFilter 9 for 64-bit platforms, which will allow searching PDF files on Microsoft® Windows® 64-bit platforms for applications such as Microsoft Office SharePoint Server 2007, Microsoft Exchange Server 2007, and Microsoft SQL Server 2005.

More info here:

SP2010 Social op Codeplex

January 14, 2010

De twitter import ( en blog import ) code die ik eerder hier had gepubliceerd, staat nu als volledig project op

Project on codeplex:

Orginele blogpost.

Sandcastle and Powershell

January 13, 2010

We have been using Sandcastle and the Sandcastle help file builder tools for our code documentation for quite some time now. One thing kept bugging me, the fact I had to edit the shfbproj file everytime we added or removed a project to the solution.

Since we use powershell over at the build server to do extra tasks around building and packageging, I wrote a little powershell script to generate (part of) the shfbproj file.

First we need to modify the shfbproj file to include a reference to an environment variable were we will store the assemblies to generate documentation for:


The thing to note here is the $(DOCUMENTSOURCES) which is going to be replaced with the content of environment variable DOCUMENTSOURCES by MsBuild.

Next we will generate this $(DOCUMENTSOURCES) through our powershell, which will put a piece of XML in this variable which contains all the documentsources:

foreach ($folder in get-Childitem | where {$_.PsIsContainer}) {
    cd $
    if (Test-Path "manifest.ddf" ) {
        cd bin
        $dll = $
        $dll += ".dll"
        $xml = $
        $xml+= ".xml"
        if (Test-Path $dll ){
            $documentsources += "<DocumentationSource sourceFile=""..\"
            $documentsources += $
            $documentsources += "\bin\"
            $documentsources += $dll
            $documentsources += """ />"
        if (Test-Path $xml ){
            $documentsources += "<DocumentationSource sourceFile=""..\"
            $documentsources += $
            $documentsources += "\bin\"
            $documentsources += $xml
            $documentsources += """ />"
        cd ..   
    cd ..
cd $deploymentpath
$env:documentsources = $documentsources

And now all projects ( in this case that have a manifest.ddf ( SP2007 ) ) will be used for generating the documentation.