SharePoint 2010

WSSdemo.com

30

Nov

Ha great, wssdemo.com is running the SP2010 public beta!

Head over there for more information on SP2010.

wssdemo.com

via @waldekm

Categorie: Demo, News, SharePoint 2010

Share:

Stef van Hooijdonk schreef

Comments (0) | Permalink

Great Content for SharePoint 2010 Developers on Channel9

24

Nov

Saw this over at the MSDN homepage, by Mathijs Hoekstra, there is a ton of content for SharePoint 2010 Developers on Channel9.

Categorie: Learning

Share:

Stef van Hooijdonk schreef

Comments (0) | Permalink

Windows 2008 R2 and SharePoint 2010

21

Nov

If you had problems installing SP2010 onto Win2k8R2, head over to Connect to download this hotfix.

It should fix the "allowInsecureTransport" error you were having.

via Jie Li's blog

Categorie: Installation

Share:

Stef van Hooijdonk schreef

Comments (0) | Permalink

SP2010 beta 2 does not install correctly on Windows 2008 R2 just yet

18

Nov

SP2010 beta 2, finally it is here!

But be advised, currently you should install this on Windows 2008 and NOT Windows 2008 R2!.

during the configuration of the services you will get an error relating to "allowInsecureTransport".

This is fixed by a HotFix for WCF. But the Windows 2008 R2 version is not yet available.

Categorie: SharePoint 2010

Share:

Stef van Hooijdonk schreef

Comments (0) | Permalink

Coding against a Document Set

16

Nov

I’ve just had a 5 day training on development for SharePoint 2010. We’ve seen some cool stuff, were able to do some Hands on Labs and talk to other SharePoint experts about the new stuff that is coming up.

One of the best things though about this training was the ability to try some stuff out for yourself. The fact that no project managers or customers were bothering me for a week allowed me to finally take the time to look around in the object model, the central admin and the new front end interfaces.

Over the next few week I’ll be publishing some post on the things I’ve tried out. I hope to publish a lot more posts about SP2010 once Beta 2 comes available.

DISCLAIMER: The examples are build on and tested against a Beta 1 build of SharePoint 2010 and a Beta 1 build of Visual Studio 2010, so there is no guarantee this will work on later versions.

One of the things I was eager to try out is the new Document Sets feature. Document Sets allow you to group related documents together and share metadata between those docs. When you view a document set in a library, you are presented with a welcome page that shows the metadata of the set and the contents.

The welcome page in itself is something you’re able to customize. So you can add web parts and other controls through the interface or SharePoint Designer to the welcome page.

First let me start by giving you some code you can use to show extra information about the document set in a web part you can place on the welcome page:

        1: try

       2: {

       3:     SPListItem item = SPContext.Current.ListItem;

       4:  

       5:     DocumentSet set = DocumentSet.GetDocumentSet(item.Folder);

       6:  

       7:     writer.WriteLine("ContentType: {0}<br/>", item.ContentType.Name);

       8:     writer.WriteLine("Title: {0}<br/>", item.Title);

       9:     writer.WriteLine("WelcomePageUrl: {0}<br/>", set.WelcomePageUrl);

      10:     writer.WriteLine("ItemCount: {0}<br/>", set.Folder.ItemCount);

      11:     writer.WriteLine("Welcomepage Fields:<br/>");

      12:     DocumentSetTemplate template = set.ContentTypeTemplate;

      13:     WelcomePageFieldCollection fields = template.WelcomePageFields;

      14:     foreach (SPField field in fields)

      15:     {

      16:         writer.WriteLine("{0}<br/>", field.Title);

      17:     }

      18: }

      19: catch (Exception)

      20: { }

First we get a reference to the current List Item through the SPContext. This list item is the main item for the document set that contains the metadata that is pushed into the child documents.

We then can get a reference to the DocumentSet by passing in the SPFolder of the item into a static method of the DocumentSet class. The DocumentSet class is stored in the Microsoft.Office.DocumentManagement.dll in the DocumentSets namespace.

The DocumentSetTemplate in turn contains more information about the fields that are shared or shown on the Welcome page.

In the next post I’ll show you how to provision a document set from a feature. Something that is quite easy to do with the new SharePoint project and item templates for Visual Studio 2010.

Categorie: Document sets, Object model

Share:

Peter Gerritsen schreef

Comments (0) | Permalink

Provisioning a Document Set

16

Nov

In this post I’ll show you how to create a project in Visual Studio 2010 with the new SharePoint project and item templates to provision a Document Set from a feature.

DISCLAIMER: The examples are build on and tested against a Beta 1 build of SharePoint 2010 and a Beta 1 build of Visual Studio 2010, so there is no guarantee this will work on later versions or even on the Beta 1 build you're running.

A Document Set is basically a content type just like all the others you can find in SharePoint, it derives from the Folder content type. So the steps you need to take to provision a Document Set content type are not that different as well.

We’ll start out by creating an empty SharePoint project in Visual Studio 2010 and work from there.

First we’ll add a Content Type item to the project. In the elements.xml file we place the following content:

        1: <?xml version="1.0" encoding="utf-8"?>

       2: <Elements xmlns="http://schemas.microsoft.com/sharepoint/">

       3:   <ContentType ID="0x0120D520002228EBDE71841343B23171CE351F7D39" Name="Test Doc Set" Group="Document Set Content Types" Version="2" ProgId="SharePoint.DocumentSet">

       4:     <Folder TargetName="_cts/Test Doc Set" />

       5:     <FieldRefs>

       6:       <FieldRef ID="{038d1503-4629-40f6-adaf-b47d1ab2d4fe}" Name="Company" />

       7:     </FieldRefs>

       8:     <XmlDocuments>

       9:       <XmlDocument NamespaceURI="http://schemas.microsoft.com/sharepoint/events">

        <spe:Receivers xmlns:spe="http://schemas.microsoft.com/sharepoint/events">

          <Receiver>

            <Name>DocumentSet ItemUpdated</Name>

            <Synchronization>Synchronous</Synchronization>

            <Type>10002</Type>

            <SequenceNumber>100</SequenceNumber>

            <Assembly>Microsoft.Office.DocumentManagement, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c</Assembly>

            <Class>Microsoft.Office.DocumentManagement.DocumentSets.DocumentSetEventReceiver</Class>

            <Data />

            <Filter />

          </Receiver>

          <Receiver>

            <Name>DocumentSet ItemAdded</Name>

            <Synchronization>Synchronous</Synchronization>

            <Type>10001</Type>

            <SequenceNumber>100</SequenceNumber>

            <Assembly>Microsoft.Office.DocumentManagement, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c</Assembly>

            <Class>Microsoft.Office.DocumentManagement.DocumentSets.DocumentSetItemsEventReceiver</Class>

            <Data />

            <Filter />

          </Receiver>

        </spe:Receivers>

      </XmlDocument>

      <XmlDocument NamespaceURI="http://schemas.microsoft.com/office/documentsets/allowedcontenttypes">

        <act:AllowedContentTypes xmlns:act="http://schemas.microsoft.com/office/documentsets/allowedcontenttypes" LastModified="11/4/2009 3:30:17 PM">

          <AllowedContentType id="0x0101" />

        </act:AllowedContentTypes>

      </XmlDocument>

      <XmlDocument NamespaceURI="http://schemas.microsoft.com/office/documentsets/sharedfields">

        <sf:SharedFields xmlns:sf="http://schemas.microsoft.com/office/documentsets/sharedfields" LastModified="11/4/2009 3:31:50 PM">

          <SharedField id="cbb92da4-fd46-4c7d-af6c-3128c2a5576e" />

          <SharedField id="038d1503-4629-40f6-adaf-b47d1ab2d4fe" />

        </sf:SharedFields>

      </XmlDocument>

      <XmlDocument NamespaceURI="http://schemas.microsoft.com/office/documentsets/welcomepagefields">

        <wpf:AllowedContentTypes xmlns:wpf="http://schemas.microsoft.com/office/documentsets/welcomepagefields" LastModified="11/4/2009 3:31:50 PM">

          <WelcomePageField id="038d1503-4629-40f6-adaf-b47d1ab2d4fe" />

        </wpf:AllowedContentTypes>

      </XmlDocument>

      <XmlDocument NamespaceURI="http://schemas.microsoft.com/office/documentsets/defaultdocuments">

        <dd:DefaultDocuments xmlns:dd="http://schemas.microsoft.com/office/documentsets/defaultdocuments" LastModified="11/5/2009 8:39:24 AM" AddSetName="True">

          <DefaultDocument name="Enterprise Content Management.docx" idContentType="0x0101" />

          <DefaultDocument name="Extending Search.docx" idContentType="0x0101" />

        </dd:DefaultDocuments>

      </XmlDocument>

      <XmlDocument NamespaceURI="http://schemas.microsoft.com/sharepoint/v3/contenttype/forms">

        <FormTemplates xmlns="http://schemas.microsoft.com/sharepoint/v3/contenttype/forms">

          <Display>DocSetDisplayForm</Display>

          <Edit>ListForm</Edit>

          <New>DocSetDisplayForm</New>

        </FormTemplates>

      </XmlDocument>

      <XmlDocument NamespaceURI="http://schemas.microsoft.com/sharepoint/v3/contenttype/forms/url">

        <FormUrls xmlns="http://schemas.microsoft.com/sharepoint/v3/contenttype/forms/url">

          <New>_layouts/NewDocSet.aspx</New>

        </FormUrls>

      </XmlDocument>

    </XmlDocuments>

  </ContentType>

</Elements>

As you can see, the basics are the same as for any content type. The main difference is in all the XmlDocument elements in there:

Some event handlers are hooked up to make sure the metadata gets pushed down into the child documents (plus some other stuff)
The content types that users are allowed to add to the set are specified
We specify which fields are shared between the documents the set contains
The fields that are shown on the welcome page are defined as well
We then specify if there’s default content to add when a new Document Set is created

After we’ve created the basic plumbing for the Document Set content type, we’ll need to make sure that the files that are required are created in the right place as well. In order to accomplish this we’ll add a SharePoint Module item to the solution. This module will create the welcome page and default content in the right location in the site collection. The element.xml file will contain the following content:

       1: <?xml version="1.0" encoding="utf-8"?>

       2: <Elements xmlns="http://schemas.microsoft.com/sharepoint/">

       3:   <Module Name="_ctsTest Doc Set_" HyperlinkBaseUrl="http://moss.contoso.com/sites/docsettest" Path="WelcomePages\Files\_cts\Test Doc Set" Url="_cts/Test Doc Set">

       4:     <File Url="docsethomepage.aspx" Path="docsethomepage.aspx">

       5:       <AllUsersWebPart WebPartOrder="0" WebPartZoneID="WebPartZone_TopLeft" ID="g_ae6da3d4_9233_45d6_b9fd_6300815e16c6">

       6:         <![CDATA[Content omitted]]>

       7:       </AllUsersWebPart>

       8:       <AllUsersWebPart WebPartOrder="0" WebPartZoneID="WebPartZone_CenterMain" ID="g_d8062545_cc87_4e82_9c55_cae80486ffea">

       9:         <![CDATA[Content omitted]]>

      10:       </AllUsersWebPart>

      11:       <AllUsersWebPart WebPartOrder="0" WebPartZoneID="WebPartZone_Top" ID="g_651be1ba_c8bb_4d29_87b0_87c769cd5179">

      12:         <![CDATA[Content omitted]]>

      13:       </AllUsersWebPart>

      14:     </File>

      15:     <File Path="Enterprise Content Management.docx" Url="Enterprise Content Management.docx" />

      16:     <File Path="Extending Search.docx" Url="Extending Search.docx" />

      17: </Module>

      18: </Elements>

We see that the page layout for the document set homepage is created in the _cts folder for the content type. The web parts that are placed on the page are configured here as well, so any modifications and additions will be used on the welcome page of all document sets based in this content type. Also the two documents for the default content are placed in the corresponding _cts folder in the site collection.

The final Visual Studio solution will look like this:

After deploying the solution and activating the feature, which is very easy to do with the new SharePoint stuff in Visual Studio (just press ctrl + f5), we can see that the _cts folder will be created in the site collection:

After we add the content type to a document library and create a new item based on the content type we’ll be presented with the following:

You can download the sample solution here: DocSetProvisioning.zip (62,88 KB)
DISCLAIMER: This hasn't been properly tested, so there's is no guarantee it will work. If it f***s up your farm, the most you can expect as support from me, is an email wishing you good luck with restoring it.

Categorie: Document sets

Share: