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\14\TEMPLATE\FEATURES
Copy and
paste the folder and rename it. Assume we rename it
MyCompany.MyCustomDocumentLibrary.
href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg7CIfvK_TpTVVY9U7ENAQDVJy5A7tawBuw2UEwV4xjd27MAZLhLNCDE9HL8UIA4KibLV5_Q9dHiud51_vo6E-Ii5OW_TWUt5c29iR-p0SiqEF2_ZziQSou__EUivP8LHVxRk_e7frD5EjO/s1600/Creating+a+custom+document+library+for+sharepoint+2010+-+010+-+duplicating+DocuementLibrary+folder.jpg">style="WIDTH: 320px; HEIGHT: 239px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666374063853351122 border=0 alt=""
src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg7CIfvK_TpTVVY9U7ENAQDVJy5A7tawBuw2UEwV4xjd27MAZLhLNCDE9HL8UIA4KibLV5_Q9dHiud51_vo6E-Ii5OW_TWUt5c29iR-p0SiqEF2_ZziQSou__EUivP8LHVxRk_e7frD5EjO/s320/Creating+a+custom+document+library+for+sharepoint+2010+-+010+-+duplicating+DocuementLibrary+folder.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">Open
the Feature.xml file with Visual Studio or a text editor, and change these
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">Add
the following 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">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\14\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.)
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">Here
is the new xml after the changes has been performed:
size=2><?size=2>xml
size=2>versionsize=2>="color=#0000ff size=2>1.0"size=2> size=2>encodingsize=2>="color=#0000ff size=2>utf-8size=2>"size=2>?>
<size=2>Featuresize=2> size=2>Idsize=2>="color=#0000ff size=2>00BFEA71-E717-4E80-AA17-D0C71B310001size=2>"
size=2>
Titlesize=2>="color=#0000ff size=2>MyCompany MyCustom Document Librarysize=2>"
size=2>
Descriptionsize=2>="color=#0000ff size=2>Allow a custom document library to be created within this
site"
color=#ff0000
size=2>
Versionsize=2>="color=#0000ff size=2>1.0.0.0"
color=#ff0000 size=2>size=2>
Scopesize=2>="color=#0000ff size=2>Web"
color=#ff0000 size=2>size=2>
Hiddensize=2>="color=#0000ff size=2>False"
color=#ff0000 size=2>size=2>
AlwaysForceInstallsize=2> ="color=#0000ff size=2>TRUE"
color=#ff0000 size=2>size=2>
ImageUrl
="color=#0000ff size=2>MyCompany/sharePointSummitLogo.jpgsize=2>"
size=2>
DefaultResourceFilesize=2>="color=#0000ff size=2>core"size=2>
size=2>size=2>
xmlnssize=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>ElementManifestscolor=#0000ff
size=2>>
size=2><size=2>ElementManifestcolor=#0000ff size=2> color=#ff0000 size=2>Locationcolor=#0000ff size=2>="size=2>size=2>ListTemplates\DocumentLibrary.xml"color=#0000ff size=2>
/>
</size=2>ElementManifestscolor=#0000ff size=2>>
</color=#a31515 size=2>Featurecolor=#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.
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">Here
is the new xml after the changes has been performed:size=2>
<?
size=2>xmlsize=2>versionsize=2>="color=#0000ff size=2>1.0"size=2> size=2>encodingsize=2>="color=#0000ff size=2>utf-8size=2>"size=2>?>
<size=2>Elementssize=2> size=2>xmlnssize=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>
Namesize=2>="color=#0000ff size=2>customdoclib1"
color=#ff0000 size=2>size=2>
Typesize=2>="color=#0000ff size=2>10001"
color=#ff0000 size=2>size=2>
BaseTypesize=2>="color=#0000ff size=2>1"
size=2>size=2>
OnQuickLaunchsize=2>="color=#0000ff size=2>TRUE"
color=#ff0000 size=2>size=2>
SecurityBitssize=2>="color=#0000ff size=2>11"
color=#ff0000 size=2>size=2>
Sequencesize=2>="color=#0000ff size=2>110"
color=#ff0000 size=2>size=2>
DisplayNamesize=2>="color=#0000ff size=2>My Company Document Librarysize=2>"
size=2>
Descriptionsize=2>="color=#0000ff size=2>Create a document library with xyz
functionalities"
size=2>size=2>
Imagesize=2>="color=#0000ff size=2>/_layouts/images/itdl.pngsize=2>"
size=2>
DocumentTemplatesize=2>="color=#0000ff size=2>121"size=2>/>
</color=#a31515 size=2>Elementscolor=#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.
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
we rename the folder to customdoclib1
href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-F-1AaqA53HJRcPpobfSWKKSLd8HHE3RRHLS6xDK3nT6agQ6CiGUYiA5CpF5YU8k3VIF_Exp_n9l80UW4omlJ4ql7gjAdpM1aX2lOhHwGmxKGIw2rQaRptPcUThQOwSDqVy1iTHLnXpBi/s1600/Creating+a+custom+document+library+for+sharepoint+2010+-+020+-+renaming+Doclib+folder.jpg">style="WIDTH: 320px; HEIGHT: 199px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666374060315019298 border=0 alt=""
src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-F-1AaqA53HJRcPpobfSWKKSLd8HHE3RRHLS6xDK3nT6agQ6CiGUYiA5CpF5YU8k3VIF_Exp_n9l80UW4omlJ4ql7gjAdpM1aX2lOhHwGmxKGIw2rQaRptPcUThQOwSDqVy1iTHLnXpBi/s320/Creating+a+custom+document+library+for+sharepoint+2010+-+020+-+renaming+Doclib+folder.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
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
order to obtain this screen
href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh45n_b5P6ut-GBb6cuaMrrIA8BXWjqeSuCylUE7b4LWRAy9k76bQnhzxIv8DMDbdpoICLbNm-ysMmu0V0XkQ5nvCFfKTwUT-8-nnHbWbEpnT_kRNQtc77YGAkhv1faoNlaZp5BHgs7x0zd/s1600/Creating+a+custom+document+library+for+sharepoint+2010+-+030+-+installing+the+feature.jpg">style="WIDTH: 320px; HEIGHT: 160px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666374051135403458 border=0 alt=""
src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh45n_b5P6ut-GBb6cuaMrrIA8BXWjqeSuCylUE7b4LWRAy9k76bQnhzxIv8DMDbdpoICLbNm-ysMmu0V0XkQ5nvCFfKTwUT-8-nnHbWbEpnT_kRNQtc77YGAkhv1faoNlaZp5BHgs7x0zd/s320/Creating+a+custom+document+library+for+sharepoint+2010+-+030+-+installing+the+feature.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="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhvn3lUYi5UpeBk5MZPeH0sFZQktQTK7TMa0DATCJBHOso66zaBwsHVIiQ6DJV7flGTyljF9YZiF19cvKvWrIqtpSEpikq9EzYkMC_vDsPAfpAlnN5E0jVXON0lduMyy9CE0gGuTjXb7XGP/s1600/Creating+a+custom+document+library+for+sharepoint+2010+-+040+-+feature+installed.jpg">style="WIDTH: 320px; HEIGHT: 152px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666374046463454482 border=0 alt=""
src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhvn3lUYi5UpeBk5MZPeH0sFZQktQTK7TMa0DATCJBHOso66zaBwsHVIiQ6DJV7flGTyljF9YZiF19cvKvWrIqtpSEpikq9EzYkMC_vDsPAfpAlnN5E0jVXON0lduMyy9CE0gGuTjXb7XGP/s320/Creating+a+custom+document+library+for+sharepoint+2010+-+040+-+feature+installed.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="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh51Sr6hXvaMiyyIQcQcut1FXr2hP2B4D8K2Xo2lM_rsF0kyZCLnjXqmRf84AmnZKw2gBVn2H0jj6_bJcB_QE6xynLG60i_SzgbTrub1gHNUAsivkhQTifLaaom4dxa4ww4NhlfnA-_Kvpo/s1600/Creating+a+custom+document+library+for+sharepoint+2010+-+050+-+creating+the+custom+library+within+a+SharePoint+2010+site.jpg">style="WIDTH: 320px; HEIGHT: 152px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666374046951971602 border=0 alt=""
src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh51Sr6hXvaMiyyIQcQcut1FXr2hP2B4D8K2Xo2lM_rsF0kyZCLnjXqmRf84AmnZKw2gBVn2H0jj6_bJcB_QE6xynLG60i_SzgbTrub1gHNUAsivkhQTifLaaom4dxa4ww4NhlfnA-_Kvpo/s320/Creating+a+custom+document+library+for+sharepoint+2010+-+050+-+creating+the+custom+library+within+a+SharePoint+2010+site.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="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhxVh-RdMui_88eNiCtph1mUK4p1UxH6sGSttW4XHMRX0m2mtkfDxl5hffRCOnuUCHXZwAuHfIQgPde0NC3VsYeJzJx30c3-nM8p5WtDzQfyNlStJlU1EXxysuSquviJCLpeog6wbT07NKh/s1600/Creating+a+custom+document+library+for+sharepoint+2010+-+060+-+custom+document+library+within+a+SharePoint+2010+site+created.jpg">style="WIDTH: 320px; HEIGHT: 218px; CURSOR: hand"
id=BLOGGER_PHOTO_ID_5666376901611298594 border=0 alt=""
src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhxVh-RdMui_88eNiCtph1mUK4p1UxH6sGSttW4XHMRX0m2mtkfDxl5hffRCOnuUCHXZwAuHfIQgPde0NC3VsYeJzJx30c3-nM8p5WtDzQfyNlStJlU1EXxysuSquviJCLpeog6wbT07NKh/s320/Creating+a+custom+document+library+for+sharepoint+2010+-+060+-+custom+document+library+within+a+SharePoint+2010+site+created.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">Well
done !!!
No comments:
Post a Comment