Dissing - SharePoint MVP

To use one-liner or not to use one-liner?

2012-01-21T22:12:00.001+01:00

A recurring problem in many of the projects I'm working on is a link to open a link up in a pop / model window. My first thought was to do as Venkatesh R've described it here http://geekswithblogs.net/venkatx5/archive/2010/11/17/how-to-open-a-page-in-sharepoint-2010-dialog-framework.aspx. By making a new SP.UI. $ create_DialogOptions (); object and call SP.UI.ModalDialog.showModalDialog. Not because it's hard but if you do not need the callback. So it is easier to do as described in the SharePoint Developer Team Blog http://blogs.msdn.com/b/sharepointdev/archive/2011/06/23/how-to-open-a-list-form-in-a-modal-dialog-box.aspx whereas in a one-liner can open link in a model window.
<div id="displayDiv"> <p> Please help us with our survey. Take our poll now! </ P> <input onclick = "javascript: SP.UI.ModalDialog.showModalDialog ({url: '.. / Lists / GBE / NewForm.aspx', title: 'User Survey'}); return false; "id =" btnVote "type =" button "value =" Vote "/> </ div>

Which approach would you choose? Post a comment with your solution.

Change the user profile property display ordre

2011-12-19T21:56:00.001+01:00

On the last couple of projects, the customer wants to change the display order of the user profile properties and there is the PowerShell to do it.

To see the current user profile display order call the script like this

& '.\change userprofile display ordre.ps1' http://spsite

To change the order call the script like this

& '.\change userprofile display ordre.ps1' http://spsite nameoftheuserprofileproperty sortorder

e.g. & '.\change userprofile display ordre.ps1' http://spsite firstname 5000

Download the powershell here

Playing with SharePoint Rich Text Editor (RTE)

2011-11-06T16:27:00.001+01:00

At my current project we needed to add a text highlight function button to the Rich Text Editors (RTE) ribbon, so when the user click on the button a selected text in the RTE, is wrapped with a predetermined HTML tag, indicating the text has been highlighted. Like <span css=”highlight”>the selected text</span>

The thing we need is:

1) The button in the ribbon, only showed when we are in the context of the RTE

2) The JavaScript snippet the will interact with the RTE

3) A feature the adds the ribbon button and the JavaScript to the page

The button is added to the style group like this:

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<CustomAction
   Id="Ribbon.Demo.HighlightText"
   Location="CommandUI.Ribbon"
   Title="Insert Tooltips">
    <CommandUIExtension>
      <CommandUIDefinitions>
        <CommandUIDefinition Location="Ribbon.EditingTools.CPEditTab.Styles.Controls._children">
          <Button
           Id="Ribbon.Demo.HighlightText.Button"
           Sequence="12"
           LabelText="High light text"
           Alt="High light text"
           TemplateAlias="o1"
           Image32by32="/_layouts/RTE.Demo/images/highlight32.png"
           Command="Ribbon.Demo.HighlightText.Command"
           ToolTipTitle="High light text"
      />
        </CommandUIDefinition>
      </CommandUIDefinitions>
      <CommandUIHandlers>
        <CommandUIHandler
         Command="Ribbon.Demo.HighlightText.Command"
         CommandAction="javascript:HighLightText();"
         EnabledScript="true" />
      </CommandUIHandlers>
    </CommandUIExtension>
</CustomAction>
</Elements>

The JavaScript snippet looks like this:

function HighLightText() {
    var rng = RTE.Cursor.get_range().$3_0;
    var selectedText = RTE.Cursor.s_range.get_text();
    RTE.Cursor.get_range().deleteContent();
    var d = rng.ownerDocument;
    var a = d.createElement("span");
    a.innerHTML = selectedText;
    a.setAttribute("class", "highlight");
    SP.UI.UIUtility.insertAfter(a, rng);
}

Download the full project here

Events for Danes at the SharePoint Conference

2011-09-17T20:11:00.001+02:00

There are a lot of events at this year's SharePoint Conference, so in order to keep up, I've collected a list of events that are of interest to Danes.

Monday 3 October

20:00-00:00 - The RED Party presented by AvePoint
- http://www.avepoint.com/spc2011/the_red_party/
Heat Ultra Lounge (Anaheim GardenWalk,321 Katella Avenue, Anaheim) (http://www.heatultraloungeoc.com/)

20:30 – Danskerarrangement
- http://www.linkedin.com/groups/Danskerarrangement-mandag-3-oktober-kl-3830839.S.68372719

Tuesday 4 October

2000-1200 - Disneyland® Park Private Party for SharePoint Conference 2011
- http://www.mssharepointconference.com/pages/activitiespage.aspx#disney

Wednesday 5 October

17:00-19:30 - SP&TheCity Drinks&Networking (danske kvindelige deltagere)
- http://www.linkedin.com/groups/Ogs%C3%A5-i-%C3%A5r-inviterer-vi-3830839.S.50541142?qid=5df809d6-1fde-4738-8d1c-1ec08f13d637
Anabella Hotel, Tangerine Grill & Patio

20:00 - SharePint @ the SharePoint Conference 2011 in Anaheim, CA
- http://www.andrewconnell.com/blog/archive/2011/08/22.aspx
ESPNZone (http://www.espnzone.com/anaheim/)

19:30-1:00 - OktoberFiesta!
- http://events.r20.constantcontact.com/register/event?oeidk=a07e4rymr7ffc255c6b&llr=b4mprxfab
Tortilla Jo's Restaurant, Downtown Disney, Anaheim, CA

Visual Studio 2010 SharePoint Power Tools

2011-07-29T09:41:00.001+02:00

The Visual Studio 2010 SharePoint Power Tools is a set of templates and extensions that provides additional functionality to SharePoint developers who use the SharePoint developer tools in Visual Studio 2010. Below is the list of features included in the current release of the power tools.

http://visualstudiogallery.msdn.microsoft.com/8e602a8c-6714-4549-9e95-f3700344b0d9/

How to create send to connection with PowerShell?

2011-07-20T20:21:00.001+02:00

Send to connection is used in many seniors, so being able to deploy them through PowerShell is a must and it is in this way you do it:

First the XML configuration file, SendTos tag can be added multiple times if you have several applications. Under the SendTos tag is SendTo which is the connection itself. A send to consist of an Action, which can Copy, Move, or Link. Explanation which is the description for sending the link. Official filename is the name or title of sending the link. OfficialFileUrl is the URL of the site as the document to be sent, N.B. Remember that the content organizer feature must be enabled on the site. ShowOnSendToMenu is whether it should be shown in the document context menu.

<SendTos WebApplicationUrl="http://win-l2sfc3oetnn/">
  <SendTo>
    <Action>Move</Action>
    <Explanation>Move the document to 'a' site collection</Explanation>
    <OfficialFileName>Move to 'a'</OfficialFileName>
    <OfficialFileUrl>/docid/a/_vti_bin/officialfile.asmx</OfficialFileUrl>
    <ShowOnSendToMenu>false</ShowOnSendToMenu>
  </SendTo>
</SendTos>

The second part, is the PowerShell, where I loops thought the to sends tags and grab the web application. Then I test whether the connection already exists, if not I create it by adding a Microsoft.SharePoint.SPOfficialFileHost to OfficialFileHosts collection located on the web application.

[xml]$SendTos = gc $pwd\sendto.xml
 
$SendTos.SendTos | % {
	$webapp = Get-SPWebApplication $_.WebApplicationUrl.TrimEnd("/")
 
	$_.SendTo | % {
		$SendTo = $_
 
		$officialFileHostTemp = $webapp.OfficialFileHosts | ? { 
			$_.OfficialFileName -eq $SendTo.OfficialFileName 
		}
 
		if($officialFileHostTemp -eq $null)
		{
			[Microsoft.SharePoint.SPOfficialFileHost] $officialFileHost = New-Object "Microsoft.SharePoint.SPOfficialFileHost"
			$officialFileHost.Action = [Enum]::Parse([Microsoft.SharePoint.SPOfficialFileAction], $SendTo.Action)
			$officialFileHost.Explanation = $SendTo.Explanation
			$officialFileHost.OfficialFileName = $SendTo.OfficialFileName
			$officialFileHost.OfficialFileUrl = $url+$SendTo.OfficialFileUrl
			$officialFileHost.ShowOnSendToMenu = [bool]::Parse($SendTo.ShowOnSendToMenu)
			$webapp.OfficialFileHosts.Add($officialFileHost)
			$webapp.Update()
		}
		$officialFileHostTemp = $null
	}
}

Change the PowerShell UI Culture

2011-07-20T17:30:00.000+02:00

At one of my projects I’m using the new and greater multi language options in SharePoint 2010 and with ASP.Net resources it is really easy to create site in different languages. When I create a site e.g. in Danish the content type display name is translated into Danish, as expected, but when I start my SharePoint managed shell it is running in English context and if I have some PowerShell code which is dependent on language resources, then it will ask in English, but when my site is created in Danish, it may give some weird errors. The solution to this is to set PowerShell CurrentUICulture to be as the site you work with like this.

#Ensure the PowerShell process is running the same culture as SPWeb is created with
$web = Get-SPWeb "http://win-l2sfc3oetnn"
[int]$lcid = $web.Language
$culture = new-object "System.Globalization.CultureInfo" $lcid
[System.Threading.Thread]::CurrentThread.CurrentUICulture = $culture

Ribbon Toggle button demo

2011-05-29T15:33:00.001+02:00

I have a customer who need a toggle button in the Ribbon. Make a normal button in the Ribbon is straightforward and there is a lot of good articles out there. But there is not so many articles on the toggle button, Chris O'Brien and Wictor Wilen have some post, see the link, but not on handling server site code that call business logic to test which state the toggle button is in. My demo code is built around how to put a toggle button in a document library and test if it is on or off base on some server site business logic.

My demo code: http://cid-18d25562ce576dcc.office.live.com/self.aspx/Offentlig/SharePoint%20files/Ribbon.Demo.zip

Links:

How to add an application server role to your SharePoint farm

2011-03-13T13:27:00.001+01:00

To add an application sever with an application server role to your SharePoint farm run this PowerShell commands:

Connect-SPConfigurationDatabase -DatabaseServer "MySqlServer" -DatabaseName "MySharePointFarmName_SharePoint_Config" -Passphrase "myPassPhrase"
Install-SPHelpCollection -All
Initialize-SPResourceSecurity
Install-SPService
Install-SPFeature -AllExistingFeatures
Install-SPApplicationContent

For more infomation on this read this technet article “Add a Web or application server to the farm (SharePoint Server 2010)” - http://technet.microsoft.com/en-us/library/cc261752.aspx

Remove the SharePoint menu item “Edit in SharePoint Designer” in Site Action

2011-03-01T11:34:00.001+01:00

I had a customer who wanted to remove the menu option "Edit in SharePoint Designer" in the site action. It was not simply enough to disable edit in SharePoint Designer in central administration, for it does not remove the the menu item but make it just gray.
My first thought was to make a Hidde custom action, but it turns out that many of the items in the site action can not remove by a Hidde custom action. It turns out that the menu items in the site action is hardcore in the master pagen. eg. v4.master. So we have four solutions to the problem position.
1) We can remove the rights of the logged on user.
2) In v4.master file, remove the line 147 to 157th
3) Do some JavaScript that remove the menu item
4) Make a custom control or delegate control ala:

SPRibbon ribbonControl = this.Parent.Controls.Cast<Control>().First(c => (c is SPRibbon)) as SPRibbon;
SPRibbonPeripheralContent ribbonPeripheralContent = ribbonControl.Controls[0] as SPRibbonPeripheralContent;
SiteActions siteActions = ribbonPeripheralContent.Controls.Cast<Control>().First(c => (c is SiteActions)) as SiteActions;
FeatureMenuTemplate featureMenuTemplate = siteActions.Controls[0].Controls[2] as FeatureMenuTemplate;
Control editInSharePointDesigner = featureMenuTemplate.Controls.Cast<Control>().First(csd => (csd is MenuItemTemplate) && ((MenuItemTemplate)csd).Text.Equals("Edit in SharePoint Designer", StringComparison.InvariantCultureIgnoreCase));
featureMenuTemplate.Controls.Remove(editInSharePointDesigner);

Missing the open button when opening PDF files from SharePoint 2010.

2011-01-16T13:47:00.001+01:00

By the default setting of a SharePoint 2010, a users can’t open PDF files and many other files types (see the bottom of the post for all default file type allowed to download http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spwebapplication.allowedinlinedownloadedmimetypes.aspx) direct from SharePoint, neither “Display PDF in browser” mode or in the download popup, where the “open” button is missing.

The thing is SharePoint 2010 adds an additional security header to force the file to be saved to the disk before the users can open it. To fix this the BrowserFileHandling property should be set to “permissive” http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spbrowserfilehandling.aspx. This property exist both on a webapplication level http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spwebapplication.browserfilehandling.aspx and a on document library level http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.splist.browserfilehandling.aspx.

To fix this on a webapplication level, by using the GUI.

Open Central Administration
Application Management
Manage Web Applications
Select the webapplication to change
Click General Settings in the ribbon
Scroll down to Browser File Handling and select Permissive
Click on the OK button

To fix this with PowerShell on a webapplication level

Get-SPWebApplication http://vsitsp01 | % { $_.BrowserFileHandling = "permissive"; $_.update() }

To fix this with PowerShell on a document library level

$spweb = Get-spweb http://vsitsp01

$doclib = $spweb.Lists["Documents"]

$doclib.BrowserFileHandling

$doclib.BrowserFileHandling = "permissive"

$doclib.Update()

File types allowed to be download:

application/directx
application/envoy
application/fractals
application/internet-property-stream
application/liquidmotion
application/mac-binhex40
application/ms-infopath.xml
application/msaccess
application/msword
application/oda
application/oleobject
application/onenote
application/pics-rules
application/pkcs10
application/pkcs7-mime
application/pkcs7-signature
application/pkix-crl
application/postscript
application/rtf
application/set-payment-initiation
application/set-registration-initiation
application/streamingmedia
application/vnd.fdf
application/vnd.ms-excel
application/vnd.ms-excel.12
application/vnd.ms-excel.addin.12
application/vnd.ms-excel.binary.12
application/vnd.ms-excel.macroEnabled.12
application/vnd.ms-excel.macroEnabledTemplate.12
application/vnd.ms-excel.template.12
application/vnd.ms-office.calx
application/vnd.ms-officetheme
application/vnd.ms-pki.certstore
application/vnd.ms-pki.pko
application/vnd.ms-pki.seccat
application/vnd.ms-pki.stl
application/vnd.ms-powerpoint
application/vnd.ms-powerpoint.12
application/vnd.ms-powerpoint.addin.12
application/vnd.ms-powerpoint.macroEnabled.12
application/vnd.ms-powerpoint.presentation.12
application/vnd.ms-powerpoint.show.12
application/vnd.ms-powerpoint.show.macroEnabled.12
application/vnd.ms-powerpoint.slide.macroEnabled.12
application/vnd.ms-powerpoint.template.12
application/vnd.ms-powerpoint.template.macroEnabled.12
application/vnd.ms-project
application/vnd.ms-visio.viewer
application/vnd.ms-word.document.12
application/vnd.ms-word.document.macroEnabled.12
application/vnd.ms-word.template.12
application/vnd.ms-word.template.macroEnabled.12
application/vnd.ms-works
application/vnd.ms-xpsdocument
application/vnd.oasis.opendocument.presentation
application/vnd.oasis.opendocument.spreadsheet
application/vnd.oasis.opendocument.text
application/vnd.openxmlformats-officedocument.presentationml.slide
application/vnd.rn-realmedia
application/vnd.visio
application/vnd.visio.webdrawing
application/winhlp
application/x-bcpio
application/x-compress
application/x-cpio
application/x-csh
application/x-dvi
application/x-gtar
application/x-gzip
application/x-hdf
application/x-internet-signup
application/x-iphone
application/x-latex
application/x-miva-compiled
application/x-ms-application
application/x-ms-manifest
application/x-ms-reader
application/x-ms-vsto
application/x-ms-wmd
application/x-ms-wmz
application/x-msaccess
application/x-mscardfile
application/x-msclip
application/x-msdownload
application/x-msmediaview
application/x-msmetafile
application/x-msmoney
application/x-mspublisher
application/x-msschedule
application/x-msterminal
application/x-mswrite
application/x-netcdf
application/x-oleobject
application/x-perfmon
application/x-pkcs12
application/x-pkcs7-certificates
application/x-pkcs7-certreqresp
application/x-sh
application/x-shar
application/x-smaf
application/x-stuffit
application/x-sv4cpio
application/x-sv4crc
application/x-tar
application/x-tcl
application/x-tex
application/x-texinfo
application/x-troff
application/x-troff-man
application/x-troff-me
application/x-troff-ms
application/x-ustar
application/x-wais-source
application/x-x509-ca-cert
audio/aiff
audio/basic
audio/mid
audio/mpeg
audio/wav
audio/x-aiff
audio/x-mpegurl
audio/x-ms-wax
audio/x-ms-wma
audio/x-pn-realaudio
audio/x-pn-realaudio-plugin
audio/x-smd
drawing/x-dwf
image/bmp
image/cis-cod
image/gif
image/ief
image/jpeg
image/pjpeg
image/png
image/tiff
image/vnd.wap.wbmp
image/x-cmu-raster
image/x-cmx
image/x-icon
image/x-jg
image/x-portable-anymap
image/x-portable-bitmap
image/x-portable-graymap
image/x-portable-pixmap
image/x-rgb
image/x-xbitmap
image/x-xpixmap
image/x-xwindowdump
text/calendar
text/css
text/dlm
text/h323
text/iuls
text/plain
text/richtext
text/setext
text/tab-separated-values
text/x-ms-iqy
text/x-setext
text/x-vcard
video/mpeg
video/quicktime
video/x-ivf
video/x-la-asf
video/x-ms-wm
video/x-ms-wmp
video/x-ms-wmv
video/x-ms-wmx
video/x-ms-wvx
video/x-msvideo
video/x-sgi-movie

Install/Uninstall User Solution Application Wide

2010-12-12T13:51:00.001+01:00

Build on this blog post on how to get sandboxed on the farm, I also need to be able to install/uninstall sandboxed solution farm wide. There for I made they have two functions to wrap the install and Uninstall-SPUserSolution SPUserSolution.

The core code is when a call (a version 2) of the Get-UserSolution filter to get the deactiveated solutions and then call the build-in cmdlet Install-SPUserSolution

$gc = Start-SPAssignment
Get-UserSolution -SiteCollection $SiteCollection -Filter $Filter -Verboses:$Verboses | `
Where-Object -FilterScript { $_.Status -eq "Deactivated" } | `
Install-SPUserSolution -Site $SiteCollection -AssignmentCollection $gc
Stop-SPAssignment $gc

The code:

Get sandboxed solution on the farm

2010-12-12T10:33:00.001+01:00

How to get all sandboxed (user solution) installed on the SharePoint farm.

$gc = Start-SPAssignment
$gc | Get-SPSite | Get-SPUserSolution
Stop-SPAssignment $gc

The output:

Name                                SolutionId                                                      Status

----                                     ----------                                                         ------

Contacts.wsp                   3089ef04-527e-4b35-a0a2-af5f4df8a71b     Activated

Sandboxed1.wsp              a9240922-c794-433c-acf7-0ce7863b46d0 Deactivated

Sandboxed1.1.wsp           a9240922-c794-433c-acf7-0ce7863b46d0 Activated

Sandboxed1.1.wsp           a9240922-c794-433c-acf7-0ce7863b46d0 Activated

Sandboxed1.2.wsp           a9240922-c794-433c-acf7-0ce7863b46d0 Deactivated

Sandboxed1.wsp              a9240922-c794-433c-acf7-0ce7863b46d0 Activated

It is really simple to get a full list of sandboxed solutions, but the output is not useful, because we can see which site collection the sandboxed solution is store in.

This small PowerShell script will display the site collection url

function Get-UserSolution
{
	param(
		[Parameter(
    		Position=0, 
    		Mandatory=$true, 
    		ValueFromPipeline=$true,
    		ValueFromPipelineByPropertyName=$true)
    	]
    	$SiteCollection
	)
	process
	{
		Write-host "Site Collection:" $SiteCollection.Url
		$gc = Start-SPAssignment
		$SiteCollection | Get-SPUserSolution -AssignmentCollection $gc
		Stop-SPAssignment $gc
	}
}
Get-SPSite | Get-UserSolution

The output:

Site Collection: http://win-ugka6ujlm21

Name                               SolutionId                                                       Status
----                                    ----------                                                          ------
Contacts.wsp                   3089ef04-527e-4b35-a0a2-af5f4df8a71b     Activated
Sandboxed1.wsp              a9240922-c794-433c-acf7-0ce7863b46d0 Deactivated
Sandboxed1.1.wsp           a9240922-c794-433c-acf7-0ce7863b46d0 Activated
Sandboxed1.1.wsp           a9240922-c794-433c-acf7-0ce7863b46d0 Activated
Sandboxed1.2.wsp           a9240922-c794-433c-acf7-0ce7863b46d0 Deactivated
Site Collection: http://win-ugka6ujlm21/my

Site Collection: http://win-ugka6ujlm21/sites/sandbox

Sandboxed1.wsp              a9240922-c794-433c-acf7-0ce7863b46d0 Activated

The code:

Windows 7 Favorites and SharePoint

2010-11-06T17:37:00.001+01:00

One of the many cool features in Windows 7 is the Favorites

This is a list of “shortcut” that is display in the Windows Explore and in the “save as” dialog in programs like Word.

The Windows 7 Favorites works by creating a shortcut to folder and this goes for WebDav folders to.

To setup the a shortcut to a SharePoint site

To setup the shortcut and you only need to do this one time. Open Word and to go “save as” (the shortcut for this is F12), enter the url for the SharePoint site in the file name (Only the url!) and click enter or click on the save button. Then right click on the and select “Add current location to Farvorites” and wola your SharePoint is add and it is easy to browse next time when you want to save a document.

IE 9, site pinning, overlay icons and SharePoint

2010-11-01T21:14:00.001+01:00

One of the new thing in IE 9 is the site pinning. A cool new feature that allows a users to add a tab in IE9 to the taskbar. After the tab is added to the taskbar we can, from IE 9, interact with it, like overlay icons and ther is it where SharePoint comes in, as the data provider. I create an announcements list and read the current count from it and set the overlay icons to match the count all through JavaScript.

The results of adding two list items to announcements list

My code

This is the code in the PlaceHolderAdditionalPageHead content placeholder

<script src="http://ajax.Microsoft.com/ajax/jQuery/jquery-1.4.2.min.js" type="text/javascript"></script>

This is the code in the PlaceHolderMain content placeholder

<span id="statusInfomation">Loading...</span>
<script type="text/javascript">
var loadingIcon = "/_layouts/images/jumplist/search.ico"
 
var	getData = function()
{
	$.getJSON("/ie9test/_vti_bin/listdata.svc/Ie9TestAnno()/$count", function (data)
	{
		if(data != 0 && data < 6)
		{
			var icon = "/_layouts/images/jumplist/num_" + data + ".ico";
			setOverlayIcon(icon, "Now got " + data);
		}
		else if(data == 0)
		{
			setOverlayIcon("", "Now got " + data);
		}
	});
}
 
function setOverlayIcon(url, text)
{
	$("#statusInfomation").html(text);
	if(url != "")
	{
		window.external.msSiteModeSetIconOverlay(url, text);
	}
	else
	{
		window.external.msSiteModeClearIconOverlay();
	}
}
 
$(document).ready(function()
{
	setOverlayIcon(loadingIcon, "Loading...");
	setInterval(getData, 5000);
});
</script>

In function in line 21, is where I interact with the overlay icons, pure magic :D

- Happy IE 9 coding

List the controls added to a SPDelegate on a Website

2010-10-30T20:35:00.001+02:00

I need to inspect a delegate control, to discover which control there is add to it. So I create this PowerShell code to create a HttpContext, set the right Current.Items to be a real SharePoint context. Create a SharePoint Delegate Control, set the properties and then invoke CreateChildControls on it and out put the result on the screen.

[System.Reflection.Assembly]::LoadWithPartialName("System.Web") | Out-Null
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") | Out-Null
 
#parm
$delegateControlId = "SmallSearchInputBox"
$weburl = "/cwd"
$hosturl = "http://win-ugka6ujlm21"
$absoluteUrl = $hosturl+$weburl
 
#creating a fake httpcontext
$request = New-Object "System.Web.HttpRequest" "", $absoluteUrl, ""
$stringWriter = New-Object "System.IO.StringWriter"
$httpResponse = New-Object "System.Web.HttpResponse" $stringWriter
[System.Web.HttpContext]::Current = New-Object "System.Web.HttpContext" $request, $httpResponse
 
#HACK - Need a 'Microsoft.SharePoint.SPWeb' not a 'System.Management.Automation.PSObject'
[System.Web.HttpContext]::Current.Items["HttpHandlerSPWeb"] = (Get-SPSite -Identity $hosturl).OpenWeb($weburl, $false) 
 
#create and set properties for the delegate control
$dc = New-Object "Microsoft.SharePoint.WebControls.DelegateControl"
$dc.AllowMultipleControls = $true
$dc.ControlId = $delegateControlId
 
#create a method object and invole the method
$bindingFlags = [Reflection.BindingFlags] "NonPublic,Instance"
$method = $dc.GetType().GetMethod("CreateChildControls", $bindingFlags)
$method.Invoke($dc, @());
 
#list the child controls
$dc.Controls | %{
	$_.GetType().BaseType
}
 
#dispose
$StringWriter.Dispose | Out-Null
$httpResponse.Close() | Out-Null

The code:

Health Analyzer Demo

2010-09-21T16:44:00.001+02:00

What is health analyzer? This is the copy/pasta from msdns Overview of SharePoint Health Analyzer “SharePoint Health Analyzer is a feature in Microsoft SharePoint Foundation 2010 that enables administrators to schedule regular, automatic checks for potential configuration, performance, and usage problems in the server farm.”

So what we need to create a health analyzer rule?

Create a subclass of the SPHealthAnalysisRule or SPRepairableHealthAnalysisRule
Register the rule
Test/execute the rule

1) Create a subclass

In this demo I create a subclass of the SPRepairableHealthAnalysisRule and besides for implement the abstract properties from SPRepairableHealthAnalysisRule, I also override Check and Repair method.

The Check method is used to identify a single potential problem in the SharePoint environment. In this demo we are a test if a very important file exists on the c: drive.

public override SPHealthCheckStatus Check()
{
    FileInfo info = new FileInfo(@"c:\importantfile.txt");
    return info.Exists ? SPHealthCheckStatus.Passed : SPHealthCheckStatus.Failed;
}

Repair method is used to repair the problem that if the Check method return SPHealthCheckStatus.Failed. In the demo we just create the very important file on the c drive.

public override SPHealthRepairStatus Repair()
{
    try
    {
        if (Check().Equals(SPHealthCheckStatus.Failed))
        {
            FileInfo info = new FileInfo(@"c:\importantfile.txt");
            info.Create();
            return SPHealthRepairStatus.Succeeded;
        }
        else
        {
            return SPHealthRepairStatus.Succeeded;
        }
    }
    catch
    {
        //TODO: Log the error
        return SPHealthRepairStatus.Failed;
    }
}

2) Register the rule

Microsoft has a “How to: Create a Feature to Register a Health Rule” where they use a feature receiver to register rule with. But I’m big PowerShell fan, so it was naturally for me to create a simple PowerShell script to register and unregister.

Register PowerShell:

First we load the SharePoint DLL and my custom DLL. Then we call the static RegisterRules method with take the custom assembly as parameter. The RegisterRules return an IDictionary<Type, Exception>. We test if the IDictionary<Type, Exception> count is 0, if not, we display the exceptions by pipe the collection to the Format-List cmdlet.

[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") | Out-Null
$assembly = [System.Reflection.Assembly]::LoadWithPartialName("HealthAnalyzerDemo")
$exceptions = [Microsoft.SharePoint.Administration.Health.SPHealthAnalyzer]::RegisterRules($assembly);
if($exceptions -ne $null)
{
	if($exceptions.Count -eq 0)
	{
		Write-Host "All rules were registered.";
	}
	else
	{
		$exceptions | fl
	}
}
$assembly = $null

Unregister PowerShell:

The only difference between the register script and the unregister script is, instead of call the RegisterRules method we call the UnRegisterRules.

[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") | Out-Null
$assembly = [System.Reflection.Assembly]::LoadWithPartialName("HealthAnalyzerDemo")
$exceptions = [Microsoft.SharePoint.Administration.Health.SPHealthAnalyzer]::UnregisterRules($assembly);
if($exceptions -ne $null)
{
	if($exceptions.Count -eq 0)
	{
		Write-Host "All rules were unregistered.";
	}
	else
	{
		$exceptions | fl
	}
}
$assembly = $null

3) Test/execute the rule

Microsoft has a “How to: Test a Health Rule During Development” where they use a console application to test/execute the health rule. But this is so obviously a PowerShell thing :)

Execute rule PowerShell:

First we load the SharePoint DLL and my custom DLL. Then we create a new object of the rule class. Write the current return status from the Check method. Test if the status is equal to failed, if it is, we call the Repair method.

[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") | Out-Null
[System.Reflection.Assembly]::LoadWithPartialName("HealthAnalyzerDemo") | Out-Null
$checkIfFileOnDiskExistRuleRepair = New-Object "HealthAnalyzerDemo.HealthAnalyzers.CheckIfFileOnDiskExistRuleRepair"
$status = $checkIfFileOnDiskExistRuleRepair.Check()
Write-Host "Status for"$checkIfFileOnDiskExistRuleRepair.Summary"is:"$status
if($status -eq [Microsoft.SharePoint.Administration.Health.SPHealthCheckStatus]::Failed)
{
	Write-Host "Calling the Repair method"	
	Write-Host "Result:" $checkIfFileOnDiskExistRuleRepair.Repair()
}

Summary:

It's really easy to make rules, that will give the It-pros a fight change to managed and maintain the SharePoint platform. Microsoft has some “Guidelines for Designing Health Rules”.

My demo code

Using GeSHi to syntax higligh

2010-09-14T20:23:00.001+02:00

I just found this great tool to create syntax highligt in Windows Live Writer.

The tool is call GeSHi (Generic Syntax Highlighter) and has the following goals:

Support for a wide range of popular languages.
Easy to add a new language for highlighting.
Highly customisable output formats.

For more infomation:

Homepage: http://www.vcprojects.com/geshi/
Download & Discussion: http://www.vcprojects.com/geshi/download-discussion

Managing Custom Areas and Categories with Powershell

2010-09-14T20:11:00.001+02:00

The patterns & practices SharePoint Guidance team has posted this article on how to manag custom areas and categories i SharePoint 2010 http://msdn.microsoft.com/en-us/library/ff798462.aspx. But all the examples is written in C# (and that’s a good thing ) but I don’t want to have to use a feature receiver add my custom areas and categories, so I have create this demo PowerShell script, strongly inspire by the Microsoft article.

[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Practices.ServiceLocation") | Out-Null
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Practices.SharePoint.Common") | Out-Null
 
#EventSeverity		Description
#	None			Indicates no event entries are written. 
#	ErrorCritical	Indicates a problem state that needs the immediate attention of an administrator.
#	Error			Indicates a problem state requiring attention by a site administrator. 
#	Warning			Indicates conditions that are not immediately significant but that may eventually cause failure.
#	Information		Contains noncritical information provided for the administrator.
#	Verbose
 
#TraceSeverity		Description
#	None			Writes no trace information to the trace log file.
#	Unexpected		Represents an unexpected code path and actions that should be monitored.
#	Monitorable		Represents an unusual code path and actions that should be monitored. 
#	High			Writes high-level detail to the trace log file.
#	Medium			Writes medium-level detail to the trace log file.
#	Verbose			Writes low-level detail to the trace log file.
 
#Create a List<DiagnosticsArea> to collect the Diagnostics Area
$areaCollection = New-Object 'System.Collections.Generic.List[Microsoft.Practices.SharePoint.Common.Logging.DiagnosticsArea]'
 
#Add a DiagnosticsArea with the name Custom Area
$customArea = New-Object 'Microsoft.Practices.SharePoint.Common.Logging.DiagnosticsArea' -ArgumentList "Custom Area"
#Add a DiagnosticsCategory, to the Custom Areas DiagnosticsCategories collection, with the name Business logic, EventSeverity set to Warning and TraceSeverity to Medium
$customArea.DiagnosticsCategories.Add((New-Object 'Microsoft.Practices.SharePoint.Common.Logging.DiagnosticsCategory'("Business logic", ([Enum]::Parse([Microsoft.SharePoint.Administration.EventSeverity], 'Warning')), ([Enum]::Parse([Microsoft.SharePoint.Administration.TraceSeverity], 'Medium')))))
#Add a DiagnosticsCategory, to the Custom Areas DiagnosticsCategories collection, with the name Data layer, EventSeverity set to Error and TraceSeverity to Medium
$customArea.DiagnosticsCategories.Add((New-Object 'Microsoft.Practices.SharePoint.Common.Logging.DiagnosticsCategory'("Data layer", ([Enum]::Parse([Microsoft.SharePoint.Administration.EventSeverity], 'Error')), ([Enum]::Parse([Microsoft.SharePoint.Administration.TraceSeverity], 'Medium')))))
#Add the Custom Area to the List<DiagnosticsArea> collection
$areaCollection.Add($customArea)
 
#Create a new DiagnosticsArea witht the name Test Area and adds it to the List<DiagnosticsArea> collection
$areaCollection.Add((New-Object 'Microsoft.Practices.SharePoint.Common.Logging.DiagnosticsArea' -ArgumentList "Test Area"))
 
#Get a IConfigManager from the SharePointServiceLocator
$configManager =[Microsoft.Practices.SharePoint.Common.ServiceLocation.SharePointServiceLocator]::GetCurrent().GetInstance([Microsoft.Practices.SharePoint.Common.Configuration.IConfigManager])
 
#Create a new DiagnosticsAreaCollection with the IConfigManager as parameter
$configuredAreas = New-Object 'Microsoft.Practices.SharePoint.Common.Logging.DiagnosticsAreaCollection' $configManager
 
#loop through the newly collection of diagnosticsareas
$areaCollection | % {
 
	#get the instance from the current configuration
	$existingArea = $configuredAreas[$_.Name]
 
	#if the area the is null, we add add the area from the List<DiagnosticsArea> collection
	#else we loop through the collection we got from current configuration
	if($existingArea -eq $null)
	{
		$configuredAreas.Add($_)
	}
	else
	{	
		#loop through the collection we got from current configuration
		$customArea.DiagnosticsCategories | % {
 
			#get the category instance from the $existingArea (DiagnosticsArea)
			$existingCategory = $existingArea.DiagnosticsCategories[$_.Name]
			#if the category is null, we add to the current configuration
			if($existingCategory -eq $null)
			{
				$existingArea.DiagnosticsCategories.Add($_);
			}
		}
	}
}
#save the current configuration
$configuredAreas.SaveConfiguration()

The demo code.

What new and download link to SDK for SharePoint 2010

2010-09-12T10:58:00.001+02:00

Download link:

SDK for SharePoint 2010 Reference: Software Development Kit download

What’s new links:

Proud to present the next release of SharePoint Manager

2010-08-29T20:13:00.001+02:00

This release includes new features and a bug fix:

ServiceProxies

ApplicationProxies

ReadOnly mode

Feature
Delete

External list error handling
Site Subscriptions

Download the new release here: http://spm.codeplex.com/releases/view/51438

Querying for features with PowerShell

2010-08-29T16:30:00.001+02:00

On my current project we have a feature with a model that adds some aspx files in a document library. My problem is when I add a new file to the model manifest the new aspx is not now added to the document library, on WSP solution upgrade. The solution for this is to “re-active” the feature with the model. This is easily done, either through the GUI or by PowerShell “Enable-SPFeature –Force”, but the problem is I don’t know where the feature is already activated and I don’t won to look through over all the webs to check if the feature is activated, so I need to query for where the feature is activated. This is done by calling a method called “QueryFeatures” http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spfeaturequeryresultcollection.aspx. This method can be found on the SPContentDatabase, SPWebApplication, SPWebService, and the SPSite classes.

In my example I query the SPWebService for two features and then re-active by calling Enable-SPFeature –Force N.B. this don’t disable the feature and there for, if there are a feature receiver attach to the feature, with FeatureDeactivating method, this well not be call.

My PowerShell (Code update 11/9-2010)

$featureGuids = ("41ee3cfa-0863-4c1c-9f6b-41697ff44ee0", "7176542e-ec21-411e-86b3-24abb5251a0b")
$contentService = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$featureGuids | % { $contentService.QueryFeatures([Guid]$_) } | % {
Enable-SPFeature -Identity $_.DefinitionId -Url $_.Parent.Url -Force
}

OData, REST and this cool program call LINQPad

2010-07-22T19:33:00.001+02:00

I was watching this video http://azgroups.nextslide.com/odata-begins with Scott Hanselman about OData. OData is cool in itself, but what exited me most was then Scott showed this program call LINQPad http://www.LINQpad.net. LINQPad is not only a tool to build your LINQ statement in but also to execute against a data source. In Scott example, he use the http://odata.netflix.com/ as the data source and create a LINQ query that LINQPad then translator in to a REST statement, sooo cool :D

A simple walk through to query netflix.com

1) Open LINQPad and click on “Add connection”

2) Choose WCF Data Services as the data content and click next.

3) Insert the url to Netflix.com (http://odata.netflix.com/Catalog/) and click OK

4) Set the database to Netflix.com

5) Type a LINQ query like this

6) Select the SQL view instead of Results and wola your REST statement.

PowerShell, events and file watcher

2010-07-17T08:59:00.001+02:00

A simple script that create a file watcher on a specific folder and collect the events in a global variable.

function watch-folder {
    param([string]$path)
    $fileSystemWatcher = new-object System.IO.FileSystemWatcher
    $fileSystemWatcher.Path = $path
    $global:events = new-object system.data.datatable
    [void] $events.Columns.Add("Time", [datetime])
    [void] $events.Columns.Add("Full path", [string])
    [void] $events.Columns.Add("Change type", [string])
    $event = {
        [void] $events.Rows.Add([datetime]::Now, $eventArgs.FullPath, $eventArgs.ChangeType)
    }
    [void](Register-ObjectEvent -InputObject $fileSystemWatcher -EventName Created -Action $event)
    [void](Register-ObjectEvent -InputObject $fileSystemWatcher -EventName Changed -Action $event)
    [void](Register-ObjectEvent -InputObject $fileSystemWatcher -EventName Deleted -Action $event)
}
cls
watch-folder "c:\Temp"
"foobar" > c:\temp\test.txt
del c:\temp\test.txt
$global:events
get-eventsubscriber -force | unregister-event -force

patterns & practices SharePoint Guidance - SharePoint 2010 Release now Live on MSDN!!

2010-07-12T15:19:00.001+02:00

Copy/paste from MSDN:

The following releases are designed to help solution developers and architects make the right decisions and follow proven practices when building applications for SharePoint

MSDN link : http://msdn.microsoft.com/en-us/library/ff770300.aspx

Codeplex link: http://spg.codeplex.com/