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

Quebec SharePoint Summit 2012 – Debriefing

mahoneycuttnc2002 — Wed, 09 May 2012 17:03:02 +0000

Le chateau Frontenac by night (Gilles Pommier)

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 am now starting the publishing of several posts based on what I have demonstrated during the two conferences I gave at the summit.
As the language spoken at the conference was french, and in order to serve the conference participants first in their laguage, I will first publish the posts in french within the french version of MOSS-HOW-TO : “MOSS Comment …”.

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">But first of all… In one of the two conferences, I have demonstrated how to do SharePoint publishing with the team sites of SharePoint Foundation.
As an example, I made a real SharePoint web facing site that was a copy of the SharePoint Summit site (that is unfortunately not made with SharePoint (but more for money reasons I learned)).

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">Some of the participants wanted to have the source code of the project. I promised to provide them with it, so here it is (if you don’t see the link you are probably using Google Chrome… sorry, switch to IE or FF):

The backUp file for the site collection –> sharepointsummit-6.bak

The .wsp file for deployment in the farm solution store –> MC.SpSummit_V4.0.0.0.wsp

The source code of the original project for Visual Studio 2008 –> MC.SpSummit.Internet-sources-2012-04-20.zip

1 – Create a Web Application within a SharePoint Farm.

1.2 - choose the 80 port

1.3 - specify this host header : sharepointsummit-ntlm

2 – create a site collection based on the team site template in english.
2.1 - Call it “Accueil”

3 – Modify the hosts file of your machine in order the url href="http://sharepointsummit-ntml">http://sharepointsummit-ntml be recognised by IIS.

3.1 - Test the url. You should display a normal english team site called Accueil by calling this Url at this step of the installation
(if there is a problem of authentification followed by an access denied, refer to href="http://support.microsoft.com/kb/896861">http://support.microsoft.com/kb/896861)

4 - Using administrator permissions for the new site, grant access to the site for anonymous users.

5 – Modify the bindings of your IIS site correponding to the web application and add the following Url :

http://sharepointsummit.org

5.1 - Modify the hosts file in order to be able to access the IIS site with this Url.
5.2 – Test it !

6 – Add the wsp file to the solution store
6.1 – deploy the solution to
the sharepointsummit-ntlm web apllication

7 – restore the .bak file to the site collection

stsadm -o restore -url http://sharepointsummit-ntlm -filename yourPath/sharepointsummit-6.bak -overwrite

Don’t forget the overwrite instruction since there is already a site collection at this Url…

8 – test the 2 Urls :

href="http://sharepointsummit-ntlm/SitePages/Home.aspx">http://sharepointsummit-ntlm/SitePages/Home.aspx

href="http://sharepointsummit.org/SitePages/Home.aspx">http://sharepointsummit.org/SitePages/Home.aspx

It should work…

If you have any trouble, post a comment on this post…

Enjoy !!!

Check it out:MOSS How to …

Creating a virtual machine with an LDAP authentification for SharePoint 2007

BSoD — Tue, 28 Feb 2012 09:46:35 +0000

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Among the best practices to succed in fast developing good solutions for SharePoint is the virtualized environments. The closest you will be to the client production environment within your virtual machines, the best chances you will have to provide your client with a reliable solution in a quick delivery time.

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Assume you have to deliver a solution requiring an form based authentication using LDAP, you sure will want to have a virtual machine with an LDAP and SharePoint on it.

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">This is what we are going to build in this tutorial. We will use a SharePoint farm on a single virtual machine and for the LDAP we will use Open LDAP

style="PADDING-RIGHT: 0px; PADDING-LEFT: 13px; FONT-WEIGHT: bold; PADDING-BOTTOM: 10px; MARGIN: 1px 0px; COLOR: #e9ab17; PADDING-TOP: 10px">1 – Step 1 building the SharePoint 2007 virtual machine

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">I have already published a post on the topic, and there is more complete ones you can examine. So assume you have a virtual machine with SharePoint 2007 properly installed.

style="PADDING-RIGHT: 0px; PADDING-LEFT: 13px; FONT-WEIGHT: bold; PADDING-BOTTOM: 10px; MARGIN: 1px 0px; COLOR: #e9ab17; PADDING-TOP: 10px">2 – Step 2 Intstalling open LDAP on the virtual machine.

style="PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; PADDING-TOP: 0px; BACKGROUND-COLOR: #fcfcfc"
marginWidth=0 marginHeight=0
src="https://skydrive.live.com/embed?cid=624237E0E19DB197&resid=624237E0E19DB197%21329&authkey=AGXYJ6vXkWYhOxY"
frameBorder=0 width=98 scrolling=no height=120>

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

openldap-for-windows.msi
The redistribuable package of open LDAP for windows
ldapbrowser26.msi
The redistribuable package of the free LDAP browser from Softerra
inetorgperson.ldif
A file that will be used to create the first LDAP account

In order to install OPEN LDAP on the virtual machinne double click openldap-for-windows.msi. Click next on the dialogs, letting the default values untill you reach the additional settings dialog. Don’t change anything neither, but notice that your machine name will be retrieved by the installation software, and carefully note the Open LDAP port number : 3899

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Then click next on the other dialogs to start the installation. We are now going to use a browser to check if the installation was successfull

style="PADDING-RIGHT: 0px; PADDING-LEFT: 13px; FONT-WEIGHT: bold; PADDING-BOTTOM: 10px; MARGIN: 1px 0px; COLOR: #e9ab17; PADDING-TOP: 10px"> style="PADDING-RIGHT: 0px; PADDING-LEFT: 13px; FONT-WEIGHT: bold; PADDING-BOTTOM: 10px; MARGIN: 1px 0px; COLOR: #e9ab17; PADDING-TOP: 10px">3 – Step 3 Browsing the LDAP server style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify"> In order to browse the LDAP directory you are going to install the Softerra browser, so this time, double click the ldapbrowser26.msi, and follow installation process untill obtaining this final screen :

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Once the Softera browser is installed, start it and we are going to create a new profile in order to test the LDAP server connection. Right click the Softerra LDAP “Browser root” node in the Scope Pane and start the new profile creation

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify"> Click Next. The software will prompt that base DN is not specified and ask “continue anyway”. Click yes on this message. Then you will be prompted for the User DN and Password.

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Where could be this information ? Actually, it is in the Open LDAP configuration file. So locate this file. It should be:

C:\Program Files\OpenLDAP\slapd.conf

rootdn ”cn=Manager,dc=maxcrc,dc=com” # Cleartext passwords, especially for the rootdn, should # be avoid. See slappasswd(8) and slapd.conf(5) for details. # Use of strong authentication encouraged. rootpw secret

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">This is the LDAP admin account color=#004080>cn=Manager,dc=maxcrc,dc=com and its password, color=#004080>secret so just type them in the LDAP Browser dialog:

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Let the next screen default values and click finish. You will be prompted for the password again, so type it again and you should obtain this screen indication that your LDAP server is working properly:

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

style="PADDING-RIGHT: 0px; PADDING-LEFT: 13px; FONT-WEIGHT: bold; PADDING-BOTTOM: 10px; MARGIN: 1px 0px; COLOR: #e9ab17; PADDING-TOP: 10px">4 - Step 4 Creating a first user account within the LDAP

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">We are now going to create the first account within the LDAP. This account will be used later to authenticate within SharePoint 2007.

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">We will use the last file of the downloaded package: inetorgperson.ldif. Go back to the OpenLDAP directory and create a ldif folder, then copy the inetorgperson.ldif file and paste it in the ldif repository.

C:\Program Files\OpenLDAP\ldif\inetorgperson.ldif

C:\Program Files\OpenLDAP\ClientTools\ldapmodify.exe

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">then, in the command prompt type a space and paste this line after having replaced VMLDAP-003 by your machine name:

style="DISPLAY: inline! important; FLOAT: none; WORD-SPACING: 0px; FONT: small arial; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; -webkit-text-size-adjust: auto; orphans: 2; widows: 2; -webkit-text-stroke-width: 0px">-a -h VMLDAP-003 -p 3899 -D “cn=Manager,dc=maxcrc,dc=com” -w secret -f “C:\Program Files\OpenLDAP\ldif\ style="WORD-SPACING: 0px; FONT: small arial; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; -webkit-text-size-adjust: auto; orphans: 2; widows: 2; -webkit-text-stroke-width: 0px"> style="DISPLAY: inline! important; FLOAT: none; WORD-SPACING: 0px; FONT: small arial; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; -webkit-text-size-adjust: auto; orphans: 2; widows: 2; -webkit-text-stroke-width: 0px">inetorgperson.ldif”

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">You will notice on the screen that the ou people has been added and within the ou, the first account for the user Robert Smith.

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Now if we go back in the Softerra 2.6 browser, we notice we can browse the people ou and also the Robert Smith account.

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Notice we can also see the user password (rJsmitH) that will be useful later to authenticate within SharePoint 2007

style="PADDING-RIGHT: 0px; PADDING-LEFT: 13px; FONT-WEIGHT: bold; PADDING-BOTTOM: 10px; MARGIN: 1px 0px; COLOR: #e9ab17; PADDING-TOP: 10px">5 - Step 5 Creating the NTLM web application for the LDAP based permissions

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">For the LDAP authentication we need a specific web application because the form based authentication will be processed by an IIS web site and the LDAP connection reference will be stored within the web application web.config.

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Actually, we need two IIS web sites. The first IIS web site is the one corresponding to the web application. The web application will be accessed in NTLM mode. This will allow administrator and power user to manage content and permissions using NTLM accounts (AD or local accounts). Then we will extend this web application for the LDAP authentication. This will create a second IIS web site that will be used for the form based authentication using LDAP accounts.

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">All this seems to be a bit confusing if you are not used to, but don’t worry, we will proceed step by step and all be clearer as long as we perform required operations…

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">So first let us create the web application. Open the SharePoint Central Administration. Click the Application Management tab. Then, click the first link of the first section: Create or extend Web Application. On the displayed dialog, click “Create a new Web Application”

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Now I want to show you how to be as close as possible to a real production environment, so we are going to use the 80 port and an host header. Assume the web application is used in real life for managing content (ECM) for the contoso company… So here are the parameters to be typed:

Create a new IIS web site – description: Web Application ECM NTLM

Port: 80

Host Header: myECM.ntlm.contoso.com

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">for the application pool, if you plan to dedicate one application pool to this web application you should call it:

SharePoint myECM.contoso.com

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Because we don’t need to make the distinction between NTLM and Form Based Authentication for the application pool since the both IIS web sites (the one for NTLM and the one for FBA LDAP) will use it. But if you plan to use the application pool for other web applications of your contoso company, you should call it:

SharePoint contoso.com

Application pool user name: SPS_myECM

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">You should have created a dedicated service account for the application pool process. Just create an account (AD or local) with a password that never expires (it is diffferent for SharePoint 2010). Don’t worry with permissions, the web application creation job will set all the required permissions automatically at the web application creation time.

Database Name and Authentication – database name: WSS_Content_MyECM

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

style="PADDING-RIGHT: 0px; PADDING-LEFT: 13px; FONT-WEIGHT: bold; PADDING-BOTTOM: 10px; MARGIN: 1px 0px; COLOR: #e9ab17; PADDING-TOP: 10px">6 - Step 6 Accessing the NTLM web application

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">For accessing the new site collection from your local machine, first with have to modify the hosts file of the machine since we have specified an Host Header.

C:\WINDOWS\system32\drivers\etc\hosts

127.0.0.1 myecm.ntlm.contoso.com

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">now try to access the site collection. You are prompted for credential and finaly you get an 401 error access denied. Hum…. Don’t worry iti is perfectly normal….

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Now, let us do another test. Minimize you virtual machine and switch to your host machine (the computer that is running the virtual machine), and do the same, modify the hosts file of your host computer… Sometimes it is working with the virtual machine name. If it is not working, get the virtual machine IP by typing IPCONFIG in a command prompt within your virtual machine, or doing a ping of the virtual machine using its name from your host computer

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">and try to connect to your site collection from your host computer. Yes it is possible and leads to many oportunities like using two different versions of IE, using the Office applications of your host machine and so on !!!! It does work !!!

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Hum, why is it working from the host computer and we get an access denied from the local machine ? It is because we need to specify host name on the local machine or disable the loopback check. See this href="http://support.microsoft.com/kb/896861">Microsoft kb entry

style="PADDING-RIGHT: 0px; PADDING-LEFT: 13px; FONT-WEIGHT: bold; PADDING-BOTTOM: 10px; MARGIN: 1px 0px; COLOR: #e9ab17; PADDING-TOP: 10px">7 - Step 7 Extending the Web application for LDAP Authentication

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Now is the time to extend the existing web application in order to create an IIS web site for the authentication using LDAP accounts.

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Go back to the central administration. Click the Application Management tab. Then, click the first link of the first section: Create or extend Web Application. On the displayed dialog, this time, click “Extend an existing Web Application” Use the Web Application drop down list to choose the Web Application ECM NTLM previusly created

Create a new IIS web site – description: Web Application ECM LDAP

Port: 80

Host Header: myECM.ldap.contoso.com

Zone: Intranet

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

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Now go back to the SharePoint Central administration and under the Application Security section click the Authentication providers link

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">then click the Intranet link and in the next page select the Form radio button. The page is refreshing and the new interface let you type the membership provider name. Type

LdapMembershipProvider

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify"> The membership provider is used for individual permissions and the role provider to grant permissions to a group of user. In this tutorial we won’t demonstrate the role provider but only the membership provider. So once the membershipprovider is specified, click OK to save the settings and close the page.

style="PADDING-RIGHT: 0px; PADDING-LEFT: 13px; FONT-WEIGHT: bold; PADDING-BOTTOM: 10px; MARGIN: 1px 0px; COLOR: #e9ab17; PADDING-TOP: 10px">9 - Step 9 Modifying the web.config of the NTLM Web Application

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Now, we have to modify the web.config files of the two web sites. So first, open the web.config of the “Web Application ECM NTLM” web site and locate the end of the system.web main section. You can use this trick: look for the machineKey tag…

      <membership defaultProvider="LdapMembershipProvider">

          <providers>

              <add

              name="LdapMembershipProvider"

              type="Microsoft.Office.Server.Security.LDAPMembershipProvider, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C"

              server="VMLDAP-003"

              port="3899"

              useSSL="false"

              connectionUsername="cn=Manager,dc=maxcrc,dc=com"

              connectionPassword= "secret"

              userNameAttribute="uid"

              userContainer="ou=people,dc=maxcrc,dc=com"

              userFilter="(objectClass=*)"

              scope="Subtree"/>

          providers>

      membership>

  system.web>

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">So open the NTLM web site and try to grant robert smith the member permission for the site by using its ldap uid. If you type the uid rjsmith in the people picker and click the check names icon it does work. SharePoint connect the LDAP server and retrieve the rjsmith account. Once the account is retrieved, the typed uid become underlined and if you roll over the uid with the mouse pointer you will see the membership provider name appear in a tool tip.

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">So, click ok in order to actually grant this account the member permisions for the site. You will notice that the account is now referenced within SharePoint as a user of the member of the site.

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

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Now modify the web.config of the "Web Application ECM LDAP" web site in exactly the same way we did for the NTLM one before. style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">Then browse to the LDAP site using the host header. (of course you have modify the hosts file of the machine before). You will be prompted for a Form Based Authentication within the OOTB SharePoint 2007 login page. style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">

rjsmith rJsmitH

style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">You will be authentified as Robert Smith and be able to contribute to the site. style="PADDING-RIGHT: 5px; PADDING-LEFT: 18px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; COLOR: gray; PADDING-TOP: 5px; FONT-FAMILY: arial; TEXT-ALIGN: justify">

Check it out:MOSS How to ...

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 …

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

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 …

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!

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

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

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

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

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

Quebec SharePoint Summit 2012 – Debriefing

Related Posts:

Creating a virtual machine with an LDAP authentification for SharePoint 2007

Related Posts:

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: