CP - Help, Answers, Tips, Questions about software, hardware and other stuff » SharePoint

Creating a Wiki Page template For SharePoint 2010 Foundation

Jeramy — Tue, 01 Nov 2011 05:46:13 +0000

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">Introduction

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">As
I have ever written several time in my previous posts, one of the severe
limitation of SharePoint Foundation is that the Wiki Pages are based on a single
template wkpstd.aspx located at

C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\TEMPLATE\DocumentTemplates

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">If
you try to add a wiki page programmatically to a wiki page library of
a SharePoint Foundation team site and you want it to be ghosted you must
use the method SPFileCollection.Add with this signature :

href="http://msdn.microsoft.com/en-us/library/aa543347.aspx"> color=#0033cc>Add(String, SPTemplateFileType)

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">And
pass the reference of the wiki page template wkpstd.aspx to the SPTemplate
parameter. If you use the other methods, you will be able to add a wikipage, but
it will be unghosted.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">I
am now going to show you a very amazing workaround to use another template than
the wkpstd.aspx one and will process in two steps. First I will
demonstrate it so as you can easily understand its principle then I will provide
a programmatic way of doing it.

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">Demonstration

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Start
creating your new template by duplicating the wkpstd.aspx and rename it
wkpcustom.aspx, then perform a little operation of customization in order each
page based on this new template can tell its name :

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">In
the page directive section add the namespace System.Diagnostics because the wiki
pages will tell their nam in the debugView…

<% size=2>@ color=#a31515 size=2>Import color=#ff0000 size=2>Namespace color=#0000ff size=2> size=2>=”System.Diagnostics” %>

Then, at the top of the PlaceHolderMain section paste this code:

size=2>

size=2>protected size=2>override
size=2>void OnPreInit( size=2>EventArgs
e)
{
size=2> base size=2>.OnPreInit(e);

color=#2b91af size=2> Debug size=2>.WriteLine( size=2>SPContext size=2>.Current.File.Name);
}

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Then,
we are going to prepare a feature to reference this wkpcustom.aspx file in a
SharePoint Foundation wiki page library.

Provisioning.SPF_WikiPages

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>xml style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="FONT-FAMILY: 'Courier New'; COLOR: red; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>version style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>= style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>“1.0“
encoding style="COLOR: blue">=“utf-8“ style="COLOR: blue">?> "urn:schemas-microsoft-com:office:office" />

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>< style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>Feature style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="FONT-FAMILY: 'Courier New'; COLOR: red; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>Id style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>= style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>“ style="COLOR: blue">00BFEA71-2062-426C-90BF-714C59600AAA“

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: red; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>Title style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>= style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>“Adding pre populate wiki
pages“

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: red; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>Description style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>= style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>“This feature will add pre-populate wiki
pages to the site pages wiki library of this site“

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: red; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>Version style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>= style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>“1.0.0.0“

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: red; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>Scope style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>= style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>“Web“

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: red; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>Hidden style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>= style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>“false“

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: red; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>DefaultResourceFile style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>= style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>“core“

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: red; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>xmlns style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>= style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>“ style="COLOR: blue">http://schemas.microsoft.com/sharepoint/“ style="COLOR: blue">>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-no-proof: yes">< style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-no-proof: yes">ElementManifests style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-no-proof: yes">>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-no-proof: yes"> style="mso-spacerun: yes"> < style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-no-proof: yes">ElementManifest style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-no-proof: yes">
style="FONT-FAMILY: 'Courier New'; COLOR: red; FONT-SIZE: 10pt; mso-no-proof: yes">Location style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-no-proof: yes">= style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-no-proof: yes">“ style="COLOR: blue">elements.xml“
/>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-no-proof: yes"> style="mso-spacerun: yes"> style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-no-proof: yes">ElementManifests style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-no-proof: yes">>

style="LINE-HEIGHT: 115%; FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-no-proof: yes"> style="LINE-HEIGHT: 115%; FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-no-proof: yes">Feature style="LINE-HEIGHT: 115%; FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-no-proof: yes">>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>< style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>Elements style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="FONT-FAMILY: 'Courier New'; COLOR: red; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>xmlns style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>= style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>“ style="COLOR: blue">http://schemas.microsoft.com/sharepoint/ color=#000000>“ style="COLOR: blue">>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> < style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>Module style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="FONT-FAMILY: 'Courier New'; COLOR: red; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>Url style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>= style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>“ style="COLOR: blue">SitePages“ style="COLOR: blue"> >

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>
< style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>File style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="FONT-FAMILY: 'Courier New'; COLOR: red; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>Url style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>= style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>“ style="COLOR: blue">wkpcustom.aspx“ style="COLOR: blue"> Type style="COLOR: blue">=“ style="COLOR: blue">GhostableInLibrary“ style="COLOR: blue">> style="COLOR: #a31515">File style="COLOR: blue">>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-no-proof: yes"> style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-no-proof: yes">Module style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-no-proof: yes">>

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Then,
install the feature and activate it for one of the team site of your Farm and
you will have a reference to your page in the site pages library of this team
site.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">And
because this file was provisioned by a feature, although there is in line code
in it, if you display the wiki page using this file, it will work, the code
will run and will write the name of the page in the debugview.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">But,
wait a minute, this file is already a template. It is a template for just one
page within the site pages library but it is exactly like the wkpstd.aspx for
the other pages. So assume we could have several pages within the library based
on this file we would have created a new template. I see some of you
smiling…

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Now
is the time to use another workaround I have already shown in a previous post to
open our library in explorer mode.
So switch to shared documents library,
open it in explorer mode, then using the explorer folder navigation go back to
the site pages library but in explorer mode now

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">then
go back to the site pages library within the SharePoint UI. You will notice that
the page is renamed and if you displayed it, its name in the debugview has
changed either. While renamed, the page remains in its ghosted state and linked
to the “template”.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Now
deactivate the feature, then reactivate it and you will have a new page
wkpcustom.aspx beside the “page 01.aspx” and the two pages are linked to the
same file on the server, so if we display one then the other, debugview will
trace the two names based on the code of an unique file on the server: we have
created our first custom template for a wiki page library in SharePoint
Foundation!

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">Coding
the sequence

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">this
applicative page called from your site will provision 9 pages in your site
page library pointing on the same unique template wkpcustom.aspx located in the
feature folder. If you modify the file in the folder, you will modify the 9
pages

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; BACKGROUND: yellow; FONT-SIZE: 10pt; mso-no-proof: yes; mso-highlight: yellow"><% style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-no-proof: yes">@ style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-no-proof: yes"> style="COLOR: #a31515">Page Language style="COLOR: blue">=”C#” style="COLOR: red">AutoEventWireup style="COLOR: blue">=”true” Inherits style="COLOR: blue">=”Microsoft.SharePoint.WebControls.LayoutsPageBase”

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-no-proof: yes"> style="mso-spacerun: yes"> style="COLOR: red">DynamicMasterPageFile style="COLOR: blue">=”~masterurl/default.master” style="BACKGROUND: yellow; mso-highlight: yellow">%>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; BACKGROUND: yellow; FONT-SIZE: 10pt; mso-no-proof: yes; mso-highlight: yellow">

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; BACKGROUND: yellow; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes; mso-highlight: yellow"
lang=EN-US><% style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>@ style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> Assembly style="COLOR: red">Name=”System.Core,
Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089″ style="BACKGROUND: yellow; mso-highlight: yellow">%>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; BACKGROUND: yellow; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes; mso-highlight: yellow"
lang=EN-US><% style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>@ style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> Import style="COLOR: red">Namespace style="COLOR: blue">=”Microsoft.SharePoint” style="BACKGROUND: yellow; mso-highlight: yellow">%>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; BACKGROUND: yellow; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes; mso-highlight: yellow"
lang=EN-US><% style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>@ style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> Import style="COLOR: red">Namespace style="COLOR: blue">=”Microsoft.SharePoint.Administration” style="BACKGROUND: yellow; mso-highlight: yellow">%>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; BACKGROUND: yellow; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes; mso-highlight: yellow"
lang=EN-US><% style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>@ style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> Import style="COLOR: red">Namespace style="COLOR: blue">=”System.Text” style="BACKGROUND: yellow; mso-highlight: yellow">%>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; BACKGROUND: yellow; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes; mso-highlight: yellow"
lang=EN-US><% style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>@ style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> Import style="COLOR: red">Namespace style="COLOR: blue">=”System.Linq” style="BACKGROUND: yellow; mso-highlight: yellow">%>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; BACKGROUND: yellow; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes; mso-highlight: yellow"
lang=EN-US><% style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>@ style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> Assembly style="COLOR: red">Name=”Microsoft.SharePoint,
Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” style="BACKGROUND: yellow; mso-highlight: yellow">%>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="BACKGROUND: yellow; mso-highlight: yellow">

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>< style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>asp style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>: style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>content style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> id style="COLOR: blue">=”PageHead” style="COLOR: red">contentplaceholderid style="COLOR: blue">=”PlaceHolderAdditionalPageHead” style="COLOR: red">runat style="COLOR: blue">=”server”>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>asp style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>: style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>content style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>< style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>asp style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>: style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>content style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> id style="COLOR: blue">=”Main” style="COLOR: red">contentplaceholderid style="COLOR: blue">=”PlaceHolderMain” style="COLOR: red">runat style="COLOR: blue">=”server”>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="COLOR: blue">protected override
void OnLoad( style="COLOR: #2b91af">EventArgs e)

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>
{

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
base.OnLoad(e);

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
SPWeb myWeb = SPContext.Current.Web;

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
myWeb.AllowUnsafeUpdates = style="COLOR: blue">true;

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
for ( style="COLOR: blue">int i = 1; i < 10; i++)

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
{

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
if (myWeb.Features[ style="COLOR: blue">new Guid( style="COLOR: #a31515">"{00BFEA71-2062-426C-90BF-714C59600AAA}")] !=
null)

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
{

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
myWeb.Features.Remove( style="COLOR: blue">new Guid( style="COLOR: #a31515">“{00BFEA71-2062-426C-90BF-714C59600AAA}”));

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
}

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
myWeb.Features.Add(new style="COLOR: #2b91af">Guid( style="COLOR: #a31515">“{00BFEA71-2062-426C-90BF-714C59600AAA}”));

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
SPList myList = myWeb.Lists["Site
Pages"];

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
SPListItem myItem = style="COLOR: blue">null;

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
SPContext.Current.Web.AllowUnsafeUpdates = style="COLOR: blue">true;

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
foreach (SPListItem anItem style="COLOR: blue">in myList.Items)

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
{

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
if (anItem.Name == style="COLOR: #a31515">“wkpcustom.aspx”)

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
{

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
myItem = anItem;

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
}

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
string destinationUrl = myWeb.Url +
“/” + myList.RootFolder.Url + style="COLOR: #a31515">“/” + style="COLOR: #a31515">“Wiki_page0″ + i + style="COLOR: #a31515">“.aspx”;

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
myItem.File.MoveTo(destinationUrl);

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
myItem.File.Update();

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
myWeb.Features.Remove(new style="COLOR: #2b91af">Guid( style="COLOR: #a31515">“{00BFEA71-2062-426C-90BF-714C59600AAA}”));

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
}

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="mso-spacerun: yes">
lbl1.Text = “Your files has been
provisionned successfully…”;

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>
}

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>< style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>asp style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>: style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>Label style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> runat style="COLOR: blue">=”server” ID style="COLOR: blue">=”lbl1″ style="COLOR: blue">>asp style="COLOR: blue">:Label style="COLOR: blue">>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>asp style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>: style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>content style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>< style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>asp style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>: style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>content style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> id style="COLOR: blue">=”PageTitle” style="COLOR: red">contentplaceholderid style="COLOR: blue">=”PlaceHolderPageTitle” style="COLOR: red">runat style="COLOR: blue">=”server”>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>Provisioning Team Site Wiki Pages

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>asp style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>: style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>content style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>< style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>asp style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>: style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>content style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> id style="COLOR: blue">=”PageTitleInTitleArea” style="COLOR: red">contentplaceholderid style="COLOR: blue">=”PlaceHolderPageTitleInTitleArea”

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US> style="COLOR: red">runat style="COLOR: blue">=”server”>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>Provisioning Team Site Wiki Pages

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN-US; mso-no-proof: yes"
lang=EN-US>

class=MsoNormal> style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-no-proof: yes"> style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-no-proof: yes">asp style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-no-proof: yes">: style="FONT-FAMILY: 'Courier New'; COLOR: #a31515; FONT-SIZE: 10pt; mso-no-proof: yes">content style="FONT-FAMILY: 'Courier New'; COLOR: blue; FONT-SIZE: 10pt; mso-no-proof: yes">>

face=Calibri>

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">And
now, I have chaged the instruction of the name displaying in the template, and I
have called back the 9 pages and here is the result.

Check it out:MOSS How to …

Use Linq inside a Script Block of an Application Page – SharePoint minimal configuration for Linq When developing for SharePoint you maybe use Linq. Assume you are developing a new piece of code and to improve ...
Using XPath to manage data returned by a SharePoint Web Service Topic: Using XPath to navigate through elements and attributes in an XML document returned by a SharePoint Web Service. This article proposes ...
Populate an ASP .Net Treeview from a SQL self-join table I had last week an ASP .net TreeView control to fill from a self-join table. I looked on the Internet ...
Adding Breadcrumb Navigation for SharePoint Application Pages Programmatically When creating a new Application Page (an .aspx page deployed to the c:\program files\common files\microsoft shared\web server extensions\template\layouts directory) you can ...
Adding a custom control to the SharePoint 2010 Team Site Wiki Page Template ( wkpstd.aspx ) programmatically Topic This is maybe my last post about the Team Site Wiki Page customization with the aim of exceeding its limitations. This time ...

Configuring SharePoint 2010 Foundation for Internet-facing publishing

Rhyled — Mon, 24 Oct 2011 01:46:23 +0000

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">Introduction

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">I
am starting a set of posts regarding the ability of ShaePoint 2010 foundation to
be used to build Internet-facing web sites. In this one we are just going to
perform configuration and creation operations so as we can obtain a SharePoint
Foundation site collection that can be used to publish content on the Internet
and therefore, available for anonymous users.

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">Business
benefits – The “why” part of the post
style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">In
SharePoint 2007 the Internet-facing publishing was rather based on the use of
the publishing part of SharePoint, its CMS.

However, the team sites that
were a part of the collaboration area of SharePoint 2007 are now with the new
wiki pages of SharePoint 2010 a way to help people to publish formal content.
The team sites are now described in the SharePoint 2010 documentation as a
solution to encourage one-to-many communication and also a solution to offer a
structured exchange of information.

Therefore the team sites of
SharePoint Foundation are now mature enough to be used as a base to build
Internet-facing web sites and are a new and more cost effective opportunity
offered by SharePoint 2010 to publish content on the Internet. The free
SharePoint Foundation team sites can be now seen as a severe competitor to the
licensed SharePoint CMS!

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px"> href="http://msdn.microsoft.com/en-us/library/ee721051.aspx#section1">Comparison
of Enterprise Wikis with Team Sites

href="http://technet.microsoft.com/en-us/library/cc288638.aspx#Section2c">Plan
Internet presence sites (SharePoint 2010 Foundation)

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">Audience

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">I
will avoid using development operations in this first post in order it can be
useful to system administrators. Of course it is also targetted for developers
so as they can configure their development machine, but they won’t have to
launch Visual Studio here.

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">1
- Extending an existing SharePoint Foundation Web Application
style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Assume
you have created a SharePoint Foundation web application using NTLM
authentication (that is the default mode).
Go to the SharePoint 2010 Central
Administration of your SharePoint Farm, click the “Manage web applications” link
then on the displayed list of the available
web application select the one you want to open to anonymous users.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Type
the name of the new web application
Type 80 for port
Define a host
header
Select Allow Anonymous because we are planning anonymous access
For
the zone, choose Internet, because we plan to extend the existing web
application for an Internet access.

href="http://3.bp.blogspot.com/-Xa3md2Gcz0k/TqRNNtUCcFI/AAAAAAAAB4U/DVv_CEgZm2c/s1600/configuring%2Bsharepoint%2Bfoundation%2Bfor%2BInternet%2Bfacing%2B-%2B010%2B-%2BExtending%2Bthe%2Bweb%2Bapplication%2B1.jpg"> style="WIDTH: 320px; HEIGHT: 154px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666739129036206162 border=0 alt=""
src="http://3.bp.blogspot.com/-Xa3md2Gcz0k/TqRNNtUCcFI/AAAAAAAAB4U/DVv_CEgZm2c/s320/configuring%2Bsharepoint%2Bfoundation%2Bfor%2BInternet%2Bfacing%2B-%2B010%2B-%2BExtending%2Bthe%2Bweb%2Bapplication%2B1.jpg">

href="http://1.bp.blogspot.com/-l9uNsSzzo-0/TqRNNdTtOtI/AAAAAAAAB4M/I5D_ek_9QJI/s1600/configuring%2Bsharepoint%2Bfoundation%2Bfor%2BInternet%2Bfacing%2B-%2B020%2B-%2BExtending%2Bthe%2Bweb%2Bapplication%2B2.jpg"> style="WIDTH: 320px; HEIGHT: 154px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666739124739848914 border=0 alt=""
src="http://1.bp.blogspot.com/-l9uNsSzzo-0/TqRNNdTtOtI/AAAAAAAAB4M/I5D_ek_9QJI/s320/configuring%2Bsharepoint%2Bfoundation%2Bfor%2BInternet%2Bfacing%2B-%2B020%2B-%2BExtending%2Bthe%2Bweb%2Bapplication%2B2.jpg">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Then,
click the “OK” button to create the web application.
Nothing has
changed in the web application list, but if you navigate to the Alternate Access
Mappings page of the central administration (in the System Settings
section), then click on the “Edit Public Zone URLs” link and select the
extended web application you will notice taht the zone was properly created.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

href="http://1.bp.blogspot.com/-6jkiiGVDXgc/TqRNM4IX8GI/AAAAAAAAB4A/hNeVSSHgqiY/s1600/configuring%2Bsharepoint%2Bfoundation%2Bfor%2BInternet%2Bfacing%2B-%2B030%2B-%2Balternate%2Baccess%2Bmapping%2B_%2Bedit%2Bzone%2Bursl%2B_%2BInternet%2Bzone%2Bcreated.jpg"> style="WIDTH: 320px; HEIGHT: 212px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666739114760204386 border=0 alt=""
src="http://1.bp.blogspot.com/-6jkiiGVDXgc/TqRNM4IX8GI/AAAAAAAAB4A/hNeVSSHgqiY/s320/configuring%2Bsharepoint%2Bfoundation%2Bfor%2BInternet%2Bfacing%2B-%2B030%2B-%2Balternate%2Baccess%2Bmapping%2B_%2Bedit%2Bzone%2Bursl%2B_%2BInternet%2Bzone%2Bcreated.jpg">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

href="http://4.bp.blogspot.com/-pH4VSLdu_hA/TqRNMg3Tj2I/AAAAAAAAB3w/s8jBZ0eAAcc/s1600/configuring%2Bsharepoint%2Bfoundation%2Bfor%2BInternet%2Bfacing%2B-%2B040%2B-%2BIIS7%2B_%2B%2BInternet%2Bzone%2BIIS%2Bweb%2Bsite%2Bcreated.jpg"> style="WIDTH: 320px; HEIGHT: 151px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666739108514598754 border=0 alt=""
src="http://4.bp.blogspot.com/-pH4VSLdu_hA/TqRNMg3Tj2I/AAAAAAAAB3w/s8jBZ0eAAcc/s320/configuring%2Bsharepoint%2Bfoundation%2Bfor%2BInternet%2Bfacing%2B-%2B040%2B-%2BIIS7%2B_%2B%2BInternet%2Bzone%2BIIS%2Bweb%2Bsite%2Bcreated.jpg">

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">2 -
Testing the anonymous acces

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">As
we have defined previously a custom host header for our Internet site we have to
modify the host file of our development machine in order to be able to acces the
site as an anonymous user.
So open the hosts file of your machine located at
:

C:\Windows\System32\drivers\etc

127.0.0.1 www.mycompany.com

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px"> Now
open a browser and browse to this url. You access your SharePoint team site as
an anonymous user and simulate an Internet acces.

href="http://2.bp.blogspot.com/-W-pUTWeO_H0/TqRhM9Q8lTI/AAAAAAAAB4k/Ibftv8qzaUw/s1600/configuring%2Bsharepoint%2Bfoundation%2Bfor%2BInternet%2Bfacing%2B-%2B050%2B-%2B%2Baccessing%2Bsharepoint%2Bfoundation%2Bteam%2Bsite%2Bthrough%2Bthe%2BInternet.jpg"> style="WIDTH: 320px; HEIGHT: 152px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666761106370893106 border=0 alt=""
src="http://2.bp.blogspot.com/-W-pUTWeO_H0/TqRhM9Q8lTI/AAAAAAAAB4k/Ibftv8qzaUw/s320/configuring%2Bsharepoint%2Bfoundation%2Bfor%2BInternet%2Bfacing%2B-%2B050%2B-%2B%2Baccessing%2Bsharepoint%2Bfoundation%2Bteam%2Bsite%2Bthrough%2Bthe%2BInternet.jpg">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">
You
will notice that the SharePoint Forms pages are also accessible, so accessible
to anonymous users. For example, anonymous users might be able to get to
http://www.mycompany.com/SitePages/Forms/AllPages.aspx. Typically you don’t want
this, so how do you prevent anonymous users from accessing these
pages?
Therefore, we are gonig to activate the lockdown
feature especially provided by Microsoft for avoiding this
problem.

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">3 -
Activating the locdown Feature

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">The
Lockdown feature actually named ViewFormPagesLockDown is located in the
SharePoint Features folder as the other out of the box ones. So to activate it
for our site collection we just have to execute the following command

stsadm -o activatefeature -name ViewFormPagesLockDown -url

http://localhost/

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">After
having done that, because our site collection was already configured to allow
anonymous acces, we need to go disable it, then enable it again. Go to the
_layouts/setanon.aspx page, switch anonymous access nothing, click OK, then go
back and set it to Entire site, click OK.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">
Anonymous users should now get an authentication prompt when they try to
navigate to a forms page. For example, try http://www.mycompany.com/SitePages/Forms/AllPages.aspx.

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">4 -
Setting custom error page for error 401 (forbidden)

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Now
we are going to do an amazing thing. We are going to change the web.config file
of the web application corresponding to the Internet access so as
anonymous user won’t be prompted anymore for authentication if they try to acces
to an unauthorized url but be redirected on a custom 401 error page within the
site.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">So
first go to your site with at least contributor permissions by using NTLM access
and create a custom 401 error page in the site pages library of your site.
Assume we call it unauthorized so as its url will be href="http://www.mycompany.com/sitepages/unauthorized.aspx">http://www.mycompany.com/sitepages/unauthorized.aspx.
Type a meessage of access denied and save the page.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Then, open
the web.config file of the Internet zone web application and locate the handlers
end tag within the system.webSever and paste the following httpErrors
sequence.

existingResponse=”Auto”>

/>

path=”/sitepages/unauthorized.aspx” responseMode=”ExecuteURL”
/>

color=#c0c0c0>

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px"> After
restarting your application pool by reloading a page of your site with anonymous
acces, you will notice an amazing thing: each time an anonymous user will try to
access to a non authorized ressource, instead of being prompted for an NTLM
authentification, he will be redirected to the custom 401 error page of your
site and he will still have your site navigation links available and be
able to keep browsing.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">And
the most amazing is you will have the same result while clicking the sign in
link.
So of course don’t do that if you plan to use an Internet access for
contributing on your site or for administrating it…

And don’t forget that this will have an impact on the whole web application since we have modified the web.config, so it won’t be possible to obtain a different behaviour for another site collection within this web application.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">
It is all that we can do for now by just performing configuration operations.

Of course, don’t forget to modify the navigation within the SharePoint 2010 UI to hide all the links that could lead to an access denied for anonymous users. In short, you should let only the links pointing on a subsite, a Site Page or a specific document.

In the next post, we are going to use Visual Studio to start customizing our site…

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">5 -
Aknowledgements

Nick whose article helped me for custom errors, I have just noticed that he also lives and works in Montreal…

Tyler Butler
of the ECM team blog who was by his publications of a big help in the realization of my projects for the internet and who made me discover the existence of the lockdown feature…

Check it out:MOSS How to …

Creating a custom document library for SharePoint 2010 Introduction It seems that it is not that obvious to find clear documentation to create a custom document library for SharePoint 2010. ...
Testing cross browser compatibility for SharePoint 2010 You will obtain the best user experience by using Internet Explorer 7 Introduction ...
Using XPath to manage data returned by a SharePoint Web Service Topic: Using XPath to navigate through elements and attributes in an XML document returned by a SharePoint Web Service. This article proposes ...
Populate an ASP .Net Treeview from a SQL self-join table I had last week an ASP .net TreeView control to fill from a self-join table. I looked on the Internet ...
Adding a custom control to the SharePoint 2010 Team Site Wiki Page Template ( wkpstd.aspx ) programmatically Topic This is maybe my last post about the Team Site Wiki Page customization with the aim of exceeding its limitations. This time ...

Creating a custom document library for SharePoint 2010

limaye.aashish — Sat, 22 Oct 2011 19:01:36 +0000

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">Introduction

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 5px; MARGIN: 1px 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">It
seems that it is not that obvious to find clear documentation to create a
custom document library for SharePoint 2010.
Most of the Microsoft
documentation is now based on using Visual Studio 2010 and are more focused on
the lists than on the document libraries.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 5px; MARGIN: 1px 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">By
the way document libraries in SharePoint 2010 seems to has become lists, but the
lack of documentation regarding the creation of custom lists remains anyway, so
after having perform some successful trials I have decided to publish a step by
step guide.

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">Functional
benefits

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 5px; MARGIN: 1px 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">I
won’t spend much time in this post explaining the functional benefits of
creating a custom document library because I plan to publish soon a new post
explaining the difference between a custom list and a list instance and the
functional benefits and drawbacks of each. But think carefully before
creating a custom document library.
I have created one in a previous project
for MOSS 2007 and had serious problems when migrating to SharePoint 2010.
In
most of the cases, a list instance is enough so if it is possible, avoid
creating a custom list or document library. In a general way, avoid as much as
possible to create custom CAML definitions for sites, lists and so
on…

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">Required
steps for creating a custom SharePoint 2010 document library

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 5px; MARGIN: 1px 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">1
- Duplicate the native DocumentLibrary feature
2 – Change the attributes
of the Feature tag of the Feature.xml file
3 – Change the attributes of the
ListTemplate tag of the DocumentLibrary.xml file
4 – Rename the DocLib folder
located in the DocumentLibrary folder
5 – Install the feature
6 – Activate
the feature for a specific site
7 -Test

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">Detailed
operations

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">1
- Duplicating the native DocumentLibrary feature

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 5px; MARGIN: 1px 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Locate
the folder of th DocumentLibrary feature located in: C:\Program Files\Common
Files\Microsoft Shared\Web Server Extensions\TEMPLATE\FEATURES
Copy and
paste the folder and rename it. Assume we rename it
MyCompany.MyCustomDocumentLibrary.

href="http://1.bp.blogspot.com/-yKgwpsUxIfY/TqMBMHh3MNI/AAAAAAAAB3U/Y3zardk_1M8/s1600/Creating%2Ba%2Bcustom%2Bdocument%2Blibrary%2Bfor%2Bsharepoint%2B2010%2B-%2B010%2B-%2Bduplicating%2BDocuementLibrary%2Bfolder.jpg"> style="WIDTH: 320px; HEIGHT: 239px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666374063853351122 border=0 alt=""
src="http://1.bp.blogspot.com/-yKgwpsUxIfY/TqMBMHh3MNI/AAAAAAAAB3U/Y3zardk_1M8/s320/Creating%2Ba%2Bcustom%2Bdocument%2Blibrary%2Bfor%2Bsharepoint%2B2010%2B-%2B010%2B-%2Bduplicating%2BDocuementLibrary%2Bfolder.jpg">

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">2
- Changing the attributes of the Feature tag of the Feature.xml file and adding
some more attributes

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">ID
Change
the ID of the feature. I usually change the last figures by the new type of the
list. Assume the new type is 10001 (it is not recommended to use a new type
smaller than 10000), the new ID of the feature of my custom document library
will be 00BFEA71-E717-4E80-AA17-D0C71B310001.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Title
The
title will appear in the UI of SharePoint 2010 in the “Manage Site Features”
page (because the attribute Scope is set to Web).

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Description
The
description will also appear in the UI of SharePoint 2010 in the “Manage Site
Features” page (Because the attribute Scope is set to Web).

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Hidden
Change
the value of the attribute to FALSE in order to see the feature in the “Manage
Features” page of your SharePoint 2010 so as you can activate it manually and
allow a site administrator to activate it.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">AlwaysForceInstall=”TRUE”
This
will avoid having an error at deployment time if you deploy this feature in a
SharePoint solution (.wsp file) by retracting, removing the old version of your
solution and re-deploying a new one.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">ImageUrl
I
have created a folder for MyCompany located in the SharePoint 2010 IMAGES folder
located at:
C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\TEMPLATE\IMAGES
(I use a part of the SharePoint summit logo
because I was speaker at this summit last year in Quebec and plan to be speaker
on 2012 at Toronto and Quebec.)

size=2> size=2>xml
size=2>version size=2>=“ color=#0000ff size=2>1.0“ size=2> size=2>encoding size=2>=“ color=#0000ff size=2>utf-8 size=2>“ size=2>?>
< size=2>Feature size=2> size=2>Id size=2>=“ color=#0000ff size=2>00BFEA71-E717-4E80-AA17-D0C71B310001 size=2>“

size=2>
Title size=2>=“ color=#0000ff size=2>MyCompany MyCustom Document Library size=2>“
size=2>
Description size=2>=“ color=#0000ff size=2>Allow a custom document library to be created within this
site“
color=#ff0000
size=2>
Version size=2>=“ color=#0000ff size=2>1.0.0.0“
color=#ff0000 size=2> size=2>
Scope size=2>=“ color=#0000ff size=2>Web“
color=#ff0000 size=2> size=2>
Hidden size=2>=“ color=#0000ff size=2>False“
color=#ff0000 size=2> size=2>
AlwaysForceInstall size=2> =“ color=#0000ff size=2>TRUE“
color=#ff0000 size=2> size=2>
ImageUrl
=“ color=#0000ff size=2>MyCompany/sharePointSummitLogo.jpg size=2>“
size=2>
DefaultResourceFile size=2>=“ color=#0000ff size=2>core“ size=2>
size=2> size=2>
xmlns size=2>= color=#0000ff size=2> href="http://schemas.microsoft.com/sharepoint/">http://schemas.microsoft.com/sharepoint/ size=2> size=2>>
                 < color=#a31515 size=2> size=2>ElementManifests color=#0000ff
size=2>>

size=2>< size=2>ElementManifest color=#0000ff size=2> color=#ff0000 size=2>Location color=#0000ff size=2>=“ size=2> size=2>ListTemplates\DocumentLibrary.xml“ color=#0000ff size=2>
/>

size=2>ElementManifests color=#0000ff size=2>>
color=#a31515 size=2>Feature color=#0000ff size=2>>

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">3
- Changing the attributes of the ListTemplate tag of the DocumentLibrary.xml
file

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Name
This
is the important key. This name and the name of the folder where the schema.xml
file of the custom library is located MUST be the SAME !
I use
customdoclib1

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Type
As
written before the new type will be 10001. The type can for example be used in a
feature that will place a custom button in a document library ribbon so as when
you activate the feature for the new button, only the document libraries with
the 10001 type will have the new button. Changing the type is one of the good
reasons to choose to create a custom document library rather to create a list
instance. But it can also cause many problems later for example when migrating
to a new version of SharePoint so be careful.
The base type will not be
changed, BaseType 1 means the list is a document library…

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">DisplayName
This
name will appear in your SharePoint site in the create page when you want to
create a custom document library within your site.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Description
The
description will appear in your SharePoint site below the display name in
the create page when you want to create a custom document library within your
site.

size=2>

size=2>xml
size=2>version size=2>=“ color=#0000ff size=2>1.0“ size=2> size=2>encoding size=2>=“ color=#0000ff size=2>utf-8 size=2>“ size=2>?>
< size=2>Elements size=2> size=2>xmlns size=2>=“ color=#0000ff size=2>http://schemas.microsoft.com/sharepoint/ size=2>“ size=2>>
      < color=#a31515 size=2> size=2>ListTemplate
color=#ff0000 size=2>
Name size=2>=“ color=#0000ff size=2>customdoclib1“
color=#ff0000 size=2> size=2>
Type size=2>=“ color=#0000ff size=2>10001“
color=#ff0000 size=2> size=2>
BaseType size=2>=“ color=#0000ff size=2>1“
size=2> size=2>
OnQuickLaunch size=2>=“ color=#0000ff size=2>TRUE“
color=#ff0000 size=2> size=2>
SecurityBits size=2>=“ color=#0000ff size=2>11“
color=#ff0000 size=2> size=2>
Sequence size=2>=“ color=#0000ff size=2>110“
color=#ff0000 size=2> size=2>
DisplayName size=2>=“ color=#0000ff size=2>My Company Document Library size=2>“
size=2>
Description size=2>=“ color=#0000ff size=2>Create a document library with xyz
functionalities“
size=2> size=2>
Image size=2>=“ color=#0000ff size=2>/_layouts/images/itdl.png size=2>“
size=2>
DocumentTemplate size=2>=“ color=#0000ff size=2>121“ size=2>/>
color=#a31515 size=2>Elements color=#0000ff size=2>>

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">4
- Renaming the DocLib folder located in the DocumentLibrary folder

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">As
written before, the important key is now to rename the folder where the document
library schema.xml file is located so as it has the same name than the name
attribute of the custom document library template.

href="http://1.bp.blogspot.com/-kwfnBHOfghk/TqMBL6WQiCI/AAAAAAAAB3E/N3PyI4CfTF4/s1600/Creating%2Ba%2Bcustom%2Bdocument%2Blibrary%2Bfor%2Bsharepoint%2B2010%2B-%2B020%2B-%2Brenaming%2BDoclib%2Bfolder.jpg"> style="WIDTH: 320px; HEIGHT: 199px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666374060315019298 border=0 alt=""
src="http://1.bp.blogspot.com/-kwfnBHOfghk/TqMBL6WQiCI/AAAAAAAAB3E/N3PyI4CfTF4/s320/Creating%2Ba%2Bcustom%2Bdocument%2Blibrary%2Bfor%2Bsharepoint%2B2010%2B-%2B020%2B-%2Brenaming%2BDoclib%2Bfolder.jpg">

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">5
- Installing the feature

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Now,
all we have to do is install the feature so open a command prompt and be sure to
have the administrator permissions on the machine. If the stsadm.exe
path is referenced in the system variables of the machine you just have to
type the following:

stsadm -o installfeature -name MyCompany.MyCustomDocumentLibrary

href="http://1.bp.blogspot.com/-FonBawsLb6A/TqMBLYJqtcI/AAAAAAAAB24/xgXKqsPUfR4/s1600/Creating%2Ba%2Bcustom%2Bdocument%2Blibrary%2Bfor%2Bsharepoint%2B2010%2B-%2B030%2B-%2Binstalling%2Bthe%2Bfeature.jpg"> style="WIDTH: 320px; HEIGHT: 160px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666374051135403458 border=0 alt=""
src="http://1.bp.blogspot.com/-FonBawsLb6A/TqMBLYJqtcI/AAAAAAAAB24/xgXKqsPUfR4/s320/Creating%2Ba%2Bcustom%2Bdocument%2Blibrary%2Bfor%2Bsharepoint%2B2010%2B-%2B030%2B-%2Binstalling%2Bthe%2Bfeature.jpg">

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">6
- Activating the feature for a specific site

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">So
now, open a site and you should see your feature in the “Manage Site Features”
page as shown in the next screen shot.

href="http://4.bp.blogspot.com/-X6OmAd1HUlE/TqMBLGvybRI/AAAAAAAAB2o/_f0sC5qdvpg/s1600/Creating%2Ba%2Bcustom%2Bdocument%2Blibrary%2Bfor%2Bsharepoint%2B2010%2B-%2B040%2B-%2Bfeature%2Binstalled.jpg"> style="WIDTH: 320px; HEIGHT: 152px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666374046463454482 border=0 alt=""
src="http://4.bp.blogspot.com/-X6OmAd1HUlE/TqMBLGvybRI/AAAAAAAAB2o/_f0sC5qdvpg/s320/Creating%2Ba%2Bcustom%2Bdocument%2Blibrary%2Bfor%2Bsharepoint%2B2010%2B-%2B040%2B-%2Bfeature%2Binstalled.jpg">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Notice
that the description filled in the feature.xml file is displayed on the
page.
Click the Activate button to enable the custom library creation within
this site.

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">7
-Testing

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Now
if you navigate to the SharePoint 2010 Create pop up using the “Site Actions”
menu and clicking “More Options…” then selecting Library in the pop up you
will notice that the references to the custom library are actually displayed by
the pop up.

href="http://2.bp.blogspot.com/-2uMYfyN_hAs/TqMBLIkQmxI/AAAAAAAAB2g/tTaWqz0b9ws/s1600/Creating%2Ba%2Bcustom%2Bdocument%2Blibrary%2Bfor%2Bsharepoint%2B2010%2B-%2B050%2B-%2Bcreating%2Bthe%2Bcustom%2Blibrary%2Bwithin%2Ba%2BSharePoint%2B2010%2Bsite.jpg"> style="WIDTH: 320px; HEIGHT: 152px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666374046951971602 border=0 alt=""
src="http://2.bp.blogspot.com/-2uMYfyN_hAs/TqMBLIkQmxI/AAAAAAAAB2g/tTaWqz0b9ws/s320/Creating%2Ba%2Bcustom%2Bdocument%2Blibrary%2Bfor%2Bsharepoint%2B2010%2B-%2B050%2B-%2Bcreating%2Bthe%2Bcustom%2Blibrary%2Bwithin%2Ba%2BSharePoint%2B2010%2Bsite.jpg">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Notice
that the name and description typed previously in the documentlibrary.xml file
are properly displayed.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">So
type a name for your new custom document library for SharePoint
2010 and check it is correctly provisioned within your site.

href="http://4.bp.blogspot.com/-oVC593mqXc0/TqMDxTAFHyI/AAAAAAAAB3c/galkDeP4FJc/s1600/Creating%2Ba%2Bcustom%2Bdocument%2Blibrary%2Bfor%2Bsharepoint%2B2010%2B-%2B060%2B-%2Bcustom%2Bdocument%2Blibrary%2Bwithin%2Ba%2BSharePoint%2B2010%2Bsite%2Bcreated.jpg"> style="WIDTH: 320px; HEIGHT: 218px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666376901611298594 border=0 alt=""
src="http://4.bp.blogspot.com/-oVC593mqXc0/TqMDxTAFHyI/AAAAAAAAB3c/galkDeP4FJc/s320/Creating%2Ba%2Bcustom%2Bdocument%2Blibrary%2Bfor%2Bsharepoint%2B2010%2B-%2B060%2B-%2Bcustom%2Bdocument%2Blibrary%2Bwithin%2Ba%2BSharePoint%2B2010%2Bsite%2Bcreated.jpg">

Check it out:MOSS How to …

Populate an ASP .Net Treeview from a SQL self-join table I had last week an ASP .net TreeView control to fill from a self-join table. I looked on the Internet ...
Using XPath to manage data returned by a SharePoint Web Service Topic: Using XPath to navigate through elements and attributes in an XML document returned by a SharePoint Web Service. This article proposes ...
Use Linq inside a Script Block of an Application Page – SharePoint minimal configuration for Linq When developing for SharePoint you maybe use Linq. Assume you are developing a new piece of code and to improve ...
Adding a custom control to the SharePoint 2010 Team Site Wiki Page Template ( wkpstd.aspx ) programmatically Topic This is maybe my last post about the Team Site Wiki Page customization with the aim of exceeding its limitations. This time ...
Adding Breadcrumb Navigation for SharePoint Application Pages Programmatically When creating a new Application Page (an .aspx page deployed to the c:\program files\common files\microsoft shared\web server extensions\template\layouts directory) you can ...

I have a new copy of SharePoint Designer 2007 and am looking for a cheap server to experiment on. Any ideas?

LickMyBifkin — Wed, 16 Mar 2011 21:00:35 +0000

I have access to a server at work but want a commercial internet server that I can use to experiment with my own personal page without anyone worrying if it doesn’t work correctly.

Best answer:

Answer by titus1971
You might want to think about some type of virtual server. We use VM ware at my company and I think Microsoft has a version as well. Yuu can even create a virtual domain to test it on.

What do you think? Answer below!

How can I get VMware to run as a service on Windows 2003? I've checked every google search and tried them all...the only thing that I want to be able to do is ...
Difference between Virtual Dedicated Server and Dedicated Server. With recommendations of each? I am interested in purchasing a powerful server to use at my home for a variety of things. As I ...
what is the difference between virtual and dedicated servers? i have started my new business of domain name registration and hosting as a reseller. i went to google.com and ...
Wilcard DNS (similar to hosts file) in Windows without a local dedicated DNS server…? I have a local test server running Apache2 with virtual hosting setup correctly. I'd like to set up a system ...
How to Create Virtual servers ? i bought a new Dell 1950 1U Server and want to create virtual servers , but have no idea how ...

SharePoint 2007 – associated lookup columns

Gravy B — Tue, 30 Nov 2010 20:02:53 +0000

No, this is not a mistake – we can also have associated lookup columns in SharePoint 2007, though not with the extended UI creation capabilities available in SharePoint 2010. Let’s first have a look at this new functionality in SharePoint 2010 (and define more accurately the terminology – I don’t think that there is a specific term for this lookup field extension, but in this article I will call it as I did in the title of the posting):

So, as you can see from the screenshot (and probably tried that many times already yourself), when you create a new lookup column in a list, you have the option to select more than one column from the target lookup list (in SharePoint 2007 we had the option to select just one “show column”). Basically what SharePoint does when you create a lookup field from the UI is to create the “normal” lookup column as before and then create another read-only “associated” lookup column for every additional show field from the check-box list that you have selected. And this functions as follows – when you create a new item, or edit an existing one in the edit form you see only the “normal” lookup column there, but when you change it to point to another item in the lookup list, all “associated” lookup columns change their values so that they correspond to the related columns in the newly selected lookup item. The associated lookup columns are read-only but you can add them to the views of the list, so that you display all additional columns that you need from the lookup item. And since the main lookup and the auxiliary lookup fields are automatically synchronized (SharePoint does that for us), you don’t need any additional code in item event receivers for instance.

Let’s now have a look at the field schema of the “normal” and “associated” lookup columns:

<Field Type="Lookup" DisplayName="Department" Required="FALSE" EnforceUniqueValues="FALSE" List="{ceaf935e-b9c6-48a0-8c23-bcec58a24c91}" ShowField="Title" UnlimitedLengthInDocumentLibrary="FALSE" RelationshipDeleteBehavior="None" ID="{98948dfd-cea5-4d6c-ac47-25bafa5218de}" SourceID="{bca1cd44-3822-49b6-b68c-2ff28ced1726}" StaticName="Department" Name="Department" ColName="int1" RowOrdinal="0" Group="" />

This is the schema of the “normal” or main lookup column – as you see, there is nothing specific in its schema – it is just a regular lookup column. And this is the schema of one of the associated lookup columns that I created for the lookup column above:

<Field Type="Lookup" DisplayName="Department:Code" List="{ceaf935e-b9c6-48a0-8c23-bcec58a24c91}" WebId="4ee36ddf-5b1b-470b-9f9a-fbd970edf5aa" ShowField="Code" FieldRef="98948dfd-cea5-4d6c-ac47-25bafa5218de" ReadOnly="TRUE" UnlimitedLengthInDocumentLibrary="FALSE" ID="{cd2b77b9-6238-4e2e-99ee-826826dc09f2}" SourceID="{bca1cd44-3822-49b6-b68c-2ff28ced1726}" StaticName="Department_x003a_Code" Name="Department_x003a_Code" Version="1" />

So, as you see we have all attributes for a normal lookup column, but one extra attribute as well – “FieldRef”. The value of this attribute is a Guid and this is exactly the ID attribute of the main lookup column. So, obviously the “FieldRef” attribute is the one that defines this association between the main and the associated lookup columns. Notice also the “ReadOnly” attribite in the associated lookup field’s schema which is set to TRUE – this guarantees that the associated lookup column doesn’t appear in the new and edit forms of the SharePoint list (you don’t need it there anyway, since it is synchronized automatically).

This is indeed a very useful new functionality in SharePoint 2010, but you may already ask yourself what SharePoint 2007 has to do in the whole matter – we don’t have this functionality there. Well, it is true that SharePoint 2007 lacks the user interface for creating “associated” lookup columns but this doesn’t mean that we cannot create columns with code specifying the values for all attributes in their schema as we decide. And it turns out that when we create a lookup column in a list and set its “FieldRef” attribute to “point” to another lookup column in the same list (both columns should target one and the same lookup list) – the “associated” lookup functionality actually works – just like in SharePoint 2010 (note here – I tested this on SharePoint 2007 service pack 2). Another detail here is that you shouldn’t forget to set the “ReadOnly” attribute of the field to TRUE – otherwise the “associated” lookup column will appear in the edit form of the list and when you try to save the list item, the page will crush with a nasty error.

As to the question of how you can create a lookup column (an associated lookup column) with code (and set its FieldRef attribute) – probably the easiest way is to use the SPFieldCollection.AddFieldAsXml method, which accepts a string parameter containing the schema XML of the new field. Note that you will have to properly format the schema XML of the associated lookup field providing the correct values to its attributes (the final XML schema should look similar to the one above):

in the ID attribute – a unique Guid value
in the Name and StaticName attributes – unique (within the SharePoint list) internal name of the field
in the List attribute – the ID of the lookup list
in the WebId attribute – the ID of the web containing the lookup list (in most cases this is the web of the current list)
in the FieldRef attribute – the ID of the main lookup field to which we want to associate the new lookup column
in the ShowField attribute – the internal name of the column in the lookup list whose value should be displayed in the new lookup column
in the ReadOnly attribute – this should be set to TRUE

And the net result will look something similar to this:

In the sample screenshot, the “Department” column is the main lookup column (displaying the “Title” column from the lookup list) and the “Department country” column is the associated lookup column (displaying the custom “Country” text column from the lookup list). Note also that the value displayed in the list view in the column of the associated lookup field is not rendered as a link, unlike the value in the column of the main lookup – actually this is exactly the same behavior as we have in SharePoint 2010. And most importantly again the same as in SharePoint 2010, the values of the associated lookup column or columns get automatically synchronized with the changes of the selected lookup item in the main lookup field.

Check it out:Stefan Stanev’s SharePoint blog

SharePoint 2010 – content type feature upgrading This is something that I had overlooked in my lengthy posting on SharePoint content types from a couple of months ...
Two small SPListItem extension methods So, it is about two small extension methods which do basically the same job – getting a specific field value ...
Error 191: Some part of your SQL statement is nested too deeply. When inserting string into SQL Server table using the INSERT predicate that uses string concatenation there seems to be an ...
How to display all versions in a SharePoint list view page – part 2 Several months ago I wrote a small posting describing how you can trick the standard list view web part to ...
Tracking with dcsMultiTrack invalid fields on client side dcsMultiTrack - is 3rd compoment. Instead of dcsMultiTrack you can use your own tracking tool or for ...

The SharePoint item being crawled returned an error when attempting to download the item.

program_1357 — Tue, 30 Nov 2010 15:03:30 +0000

SharePoint Search error – “The SharePoint item being crawled returned an error when attempting to download the item.”

If you are running a crawl and noticed that you are getting the above error on certain site or site collection.. you can correct it by one or combination of the following solutions

Avoid placing core results webpart on homepage.
Make sure that all custom webpages are checked in.
If you have any page other than the default.aspx as the hompage at the root site of the site collection, then set the default.aspx as homepage and run crawl. Once it is successful, you can go ahead and set the other page as your homepage.
Try installing Aug CUs.

Check it out:SharePoint 2010

Programatically redirect to custom error page programatically redirect to custom error page To set a custom error page const string CustomErrorPage = "/_layouts/CustomPageMappings/Error.aspx"; webApp.UpdateMappedPage(SPWebApplication.SPCustomPage.Error, CustomErrorPage); ref: http://todd-carter.com/post/2010/04/07/An-Expected-Error-Has-Occurred.aspx To call the error ...
Capacity Planning for SharePoint 2010 Only references 1. What’s New in SharePoint 2010 Capacity Planning ( Joel Oleson ) Check it out:SharePoint 2010
Branding your Sharepoint 2010 Site Ref: SharePoint 2010 Themes and Resources for Upgrading a Custom Master Page SharePoint 2010 CSS references in Master Pages http://technet.microsoft.com/hi-in/library/cc263203(en-us,office.14).aspx http://styledpoint.com/blog/ribbon-customization-changing-placement-look-and-behavior/ http://blog.drisgill.com/ http://www.nonlinearcreations.com/whitepaper/index.asp?id=17 http://sharepoint.microsoft.com/blogs/GetThePoint/Lists/Categories/Category.aspx?CategoryId=16&Name=Branding Working with the ...
Hide Columns in SharePoint New, Edit and Disp Forms Hide Columns in SharePoint New, Edit and Disp Forms There are several ways you can achieve this.. choose the best ...
Sharepoint 2010 – WebPart deployment structure This post is to put together the various files that is generated in Visual Studio 2010 like the manifest.xml, feature.xml, ...

Real World SharePoint 2010 Released!

BillGatesJr wizkid — Tue, 16 Nov 2010 11:03:06 +0000

Today I got the great news that the Real World SharePoint 2010 book has finally been released! This is my first ever publication and I’m truly excited to see it finally available. To have my first publication be this particular book where so many stellar folks have contributed is just an incredible honor for me. I was one of the few contributors that had a very early delivery date for their chapters and as such I finished my chapter in December of 2009 so I’ve been waiting a long time (almost a full year) for this sucker to finally get out. Now I just have to get my second publication finished

Thanks again to everyone who contributed or otherwise helped organize and make this book happen and a special thanks to all those who choose to purchase it

Check it out:SharePoint Automation

MSDN Visual Studio Ultimate Contest Winners I’m a little late in getting this post out due to getting a bit slammed last week with work, book ...
November 2010 SharePoint Connections Decks and Code The past few weeks have been very busy for me as I’ve just finished presenting at two different conferences, and ...
SPTechCon Decks I just wrapped up a couple of quick days at SPTechCon in Boston and had a great time! I don’t ...
Big Changes Astute readers of my blog may have noticed that my blog header and byline have changed just a bit in ...
ListItemEditor for SharePoint 2010 The ListItemEditor tool is now available for SharePoint 2010 beta. I upgraded the tool’s solution with Visual Studio 2010 beta ...

Hide Columns in SharePoint New, Edit and Disp Forms

freeyrmind — Wed, 10 Nov 2010 20:02:53 +0000

Hide Columns in SharePoint New, Edit and Disp Forms

There are several ways you can achieve this.. choose the best that fits your need…

1. PowerShell
2. SharePoint Designer
3. ContentTypes
4. Programmatically
5. jQuery

Ref:
http://blog.qumsieh.ca/2010/02/16/hide-columns-in-sharepoint-new-edit-and-disp-forms/

Check it out:SharePoint 2010

Capacity Planning for SharePoint 2010 Only references 1. What’s New in SharePoint 2010 Capacity Planning ( Joel Oleson ) Check it out:SharePoint 2010
Get all columns used to display search results Check it out:SharePoint 2010
CSS Tips SharePoint 2010 CSS Tips Compiled from various SharePoint experts like Randy Drisgill, Heather Solomon, etc. Add this style statement to your ...
ListItemEditor for SharePoint 2010 The ListItemEditor tool is now available for SharePoint 2010 beta. I upgraded the tool’s solution with Visual Studio 2010 beta ...
Sharepoint 2010 – WebPart deployment structure This post is to put together the various files that is generated in Visual Studio 2010 like the manifest.xml, feature.xml, ...

November 2010 SharePoint Connections Decks and Code

m0sRucC — Tue, 09 Nov 2010 04:03:15 +0000

The past few weeks have been very busy for me as I’ve just finished presenting at two different conferences, and as I don’t typically present at conferences this was kind of a big deal for me. You can get my slides for SPTechCon, the conference I spoke at in late October from my earlier post, and if you’re looking for the slides and code from SharePoint Connections, which I just returned from you can find them below. I know I promised several folks that I’d have these available Friday but I decided to take some long overdue family time instead.

November 2010 SharePoint Connections Slide Decks:

November 2010 SharePoint Connections Demo Code:

Now that I’m done with conferences for the year I guess it’s time to get back to writing my book

-Gary

Check it out:SharePoint Automation

SPTechCon Decks I just wrapped up a couple of quick days at SPTechCon in Boston and had a great time! I don’t ...
ListItemEditor for SharePoint 2010 The ListItemEditor tool is now available for SharePoint 2010 beta. I upgraded the tool’s solution with Visual Studio 2010 beta ...
Real World SharePoint 2010 Released! Today I got the great news that the Real World SharePoint 2010 book has finally been released! This ...
MSDN Visual Studio Ultimate Contest Winners I’m a little late in getting this post out due to getting a bit slammed last week with work, book ...
SharePoint 2010 version of the WebPart Manager tool I created a SharePoint 2010 version of the WinForm WebPart Manager tool that I demonstrated in my previous posting. Sources ...

Service Accounts and Managed Service Accounts in SharePoint 2010

Albie — Tue, 05 Oct 2010 19:03:33 +0000

With SharePoint 2010 we now have the ability to allow SharePoint to manage various service accounts thus foregoing the need to have IT administrators manually manage password changes. This new feature is a great benefit to SharePoint administrators and security conscious admins in general as it allows us to easily enforce our corporate security policies by changing these passwords on a schedule, and the administrators don’t even know what the password is so the likelihood of a compromise due to a disgruntled admin, though not eliminated, is somewhat reduced.

But the introduction of this new feature isn’t all good. The complication comes from the fact that SharePoint 2010 doesn’t implement this capability consistently. So an account that is configured as a Managed Service Account and set to have its password changed automatically could also be used in certain places that don’t understand the managed account concept. When the managed account password is changed the feature that uses that account and only knows the username and password (so it does not use the managed account details) will effectively be broken. As an example, if you configure the Enterprise Search Service to use a managed account whose password is scheduled to be changed every 30 days and you use that same account for the content crawl account then when that password is changed the content crawl will cease to function as it will be unable to authenticate the account. It’s important to note, however, that this issue only comes to light when you configure the managed account to have it’s password changed automatically.

So what things can be managed accounts and what cannot? The following lists what I’ve come across so far (if I’ve missed anything please leave a comment so I can update these lists):

Managed Service Accounts:

All Service Application Pool Accounts
- Access Service Application
- BCS Service Application
- Excel Services Service Application
- Metadata Service Application
- PerformancePoint Service Application
- Enterprise Search Service Application
- Secure Store Service Application
- Subscription Settings Service Application
- User Profile Service Application
- Visio Services Service Application
- Web Analytics Service Application
- Word Automation Service Application
- Word Viewing Service Application
- PowerPoint Viewing Service Application
- Security Token Service Application
All Content Web Application Pools
Service Instances
- Claims to Windows Token Service
- Document Conversion Launcher Service
- Document Conversion Load Balancer Service
- Microsoft SharePoint Foundation Sandboxed Code Service
- SharePoint Foundation Help Search
- SharePoint Server Search (Enterprise Search)
- Web Analytics Data Processing Service

Service Accounts (should not be managed):

Search Crawl Accounts
- For Foundation Search and Server (Enterprise) Search
Unattended User Accounts
- Excel Services Service Application
- Visio Services Service Application
- PerformancePoint Service Application
- (in general, any Secure Store application credentials)
Object Cache Portal Accounts
- Super User Account
- Super Reader Account
User Profile
- Synchronization Service Account (listed incorrectly on the FarmCredentialManagement.aspx page)
- Synchronization Connection Account
Server Search Custom Crawl Rule Accounts
- Any crawl rule that specifies an account other than the default crawl account

Again, these are just the accounts that I’ve personally bumped up against so it may not be a complete listing.

Viewing and Creating Managed Accounts

To see the current list of Managed Service Accounts using Central Admin go to Security –> Configure managed accounts:

You can edit the settings for any managed account by simply clicking the edit icon associated with the account you wish to modify. Once on the Manage Account screen you can configure the automatic password change settings:

To perform the same tasks using Windows PowerShell we can use the Get-SPManagedAccount cmdlet to retrieve the list of managed accounts:

Or we can retrieve a specific account using the -Identity parameter or by passing in a Web Application or Service:

clTo change the settings for a Managed Account we can use the Set-SPManagedAccount cmdlet:

To create a new Managed Account we use the New-SPManagedAccount cmdlet. In the example below I’m manually creating a PSCredential object so that I can specify my password (pa$$w0rd) in script (very useful for building out dev or test environments – otherwise you should use Get-Credential to prompt for the password so that it is not hard coded anywhere):

Applying Managed Accounts

Once you have your Managed Accounts created you can begin to use them for things such as Service Instances and Service and Content Application Pools. To associate a managed account with a specific Service Instance using Central Admin you can go to Security –> Configure service accounts. On the Service Accounts page you can set the account used for the Farm Account, Service Instances, Web Content Application Pools, and Service Application Pools. The Service Instances are highlighted in the following image:

Service Instances

To set the account associated with a particular Service Instance using Windows PowerShell we simply get the ProcessIdentity property of the Service Instance and set its Username property. Once set we call Update() to update the Configuration Database and then Deploy() to push the change out to all Service Instances. To make this easier I put this code in a function that I can call by passing in the Service Instance and credentials to use:

function Set-ServiceIdentity($svc, $username)
{
   $pi = $svc.Service.ProcessIdentity
   if ($pi.Username-ne $username) {
       $pi.Username= $username
       $pi.Update()
       $pi.Deploy()
    }
}

Here’s an example of how you can call this function:

Service Application Pools

To create a new Service Application pool we use the New-SPServiceApplicationPool cmdlet and pass in the name of the Application Pool to create and the Managed Account to assign as the Application Pool identity:

It’s extremely important to note that the application pool that you create using the New-ServiceApplicationPool cmdlet cannot be used for your content Web Applications. Unfortunately there is no out-of-the-box equivalent for creating Application Pools for Web Applications.

Web Application Pools

As previously noted there is no cmdlet for creating Application Pools for Web Applications. Instead what you need to do is first check if the Application Pool you need already exists by using the SPWebService’s ContentService static property. If it exists then pass in just the name of the Application Pool to the New-SPWebApplication cmdlet, otherwise pass in the name and the Managed Account to use as the Application Pool’s identity:

Applying Service Accounts

When it comes to applying non-managed accounts to the various features things get a little more complicated. Let’s start with the Crawl Accounts.

SharePoint Foundation Search Service

For SharePoint Foundation Search we can set the crawl account (or content access account) using Central Admin by navigating to the Services on Server page and clicking the SharePoint Foundation [Help] Search link which takes you to the settings page where we can set the crawl account:

To set the same information using Windows PowerShell we actually have to go old-school and use STSADM as there’s no PowerShell equivalent cmdlet. Here’s a snippet of PowerShell code that I use to accomplish this:

function ConvertTo-UnsecureString([System.Security.SecureString]$string)
{
    $unmanagedString = [System.Runtime.InteropServices.Marshal]::SecureStringToGlobalAllocUnicode($string)
    $unsecureString = [System.Runtime.InteropServices.Marshal]::PtrToStringUni($unmanagedString)
    [System.Runtime.InteropServices.Marshal]::ZeroFreeGlobalAllocUnicode($unmanagedString)

    return $unsecureString
}

$searchSvcAccount = Get-Credential "localdev\spsearchsvc"
$crawlAccount = Get-Credential "localdev\spcrawl"

$stsadmArgs = "-o spsearch -action start " + `
    "-farmserviceaccount `"$($searchSvcAccount.Username)`" " + `
    "-farmservicepassword `"$(ConvertTo-UnsecureString $searchSvcAccount.Password)`" " + `
    "-farmcontentaccessaccount `"$($crawlAccount.Username)`" " + `
    "-farmcontentaccesspassword `"$(ConvertTo-UnsecureString $crawlAccount.Password)`" " + `
    "-databaseserver `"spsql1`" " +  `
    "-databasename `"SharePoint_FoundationSearch`""

Write-Host "Running: stsadm $stsadmArgs"
$stsadmoutput = cmd /c "stsadm $stsadmArgs" 2>&1
if ($lastexitcode -ne 0) {
    throw "Unable to start Foundation Search Service.`n$stsadmoutput"
}

Note that I’m using a helper function to convert the secure password to a static string which I can then pass to the STSADM spsearch command.

SharePoint Server Search Service

To manage the crawl account for the SharePoint Server Search Service (also known as the Enterprise Search Service) using Central Admin we simply need to navigate to the Search Administration page of the Service Application that we wish to modify and click the link for the Default content access account. This will bring up the following screen:

Note that by default this account will be set to be the same account you used for the Search Service Instance which is a Managed Account. If you do not change this account and you have configured SharePoint to manage the account password then your crawls will fail when the password changes. To make this change using Windows PowerShell we use the Set-SPEnterpriseSearchServiceApplication cmdlet:

$crawlAccount = Get-Credential “localdev\spcrawl“

$searchApp | Set-SPEnterpriseSearchServiceApplication -DefaultContentAccessAccountPassword $crawlAccount.Password -DefaultContentAccessAccountName $crawlAccount.Username

Remember not to do this step until after you have provisioned the Administration Component.

Object Cache Accounts

Many administrators when they first configure SharePoint 2010 and hit a Web Application for the first time are likely to see a recurring event in the event log stating that the object cache has not been configured correctly. The specific error is as follows:

Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources.

This is essentially telling you that you have missed a manual configuration step in which you need to run some PowerShell to set two accounts for SharePoint to use to access the object cache:

function Set-WebAppUserPolicy($webApp, $userName, $userDisplayName, $perm) {
    [Microsoft.SharePoint.Administration.SPPolicyCollection]$policies = $webApp.Policies
    [Microsoft.SharePoint.Administration.SPPolicy]$policy = $policies.Add($userName, $userDisplayName)
    [Microsoft.SharePoint.Administration.SPPolicyRole]$policyRole = $webApp.PolicyRoles | where {$_.Name -eq $perm}
    if ($policyRole -ne $null) {
        $policy.PolicyRoleBindings.Add($policyRole)
    }
    $webApp.Update()
}
$webApp = Get-SPWebApplication "http://content"
$portalSuperUserAccount = Get-Credential "localdev\SPSuperUser"
$webApp.Properties["portalsuperuseraccount"] = $portalSuperUserAccount.UserName
Set-WebAppUserPolicy $webApp $portalSuperUserAccount.UserName $portalSuperUserAccount.UserName "Full Control"

$portalSuperReaderAccount = Get-Credential "localdev\SPSuperReader"
$webApp.Properties["portalsuperreaderaccount"] = $portalSuperReaderAccount.UserName
Set-WebAppUserPolicy $webApp $portalSuperReaderAccount.UserName $portalSuperReaderAccount.UserName "Full Read"

Make sure that you do not use the same account for both the super user and super reader. (And of course make sure you change the URL and account names to match your environment). For more information about these settings see the following TechNet article: http://technet.microsoft.com/en-us/library/ff758656.aspx

Unattended Accounts

There are some services, specifically the Visio Services Service Application, the Excel Services Service Application, and the PerformancePoint Service Application, that allow us to set an account that we can use for access data sources behind the scenes. These are called unattended access accounts. To set these accounts we must create a new target application in the Secure Store Service Application and associate the target application’s ID with the appropriate Service Application. The following PowerShell code demonstrates how to do this for the Visio Services Service Application (the Excel Services Service Application is virtually identical and just uses cmdlets specific to Excel rather than Visio; PerformancePoint is a lot simpler):

#Get the Visio Service App
$svcApp = Get-SPServiceApplication | where {$_.TypeName -like "*Visio*"}
#Get the existing unattended account app ID
$unattendedServiceAccountApplicationID = ($svcApp | Get-SPVisioExternalData).UnattendedServiceAccountApplicationID
#If the account isn't already set then set it
if ([string]::IsNullOrEmpty($unattendedServiceAccountApplicationID)) {
    #Get our credentials
    $unattendedAccount = Get-Credential "localdev\SPUnattended"

    #Set the Target App Name and create the Target App
    $name = "$($svcApp.ID)-VisioUnattendedAccount"
    Write-Host "Creating Secure Store Target Application $name..."
    $secureStoreTargetApp = New-SPSecureStoreTargetApplication -Name $name `
        -FriendlyName "Visio Services Unattended Account Target App" `
        -ApplicationType Group `
        -TimeoutInMinutes 3

    #Set the group claim and admin principals
    $groupClaim = New-SPClaimsPrincipal -Identity $svcApp.ApplicationPool.ProcessAccount.Name -IdentityType WindowsSamAccountName
    $adminPrincipal = New-SPClaimsPrincipal -Identity "$($env:userdomain)$($env:username)" -IdentityType WindowsSamAccountName

    #Set the account fields
    $usernameField = New-SPSecureStoreApplicationField -Name "User Name" -Type WindowsUserName -Masked:$false
    $passwordField = New-SPSecureStoreApplicationField -Name "Password" -Type WindowsPassword -Masked:$false
    $fields = $usernameField, $passwordField

    #Set the field values
    $secureUserName = ConvertTo-SecureString $unattendedAccount.UserName -AsPlainText -Force
    $securePassword = $unattendedAccount.Password
    $credentialValues = $secureUserName, $securePassword

    #Get the service context
    $subId = [Microsoft.SharePoint.SPSiteSubscriptionIdentifier]::Default
    $context = [Microsoft.SharePoint.SPServiceContext]::GetContext($svcApp.ServiceApplicationProxyGroup, $subId)

    #Check to see if the Secure Store App already exists
    $secureStoreApp = Get-SPSecureStoreApplication -ServiceContext $context -Name $name -ErrorAction SilentlyContinue
    if ($secureStoreApp -eq $null) {
        #Doesn't exist so create.
        Write-Host "Creating Secure Store Application..."
        $secureStoreApp = New-SPSecureStoreApplication -ServiceContext $context `
            -TargetApplication $secureStoreTargetApp `
            -Administrator $adminPrincipal `
            -CredentialsOwnerGroup $groupClaim `
            -Fields $fields
    }
    #Update the field values
    Write-Host "Updating Secure Store Group Credential Mapping..."
    Update-SPSecureStoreGroupCredentialMapping -Identity $secureStoreApp -Values $credentialValues 

    #Set the unattended service account application ID
    $svcApp | Set-SPVisioExternalData -UnattendedServiceAccountApplicationID $name
}

When it comes to PerformancePoint we have a lot less work we need to do as the product team was nice enough to make it so that the Set-SPPerformancePointSecureDataValues does all the work of setting up the target application for us (note though that they did screw up how the Service Application is passed into the cmdlet requiring you to pass in the ID of the Service Application rather than the actual Service Application object):

$unattendedAccount = Get-Credential "localdev\SPUnattended"
$secureValues = Get-SPPerformancePointSecureDataValues -ServiceApplication $svcApp.Id
if ($secureValues.DataSourceUnattendedServiceAccount -ne $unattendedServiceAccount.UserName) {
    Write-Host "Setting unattended service account $($unattendedServiceAccount.UserName)..."
    $svcApp.Id | Set-SPPerformancePointSecureDataValues -DataSourceUnattendedServiceAccount $unattendedServiceAccount
}

User Profile Synchronization Service Identity

One thing to watch out for is when setting the account for the User Profile Synchronization Service. This service wants you to use the Farm Account as the identity. This means that your Farm Admin account cannot have it’s password managed by SharePoint if you intend to use this service (or at least, it shouldn’t be unless you don’t mind manually fixing this service every time your password changes – good luck with that BTW). Your Farm Admin account will always be a Managed Account (you can’t change that) so be extra careful when changing this accounts password (either manually or automatically). To set this account using Central Admin you can click Start next to the User Profile Synchronization Service entry on the Services on Server page.

To accomplish the same thing using PowerShell we need to get an instance of the Synchronization Service and set a few properties and call the SetSynchronizationMachine method passing in the username and password of the Farm Admin account (note that it requires the password be passed in as a standard string and not a secure string so I use my previously defined ConvertTo-UnsecureString function):

$syncMachine = Get-SPServer "sp2010dev"
$profApp = Get-SPServiceApplication | where {$_.Name -eq "User Profile Service Application 1"}
$account = Get-Credential "localdev\spfarm"
if ($syncMachine.Address -eq $env:ComputerName) {
    $syncSvc = Get-SPServiceInstance -Server $env:ComputerName | where {$_.TypeName -eq "User Profile Synchronization Service"}
    $syncSvc.Status = [Microsoft.SharePoint.Administration.SPObjectStatus]::Provisioning
    $syncSvc.IsProvisioned = $false
    $syncSvc.UserProfileApplicationGuid = $profApp.Id
    $syncSvc.Update()
    $profApp.SetSynchronizationMachine($syncMachine.Address, $syncSvc.Id, $account.UserName, (ConvertTo-UnsecureString $account.Password))
}

if ($syncSvc.Status -eq "Disabled") {
    Write-Host "Starting User Profile Synchronization Service..."
    Start-SPServiceInstance $syncSvc
}
do {Start-Sleep 2} while ((Get-SPServiceInstance -Server $env:ComputerName | where {$_.TypeName -eq "User Profile Synchronization Service"}).Status -eq "Provisioning")

Summary

As you can see setting the accounts that are used throughout SharePoint 2010 is anything but consistent and in some cases a real pain in the a$$. I know I didn’t cover how to set every account (custom crawl rule accounts, user profile sync connection accounts, others?) but hopefully someone out there has already documented these, or if not perhaps they’d be nice enough to post a comment here for others benefit from (maybe one day I’ll add them myself but for now I think this post is quite long enough). As always, please let me know if I’ve missed something or otherwise got something wrong as I certainly don’t claim to have all the answers.

Happy PowerShelling

Check it out:SharePoint Automation

Getting an Inventory of All SharePoint Documents Using Windows PowerShell I got an email today asking if I had anything that would generate a report detailing all the documents throughout ...
Error 191: Some part of your SQL statement is nested too deeply. When inserting string into SQL Server table using the INSERT predicate that uses string concatenation there seems to be an ...
Convert .DAA files to .ISO in Linux with Poweriso Convert .DAA files to .ISO in Linux with Poweriso Posted in Labels: Ubuntu | Friday, July 23, ...
Deploying SharePoint 2010 Solution Packages Using PowerShell With SharePoint 2010 we can now deploy our Solution Packages using PowerShell. What’s cool about this is that it’s a ...
How to restrict the number of active sessions in Remote Desktop Services Manager Question After the Remote Desktop Session Host server (Terminal Server) runs for a while, there are many sessions marked as active ...

CP - Help, Answers, Tips, Questions about software, hardware and other stuff » SharePoint

Creating a Wiki Page template For SharePoint 2010 Foundation

Related Posts:

Configuring SharePoint 2010 Foundation for Internet-facing publishing

Related Posts:

Creating a custom document library for SharePoint 2010

Related Posts:

I have a new copy of SharePoint Designer 2007 and am looking for a cheap server to experiment on. Any ideas?

Related Posts:

SharePoint 2007 – associated lookup columns

Related Posts:

The SharePoint item being crawled returned an error when attempting to download the item.

SharePoint Search error – “The SharePoint item being crawled returned an error when attempting to download the item.”

Related Posts:

Real World SharePoint 2010 Released!

Related Posts:

Hide Columns in SharePoint New, Edit and Disp Forms

Hide Columns in SharePoint New, Edit and Disp Forms

Related Posts:

November 2010 SharePoint Connections Decks and Code

Related Posts:

Service Accounts and Managed Service Accounts in SharePoint 2010

Viewing and Creating Managed Accounts

Applying Managed Accounts

Service Instances

Service Application Pools

Web Application Pools

Applying Service Accounts

SharePoint Foundation Search Service

SharePoint Server Search Service

Object Cache Accounts

Unattended Accounts

User Profile Synchronization Service Identity

Summary

Related Posts: