Ben Robb's SharePoint Blog

Best Practice Conference DC

Ben Robb — Thu, 12 Aug 2010 13:05:51 +0000

I’m putting the final finishing touches to my sessions at this year’s Best Practices Conference in Washington, D.C, and I’m really looking forward to catching up with lots of old friends from across the pond – especially since so many couldn’t make it over to SP Evolution because of the Ash Cloud in April. The line up this year is absolutely fantastic, with lots of MVPs, MCMs and other experts making the time to put on one of the biggest SharePoint conferences of the year.

I’m doing 3 sessions:

Building search driven internet applications using FAST and SharePoint WCM
Build a SharePoint 2010 publishing website in 60 minutes
Extending Web Analytics reports to provide campaign / goal driven websites SharePoint 2010

3 sessions in 3 days, plus an Ask the Experts sessions is going to be hard going, but should be good fun too. I’ll be posting supporting material up during the conference, so keep tuned.

Demo content: importing the complete works of Shakespeare to SharePoint

Ben Robb — Mon, 19 Jul 2010 13:09:40 +0000

We often find that we need a fair amount of sample content to really showcase some extended WCM and FAST scenarios, and found that lorem ipsum and other automated text generation just wasn’t cutting it. As someone with a keen interest in the theatre, where better to turn to than Shakespeare’s plays, especially since I found out that someone went to the trouble of marking up all 37 plays in XML.

There were a number of challenges to work through:

The XML I downloaded had DTD references that I couldn’t be bothered working through how to make work via the System.Xml.XmlDocument object, so I went in and deleted these in all of the files. This made processing easier.
The structure I chose to implement this in was a series of webs beneath a root web, with Root / Plays / [Play name] / [Act name]. Each act web has pages beneath it.
I needed to convert the data in each scene to XHTML to push into the PageContent field.
It takes about an hour on my VM to process all 37 plays – resulting in around 130 webs and nearly 1000 SharePoint publishing pages.

With this is mind I had the following code:

$xmlpath = “C:\SPBPC2010\Assets\shaks200″
$xmlpath | ls -Filter “*.xml” | % { Process-Play -play ([xml] (Get-Content $_.VersionInfo.FileName)) -parentweb $playsWeb }

This iterates through the folder that contains the XML files for the plays, and calls “Process-Play”.

function Process-Play([xml] $play, [Microsoft.SharePoint.SPWeb] $parentWeb)
{
Write-Host “Processing play: ” $play.PLAY.TITLE

## 1. Create the web for the PLAY

$name = Convert-ToSafeString $play.PLAY.TITLE

$playWeb = New-SPWeb (“{0}/{1}” -f $playsWeb.Url, $name) -name $play.PLAY.TITLE -Template $basetemplate

## 2. Process the ACTS

$play.PLAY.ACT | % { Process-Act -act $_ -web $playWeb}

Write-Host “Finished processing play: ” $play.PLAY.TITLE

Write-Host “——————————————————-”

}

Here, we are using a function called “Convert-ToSafeString” to get rid of spaces, quotes and other characters which will cause issues in a URL, and then create a new web for that play. We then walk down through the XML ($play.PLAY.ACT) and call “Process-Act”. This does a very similar thing, and also calls “Process-Scene”:$act.SCENE | % { Process-Scene -scene $_ -web $actWeb}

Powershell is great for doing this kind of iterative processing, and is really a time saver when it comes to writing quick scripts to do this kind of task.

Process-Scene is where we start actually putting in some content. For each scene, we want to create a Publishing Page and then add content to the Page Content field:

function Process-Scene([System.Xml.XmlElement] $scene, [Microsoft.SharePoint.SPWeb] $web)

{

Write-Host “Processing the scene: “$scene.TITLE

## 1. Create the page

$pubweb = Get-SPPublishingWeb -web $web

$PageLayout = Get-SPPublishingPageLayout -web $web -name $basepagelayout

$pagename = Convert-ToSafeString ($scene.TITLE.Substring(0, $scene.TITLE.IndexOf(“.”)))

$pagecollection = [Microsoft.SharePoint.Publishing.PublishingPageCollection] $pubweb.GetPublishingPages()

$page = New-SPPublishingPage -PageCollection $pagecollection -name $pagename -pagelayout $pagelayout -title $scene.TITLE

## 2. Field: PageContent

$pagecontent = Transform-Xml -xsl $sceneXsl -xml $scene

$page.ListItem.Set_Item(“PublishingPageContent”, $pagecontent)

## 5. Update and Publish

$page.Update()

$page.ListItem.Update()

$page.CheckIn($true)

$page.ListItem.File.Publish($true)

}

Here you can see we are creating a new publishing page [I have a utility function for this – it isn’t out of the box], and calling another utility function “Transform-Xml” to set the value of the PublishingPageContent field to the transformed content.

These utility functions are here:

## ==============================================================================

## UTILITY FUNCTIONS

## ==============================================================================

function Get-SPPublishingWeb( [Microsoft.SharePoint.SPWeb] $web )

{

.SYNOPSIS

Gets a SharePoint publishing web

.EXAMPLES

return [Microsoft.SharePoint.Publishing.PublishingWeb]::GetPublishingWeb($web)

}

## ==============================================================================

function Get-SPPublishingPageLayout(

[Microsoft.SharePoint.SPWeb] $web,

[string] $name)

{

.SYNOPSIS

Gets a publishing page layout

.EXAMPLES

$pubWeb = Get-SPPublishingWeb($web)

return $pubWeb.GetAvailablePageLayouts() | ? { $_.Name -eq $name}

}

## ==============================================================================

function New-SPPublishingPage(

[Microsoft.SharePoint.Publishing.PublishingPageCollection] $PageCollection,

[string] $Name,

[Microsoft.SharePoint.Publishing.PageLayout] $PageLayout,

[string] $Title)

{

.SYNOPSIS

Creates a publishing page in the SPPublishingPageCollection supplied

.EXAMPLES

Write-Host “Creating page: $PageName”

$newPage = $PageCollection.Add(($Name + “.aspx”), $PageLayout)

$newPage.Title = $Title

$newPage.Update()

$newPage.ListItem.Update()

return [Microsoft.SharePoint.Publishing.PublishingPage] $newPage

}

## ==============================================================================

function Convert-ToSafeString([string] $s)

{

return $s.Replace(” “, “-”).Replace(“‘”, “”).Replace(“,”,”")

}

## ==============================================================================

function Transform-Xml([System.Xml.Xsl.XslCompiledTransform] $xsl, $xml)

{

$sw = New-Object System.IO.StringWriter

$xsl.Transform($xml, $null, $sw) | Out-Null

Write-Output $sw.ToString()

}

See here for the complete PS and XSL.

Manipulating the Terms Store through Powershell

Ben Robb — Thu, 06 May 2010 16:42:04 +0000

I really like Powershell, for its repeatability, the fact that it means I know that that once I’ve worked out how to do something I can save it in my stash of modules for later, and the way that I can spin up lots of different scenarios very quickly.

For my session on “Build a website in 60 minutes” at SP Evo, I spent a fair amount of time pulling together scripts for manipulating term store data quickly. I could, I guess, have just used the out of the box “import CSV file” option from the UI. But that won’t cut it when going between multiple environments in the real world. I need to be able to do it from my build scripts, and I couldn’t find any way via the API to import from a CSV – it seems that code is locked into the web UI, not baked into the core APIs.

There are other posts out there for how to set up the term store in the first place, both manually and via Powershell, so I’ll not repeat them here. But assuming you have a term store available, here is some very straightforward Powershell to start populating it:

Assuming you have an XML file in this format:

You should be able to manipulate that like this:

 $TermStoreData = [xml] (Get-Content ($xmlpath))
 $site = Get-SPSite $url
 $session = new-object Microsoft.SharePoint.Taxonomy.TaxonomySession($site)
 $termstore = $session.TermStores[$TermStoreData.termstore.name]
 $TermStoreData.termstore.group |
 ForEach-Object {
  ## create the group
  if ($termstore.Groups[$_.name] -eq $null)
  {
   $group = $termstore.CreateGroup($_.name);
   Write-Host -ForegroundColor Cyan "Added group $_.name"
   $_.termset |
   ForEach-Object {
    ## create the termset
    $termset = $group.CreateTermSet($_.name)
    Write-Host -ForegroundColor Cyan "Added termset $_.name"
    SetTermsRecursive -termsetitem $termset -parentnode $_
   }
  }
 }
 $termstore.CommitAll()

Some of the “power” of “Powershell” is in its ability to load up standard .NET objects; in this case there are no out of the box cmdlets to add term store data, so we have to make use of “new-object” to load up the TaxonomySession object. From that we are into native SharePoint code – walking down the XML and creating Term Store Groups, Term Sets and then ultimately Terms. The terms in this example are deployed in a recursive function:

function SetTermsRecursive ([Microsoft.SharePoint.Taxonomy.TermSetItem] $termsetitem, $parentnode)
{
 $parentnode.term |
 ForEach-Object {
  ## create the term
  $newterm = $termsetitem.CreateTerm($_.name, 1033)
  Write-Host -ForegroundColor Cyan "Added term $_.name"
  SetTermsRecursive($termsetitem, $_)
 }
}

Pretty neat? Some core Powershell abilities are showcased here:

Walking through XML DOM structures via the “dot” shorthand notation. For example, $TermStoreData.termstore.group is equivalent to $TermStoreData.SelectNodes(“/termstore/group”) – the dot notation means less typing and more readable code.
Pipelines – for example, the ForEach-object and pipeline associated $_ syntax.

These can be difficult to read in examples, but I strongly advise anyone starting out in Powershell to get to grips with these, particularly the piping model.

Anyway, the end result is that in a few lines of fairly simple Powershell you can take an XML file and build up a term store with data as part of your deployment model. I’ll post later about why that is important if you ever want to use those term sets in, say a site column declaration…

Creating SharePoint Page Layouts as features in 2010

Ben Robb — Tue, 27 Apr 2010 15:53:02 +0000

You have hacked together a proof of concept in SharePoint Designer, and now you need to start working for real in SharePoint features. In 2007, you had little choice other than knowing the syntax and working out the values for the associated content type.

What we are looking for is something like:

Ideally, we’d like some nice powerful mechanisms from within the Visual Studio IDE for generating this stuff. I’m working on that as part of a submission to the CKS:DEV team, but in the meantime we do have another solution. In 2010, you now have Powershell. And look what it can do for you…

First, we need to be able to get the page layout in question from a supplied SPWeb and name.

function Get-SPPublishingPageLayout(
    [Microsoft.SharePoint.SPWeb] $web,
    [string] $name)
{
    $pubWeb = Get-SPPublishingWeb -web $web
    return $pubWeb.GetAvailablePageLayouts() | ? { $_.Name -eq $name}
}

Next, we need to format all those bits into the right structure:

function Get-XmlForPageLayout([string] $name)
{
$layout = Get-SPPublishingPageLayout -web (Get-SPWeb $siteurl) -name $name
return (@”




“@ -f “PublishingModule\$name”, $layout.Title, $layout.AssociatedContentType.Name, $layout.AssociatedContentType.Id)
}

This now makes it really easy to get the format you need for your elements.xml file. All you need to do now is call this function:

$siteurl = “http://www.fabrikam.com”
Get-XmlForPageLayout -name “homepage.aspx”

Now all you need to do is cut and paste that output from your Powershell command into Visual Studio.

SPEvo slides

Ben Robb — Mon, 26 Apr 2010 08:18:53 +0000

SharePoint Evolution was a blast, and even though a lot of speakers didn’t make it over, everyone pulled together. All credit to the Combined Knowledge team, especially Steve Smith and Zoe Watson for not breaking under the pressure of #ashtag.

Like many others (especially Spence Harbar and Eric Shupps), I did a number of extra sessions, and I’ve uploaded three of the decks to Slideshare.

Building high scale, highly available websites in SharePoint 2010

Introduction to the Client OM in SharePoint 2010

Build a SharePoint website in 60 minutes

Customising the SharePoint management UI – just say no!

Ben Robb — Mon, 29 Mar 2010 10:48:02 +0000

I was recently asked at an event how to make changes to some of the core management UI features of SharePoint 2010. The question was specifically around how to make a change to the Silverlight control you get when you click on “Create” in the “View all site content” page.

What you get when you click on that link now, v4′s “Fluent UI” in place is in full swing, and a nifty Silverlight control which looks very similar to the Backstage found in the new Office clients.

Add Gallery in SharePoint 2010

Backstage in Word

My response to clients who ask for the management UI in SharePoint to be customised [beyond what you get from master pages and themes] is to ask them: “What is the business value that doing so will add?”. Without clear business drivers to making these changes, they quickly become a drain on the project, and over time will add considerable cost to the ongoing support of the solution.

Spence Harbar had a great post on this back in the 2007 days, and much of what he said then still holds. You get higher TCO by changing core features like this – on-going maintenance, support, training and so on will all be higher, and there is a higher chance that you will be locked into your delivery partner for a longer time frame. Also, chances are that you will be hit by additional testing and development as service packs and other hotfixes get released.

So I’d push back when you see this kind of requirement come in. If the client understands the cost, the additional risk, and the downsides, to customising the UI, then fine, but don’t walk in blind to that kind of scenario.

Semantic mark-up for menus

Ben Robb — Fri, 26 Mar 2010 15:10:02 +0000

In SharePoint 2007, if you were building a tightly designed website, chances are that you were faced with a problem when using the out of the box (or ASP.NET) menu controls. Before ScottGu’s team were converted into believing that standards compliance was a good thing, the ASP.NET 2.0 controls came up woefully short when it came to clean mark up, relying on nested tables to get the layout right.

SharePoint 2007 continued this theme, wrapping their Microsoft.SharePoint.WebControls.AspMenu control with more tables, and worse, marking it so that you couldn’t inherit from the control to solve the rendering issue. Thankfully, there was a work around using control adapters to delegate the Render() method.

But it was still a pain. The configuration files for your control adapter have to live in the file system, in the App_Browsers directory, which means that a WSP cannot deploy them to your farm. And they sometimes introduce performance penalties in high scale sites. And in the case of menu controls, there was business logic wrapped into the original Render() method which was hard to reproduce, since it called internal methods.

How has the story improved in 2010? ASP.NET 4.0 does solve that problem, but SharePoint 2010 will not be shipping with support for ASP.NET 4.0 – that will have to wait for a service pack. But all is not lost: the SharePoint product team has made a significant investment in standards compliance and providing better quality mark-up. An example is the new UseSimpleRendering property on the AspMenu control. This Boolean flag is now all you need to set if you want navigation list to be rendered using

tags.

So let’s check what output we get with that property set. With UseSimpleRendering=”false”, the output is the traditional output that 2007 had, with nested tables and inline styles, both frowned on by the web designer community.

With UseSimpleRendering=”true”, the output is now much cleaner:

   

  
    
      
        
          
            Home
          
        
      
      
        
          
            About us
            Currently selected

Note the lack of tables, the fact that there are no inline styles, and that accessibility has clearly been taken care of with the inclusion of specific textual clues that a particular item is selected.

Rock on!

Slides from SUGUK session on BI

Ben Robb — Tue, 16 Mar 2010 15:24:45 +0000

I presented at the London SharePoint User Group (SUGUK-London) last Thursday, on what is coming in the 2010 wave of products around BI. There was a great turnout and a lot of new (and familiar) faces in the audience.

Obviously SharePint afterwards was also fun

Some people have asked for a copy of my slides: SUGUK Business Intelligence slide deck

“Insights in SharePoint 2010” (featured article on Technet Flash Magazine, UK)

Ben Robb — Fri, 05 Mar 2010 10:53:31 +0000

I was recently asked to write a feature article on the UK TechNet magazine, published in Feb this year.

Business intelligence has always been a key business problem for which Microsoft has sought to provide rich tooling. From a client point of view, Excel has been in the market since the early 1980s, and the SQL team released SQL Reporting Services in 2004. By acquiring ProClarity, and releasing Performance Point to the market with the Office 2007 wave, Microsoft’s dedication to the BI market has been clear.

2010 sees a clear step forward in making it easier to build business intelligence applications by unifying the technology stack. The Office, SharePoint and SQL teams have been working together to make it easier for end-users, developers and IT Pros to gain insight into how their business is running.

Familiar client tools
End users are creatures of habit, and thankfully the new Office 2010 suite of products includes enhancements to Excel and Visio to help users build their own self-service reports and dashboards, while leveraging data from line of business applications securely.

SharePoint investments
SharePoint has become the de facto corporate development platform to build business intelligence solutions on. As well as new features, within areas such as Excel Services, Visio Services, and the Chart Web Parts and Performance Point Services, the team has worked hard to make the process of deploying these solutions easier for IT Pros. How?

Simplifying management by providing Powershell interfaces for IT Pros to use to manage their deployments.
SharePoint now has a Secure Store Service which allows users to have confidence that their system credentials are well secured.
Performance Point, Excel Services and Visio Services are all first class citizens leveraging the new Service Application architecture, and are configured from a central place within your SharePoint Farm.
Connecting to Line of Business applications is made easy and secure via Business Connectivity Services

SQL Server 2008 R2
The SQL team have provided some key enabling technologies for building more powerful BI solutions.

PowerPivot is a joint effort between the SQL, Excel and SharePoint teams to allow large amounts of data to be manipulated in pivot tables and reports.
Reporting Services Add-In provides a simple way of displaying Reporting Services assets within a SharePoint deployment.

The best of both worlds?
The 2010 wave of products is a major step change in creating business intelligence solutions. It gives end-users the power to create rich self-service solutions, while at the same time giving IT the governance and tools it needs to ensure quality of service and data security.

All of the products mentioned in this article are now in public beta, downloadable from TechNet.

SharePoint Evolution Conference

Ben Robb — Tue, 02 Mar 2010 15:14:41 +0000

I’m really looking forward to the SharePoint Evolution conference next month in London. Last year’s Best Practice conference was a blast; not least because it is on my home turf. I’m really looking forward to seeing all my SP friends from around the world – the speaker list is mind blowing, featuring at least 5 MCMs, dozens of MVPs and representation from leading Microsoft partners and MCS. And it’s looking likely that the conference will sell out.

cScape are going to have a good presence there: not only am I speaking, but one of my colleagues (Ari Bakker) also has a session, and we are Gold sponsors.