SharePoint Administration « Off Shore Development India

Posts Tagged ‘SharePoint Administration’

MOSS9 / Creating Publishing Content Types

Thursday, July 10th, 2008

SharePoint team and Project server team at offshoresoftwaredevelopmentindia.com has great experience of creating web application based on MOSS 2007 and Project server 2007. That includes customization and development of webpart, site definitions, theme development, extension development, module creation. The team has developed CRM application, Job portal, Project management, to CMS applications based on MOSS 2007 and project server 2007.

Team would like to share same experience. This can help who wanted to begin with the sharePoint development and Project Server development.

There are list of articles start with SP and from number 1 to …. Always start with the article SP1 and read next article to start working on MOSS easily and quickly.

How to Create Site Columns:

Before going into detail on the creation of content types via features it is important to understand how Content type IDs work.

You should read the following MSDN page that explains about ContenTypes IDs and their inheritance based model: http://msdn2.microsoft.com/en-us/library/aa543822.aspx

Since this post shows how to create Publishing Content Types we need to find from which existing content type we want to base our own. I did some research on the features that are installed and activated when you use the Publishing site. In there we can see that the base content type from which we want to inherit is the “Page”. This Content Type has an ID of:

0×010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB0
64584E219954237AF39

So in order to create our own ID we can add two hexadecimal values, or, we can add “00″ followed by a GUID. I prefer this approach as it is unique and identifies custom content types more easily.

So my content type ID can be:

0×010100C568DB52D9D0A14D9B2FDCC96666E9F20079481
30EC3DB064584E219954237AF3900ADB88465BE2C439798977662094183BC

The bold text is the Page content type ID to which I append “00″ and a new GUID.

Content Type Schema:

Second important piece of information is the Content Type schema. I could not find any information specific to publishing content types on MSDN or the MOSS SDK. So again the solution is to use the available information together with some nosing in the publishing features installed by MOSS in the 12 hive. ContentType schema on MSDN: http://msdn2.microsoft.com/en-us/library/aa544268.aspx

In the following sample I’m creating two content types: a product content type and a hardware product content type. You will see that the hardware product content type inherits from the product content type by appending 00 + a new GUID to the ID.

<!– Product base content type –>
<ContentType ID=”0×010100C568DB52D9D0A14D9B2FDCC96666E9F2007
948130EC3DB064584E219954237AF3900ADB88465BE2C43979
8977662094183BC” Name=”$Resources:contenttype_productbase_name;” Description=”$Resources:contenttype_productbase_description;” Group=”$Resources:group_productcontenttypes;” Sealed=”FALSE” Version=”0″>
<FieldRefs>
<FieldRef ID=”{F44BFBB0-4725-4167-B976-F85F84131AA3}” Name=”ProductCategory” Required=”FALSE” />
<FieldRef ID=”{EB19D87C-5DEE-4a73-85E0-506293D422D9}” Name=”ProductName” Required=”TRUE” />
<FieldRef ID=”{D73843E5-0D9F-4400-BC75-1A4C2BD27900}” Name=”ProductIntro” Required=”TRUE” />
<FieldRef ID=”{894635F9-1DF8-46f1-BC47-46EFF09FEF3D}” Name=”ProductDescription” Required=”FALSE” />
<FieldRef ID=”{D89C9409-2A97-4a7a-81F5-7D45E7CD8D6B}” Name=”LaunchDate” Required=”TRUE” />
<FieldRef ID=”{6036ECDE-521A-4dbe-94B4-40E0E4EF7029}” Name=”ProductImage” Required=”FALSE” />
<FieldRef ID=”{F31DF817-D220-4449-BD6F-2F1B7C0823ED}” Name=”ProductPrice” Required=”TRUE” />
</FieldRefs>
<DocumentTemplate TargetName=”/_layouts/CreatePage.aspx” />
</ContentType>

</Elements>

Now we need to add this to the feature and install it together with what was done in part I of this series.

The complete feature can be downloaded here.

Refer:

http://www.katriendg.com/aboutdotnet/2007_4_2_publishing-content-types.aspx

Tags: Learn SharePoint Server, Microsoft SharePoint Server, MOSS, MOSS 2007 development, MOSS Customization, MOSS Design, Publishing Content Type for MOSS, SharePoint Administration, SharePoint code, Sharepoint Configuration, sharepoint customization, sharepoint experts, Sharepoint Server, sharepoint server 2007
Posted in .Net Development, ASP.Net Frameworks, C# Development, Microsoft Project Server, Microsoft SharePoint Server, Uncategorized | No Comments »

MOSS8 / Create Site Columns in SharePoint Server

Thursday, June 12th, 2008

Team would like to share same experience. This can help who wanted to begin with the sharePoint development and Project Server development.

There are list of articles start with SP and from number 1 to …. Always start with the article SP1 and read next article to start working on MOSS easily and quickly.

Creating Site Columns:

In this 3 part series I will explain the steps you need to follow in order to create site columns, content types and page layouts for use with a MOSS publishing site.

There is already quite some information to be found on the internet on how to create site columns and custom lists using a feature, however most part apply to team sites (WSS3 sites), not MOSS publishing sites.

Field definition schema:

Site columns are created by placing <Field> elements inside an <Elements> tag. It is important to review the <Field> element definition before going any further. The complete schema definition is detailed in the WSS3 SDK which can be consulted online on the MSDN site (http://msdn2.microsoft.com/en-us/library/ms437580.aspx). On the mentioned URL you can find all the types of fields available out of the box, the required attributes, possible values and so forth.

This is very good documentation for WSS3 fields but information on extra field types for publishing site columns is not available. At least I was unable to find it in the MOSS SDK or online. My solution was to look at the feature definitions used by MOSS publishing feature available out of the box.

Most of the attributes of the <Field> element are optional. This is a sample field definition using the most common attributes:

<Field

ID=”{4C67267C-B950-4cd4-8038-DEACA9EC2F74}”
Name=”IntroductionText”
StaticName=” IntroductionText ” SourceID=”http://schemas.microsoft.com/sharepoint/v3″
Group=”My publishing fields group”
DisplayName=”Introduction text field”
Type=”Text”
Required=”FALSE”
Sealed=”TRUE”
MaxLength=”250″>

</Field>

When using other types of fields there are extra attributes that are useful.

A note about the sealed attribute: setting this to “TRUE” will ensure the field cannot be removed via the “Change column” page. However when you are creating a choice field (a dropdown, a checkbox list), and you want your users to be able to edit the list of values you need to set sealed to FALSE.

Some attributes are only used in combination with some types of fields, like for example the StorageTZ attribute, which is useful together with Type=”DateTime”.

When it comes to publishing field types there are some new types that you can use. As far as I could find they are not yet documented. By looking at the “PublishingResources” hidden feature I could find the following:

Field type	Description	Related attributes
Image	Publishing field for storing an image. The edit control shows the Insert picture button.	RichText=”TRUE” RichTextMode=”FullHtml”
HTML	HTML editing control	RichText=”TRUE” RichTextMode=”FullHtml”
Link	Hyperlink control In edit mode, allows the user to select an internal file (also external links can be allowed) In display mode shows the clickable link to the file	RichText=”TRUE” RichTextMode=”FullHtml”
SummaryLinks	Field control for editing a list of links

There are also some extra fields that are related to the page publishing content types such as “Publishing schedule start date”. I don’t think you’d like to use these as the page content types normally already inherit these types of columns.

As a sample for this and the following posts in this series I’m creating a product page content type. My product contains 8 fields going from name and description, date, image, price.

This is the XML schema (myfields.xml):

<?xml version=”1.0″ encoding=”utf-8″ ?>
<!– _lcid=”1033″ _version=”12.0.4017″ _dal=”1″ –>
<!– _LocalBinding –>
<!–
–>
<Elements xmlns=”http://schemas.microsoft.com/sharepoint/”>
<Field ID=”{F44BFBB0-4725-4167-B976-F85F84131AA3}” Name=”ProductCategory” StaticName=”ProductCategory” SourceID=”http://schemas.microsoft.com/sharepoint/v3″ Group=”$Resources:column_group_products;” DisplayName=”$Resources:column_productcategory_displayname;” Type=”Choice” Format=”Dropdown” Required=”FALSE” Sealed=”FALSE”>
<CHOICES>
<CHOICE>$Resources:column_productcategory_choice1;</CHOICE>
<CHOICE>$Resources:column_productcategory_choice2;</CHOICE>
<CHOICE>$Resources:column_productcategory_choice3;</CHOICE>
</CHOICES>
</Field>
<Field ID=”{EB19D87C-5DEE-4a73-85E0-506293D422D9}” Name=”ProductName” StaticName=”ProductName” SourceID=”http://schemas.microsoft.com/sharepoint/v3″ Group=”$Resources:column_group_products;” DisplayName=”$Resources:column_productname_displayname;” Type=”Text” Required=”TRUE” Sealed=”TRUE” MaxLength=”255″></Field>
<Field ID=”{D73843E5-0D9F-4400-BC75-1A4C2BD27900}” Name=”ProductIntro” StaticName=”ProductIntro” SourceID=”http://schemas.microsoft.com/sharepoint/v3″ Group=”$Resources:column_group_products;” DisplayName=”$Resources:column_intro_displayname;” Type=”Text” Description=”$Resources:column_intro_description;” Required=”TRUE” Sealed=”TRUE” MaxLength=”500″ NumLines=”2″></Field>
<Field ID=”{894635F9-1DF8-46f1-BC47-46EFF09FEF3D}” Name=”ProductDescription” StaticName=”ProductDescription” SourceID=”http://schemas.microsoft.com/sharepoint/v3″ Group=”$Resources:column_group_products;” DisplayName=”$Resources:column_productdesc_displayname;” Type=”HTML” Required=”FALSE” Sealed=”TRUE” RichText=”TRUE” RichTextMode=”FullHtml”></Field>
<Field ID=”{D89C9409-2A97-4a7a-81F5-7D45E7CD8D6B}” Name=”LaunchDate” StaticName=”LaunchDate” SourceID=”http://schemas.microsoft.com/sharepoint/v3″ Group=”$Resources:column_group_products;” DisplayName=”$Resources:column_date_displayname;” Type=”DateTime” Format=”DateTime” Required=”TRUE” Sealed=”TRUE” StorageTZ=”UTC”></Field>
<Field ID=”{6036ECDE-521A-4dbe-94B4-40E0E4EF7029}” Name=”ProductImage” StaticName=”ProductImage” SourceID=”http://schemas.microsoft.com/sharepoint/v3″ Group=”$Resources:column_group_products;” DisplayName=”$Resources:column_image_displayname;” Type=”Image” Required=”FALSE” Sealed=”TRUE” RichText=”TRUE” RichTextMode=”FullHtml”></Field>
<Field ID=”{6A08E31A-0620-45df-BAC1-54A4D0FBFDCE}” Name=”ProductManual” StaticName=”ProductManual” SourceID=”http://schemas.microsoft.com/sharepoint/v3″ Group=”$Resources:column_group_products;” DisplayName=”$Resources:column_manual_displayname;” Type=”Link” Required=”FALSE” Sealed=”TRUE” RichText=”TRUE” RichTextMode=”FullHtml”></Field>
<Field ID=”{F31DF817-D220-4449-BD6F-2F1B7C0823ED}” Name=”ProductPrice” StaticName=”ProductPrice” SourceID=”http://schemas.microsoft.com/sharepoint/v3″ Group=”$Resources:column_group_products;” DisplayName=”$Resources:column_productprice_displayname;” Type=”Currency” Required=”TRUE” Sealed=”TRUE” Decimals=”2″></Field>
</Elements>

To install the field definitions via a feature I’m creating a feature.xml file that refers to the myfields.xml. In the feature file I also add a dependency to the PublishingSite feature.

A note about resources files:

As you may notice in the display name and description attributes I’m referring to a resource instead of typing in the text. I recommend using resource files whenever translatable (non system name) text is used.

Living in Belgium, a country where we have three official languages I’m used to creating multi-lingual applications. Even when a first requirement does not specify a multi-lingual approach I still prefer to foresee resource files.

When creating features you can use local resource files by placing them in a sub-folder in the feature directory.

Tags: Learn SharePoint Server, Microsoft SharePoint Server, MOSS, MOSS 2007 development, MOSS Design, SharePoint Administration, SharePoint code, Sharepoint Configuration, sharepoint customization, sharepoint experts, sharepoint server 2007, Site Columns for MOSS
Posted in .Net Development, ASP.Net Frameworks, C# Development, Microsoft Project Server, Microsoft SharePoint Server | No Comments »

MOSS4 / Create Minimal Master Page for SharePoint

Wednesday, May 14th, 2008

Team would like to share same experience. This can help who wanted to begin with the sharePoint development and Project Server development.

There are list of articles start with SP and from number 1 to … Always start with the article SP1 and read next article to start working on MOSS easily and quickly.

How to Create Minimal Master Page for MOSS:

Go to Site Action -> Site setting -> Modify All Site Settings.

Then you will see the following screen. Then click on

Galleries -> Master pages and page layouts

You will see page as following image.

Click on default.master, it opens pop up then click send to -> Download a Copy

Save it to local drive. Rename defalt.master to maven.master. (Your referred name)

Then click on upload link.

On clicking upload link following page will be displayed. Click browse, select .master file we have renamed and click ok.

After clicking Ok, you will see following page. Select Content Type Publishing Master Page. Add the name and description. And click check in.

Click on maven.master. we will see popup menu. Click on check out to make master page writable. Then click on maven.master, from popup click edit in Microsoft office sharepoint designer.

This will open sharepoint server. Give the username and password of the site. The code of the current maven.master will be open.

Replace code of the current maven.master with following code.

<%– Identifies this page as a .master page written in Microsoft Visual C# and registers tag prefixes, namespaces, assemblies, and controls. –%>
<%@ Master language=”C#” %>
<!DOCTYPE html PUBLIC “-//W3C//DTD HTML 4.01 Transitional//EN” “http://www.w3.org/TR/html4/loose.dtd”>
<%@ Import Namespace=”Microsoft.SharePoint” %>
<%@ Register Tagprefix=”SPSWC” Namespace=”Microsoft.SharePoint.Portal.WebControls” Assembly=”Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>
<%@ Register Tagprefix=”SharePoint” Namespace=”Microsoft.SharePoint.WebControls” Assembly=”Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>
<%@ Register Tagprefix=”WebPartPages” Namespace=”Microsoft.SharePoint.WebPartPages” Assembly=”Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>
<%@ Register Tagprefix=”PublishingWebControls” Namespace=”Microsoft.SharePoint.Publishing.WebControls” Assembly=”Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>
<%@ Register Tagprefix=”PublishingNavigation” Namespace=”Microsoft.SharePoint.Publishing.Navigation” Assembly=”Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>
<%@ Register TagPrefix=”wssuc” TagName=”Welcome” src=”~/_controltemplates/Welcome.ascx” %>
<%@ Register TagPrefix=”wssuc” TagName=”DesignModeConsole” src=”~/_controltemplates/DesignModeConsole.ascx” %>
<%@ Register TagPrefix=”PublishingVariations” TagName=”VariationsLabelMenu” src=”~/_controltemplates/VariationsLabelMenu.ascx” %>
<%@ Register Tagprefix=”PublishingConsole” TagName=”Console” src=”~/_controltemplates/PublishingConsole.ascx” %>
<%@ Register TagPrefix=”PublishingSiteAction” TagName=”SiteActionMenu” src=”~/_controltemplates/PublishingActionMenu.ascx” %>
<%– Uses the Microsoft Office namespace and schema. –%>
<html>
<WebPartPages:SPWebPartManager runat=”server”/>
<SharePoint:RobotsMetaTag runat=”server”/>

<%– The head section includes a content placeholder for the page title and links to CSS and ECMAScript (JScript, JavaScript) files that run on the server. –%>
<head runat=”server”>
<asp:ContentPlaceHolder runat=”server” id=”head”>
<title>
<asp:ContentPlaceHolder id=”PlaceHolderPageTitle” runat=”server” />
</title>
</asp:ContentPlaceHolder>
<Sharepoint:CssLink runat=”server”/>
<asp:ContentPlaceHolder id=”PlaceHolderAdditionalPageHead” runat=”server” />
</head>

<%– When loading the body of the .master page, SharePoint Server 2007 also loads the SpBodyOnLoadWrapper class. This class handles .js calls for the master page. –%>
<body onload=”javascript:_spBodyOnLoadWrapper();”>
<%– The SPWebPartManager manages all of the Web part controls, functionality, and events that occur on a Web page. –%>
<form runat=”server” onsubmit=”return _spFormOnSubmitWrapper();”>
<wssuc:Welcome id=”explitLogout” runat=”server”/>
<PublishingSiteAction:SiteActionMenu runat=”server”/>
<PublishingWebControls:AuthoringContainer id=”authoringcontrols” runat=”server”>
<PublishingConsole:Console runat=”server” />
</PublishingWebControls:AuthoringContainer>
<%– The PlaceHolderMain content placeholder defines where to place the page content for all the content from the page layout. The page layout can overwrite any content placeholder from the master page. Example: The PlaceHolderLeftNavBar can overwrite the left navigation bar. –%>
<asp:ContentPlaceHolder id=”PlaceHolderMain” runat=”server” />
<asp:Panel visible=”false” runat=”server”>
<%– These ContentPlaceHolders ensure all default SharePoint Server pages render with this master page. If the system master page is set to any default master page, the only content placeholders required are those that are overridden by your page layouts. –%>
<asp:ContentPlaceHolder id=”PlaceHolderSearchArea” runat=”server”/>
<asp:ContentPlaceHolder id=”PlaceHolderTitleBreadcrumb” runat=”server”/>
<asp:ContentPlaceHolder id=”PlaceHolderPageTitleInTitleArea” runat=”server”/>
<asp:ContentPlaceHolder id=”PlaceHolderLeftNavBar” runat=”server”/>
<asp:ContentPlaceHolder ID=”PlaceHolderPageImage” runat=”server”/>
<asp:ContentPlaceHolder ID=”PlaceHolderBodyLeftBorder” runat=”server”/>
<asp:ContentPlaceHolder ID=”PlaceHolderNavSpacer” runat=”server”/>
<asp:ContentPlaceHolder ID=”PlaceHolderTitleLeftBorder” runat=”server”/>
<asp:ContentPlaceHolder ID=”PlaceHolderTitleAreaSeparator” runat=”server”/>
<asp:ContentPlaceHolder ID=”PlaceHolderMiniConsole” runat=”server”/>
<asp:ContentPlaceHolder id=”PlaceHolderCalendarNavigator” runat =”server” />
<asp:ContentPlaceHolder id=”PlaceHolderLeftActions” runat =”server”/>
<asp:ContentPlaceHolder id=”PlaceHolderPageDescription” runat =”server”/>
<asp:ContentPlaceHolder id=”PlaceHolderBodyAreaClass” runat =”server”/>
<asp:ContentPlaceHolder id=”PlaceHolderTitleAreaClass” runat =”server”/>
<asp:ContentPlaceHolder id=”PlaceHolderBodyRightMargin” runat=”server” />
</asp:Panel>
</form>
</body>
</html>

Above code is default code for any master pages. Whatever our design we need, code it in this file. There is one content place holder which holds the page layout.

Save the file. Then go to master page and layouts page from the site as follows.

Click on maven.master and click check in. This will open following page. Select Major Version (publish). And click open.

Again click maven.master and click Approve/Reject from popup. And click approve.

To change the master page of current site, go to;

Site action -> site settings -> modify all settings

Look and Feel -> Master page

This will open following form,

Select maven.master.
This will apply maven.master to current site.

Fore more details please refer:

http://msdn2.microsoft.com/en-us/library/aa660698.aspx

Tags: Learn SharePoint Server, Microsoft SharePoint Server, Minimal Master Page, MOSS, Moss 2007 customization, MOSS 2007 development, MOSS Design, MOSS Minimal Master Page, SharePoint Administration, SharePoint code, Sharepoint Configuration, sharepoint customization, Sharepoint Server, sharepoint server 2007, SharePoint Server Minimal Master Page, sharepoint server Solutions, Work with Minimal Master Page for MOSS
Posted in .Net Development, ASP.Net Frameworks, C# Development, Microsoft SharePoint Server | No Comments »

MOSS3 / Creating Themes / Skins / Templates

Sunday, May 4th, 2008

Team would like to share same experience. This can help who wanted to begin with the sharePoint development and Project Server development.

There are list of articles start with SP and from number 1 to …. Always start with the article SP1 and read next article to start working on MOSS easily and quickly.

Creating Themes / Skins / Templates

On the SharePoint server go to the Themes folder e.g. c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\Themes

Make a copy one of the existing theme folders and its contents rename it e.g. MyTheme.

Rename the .INF file within the MyTheme folder to MyTheme.INF

Edit MyTheme.INF.
- At the the info section, Change the title, to MyTheme. Change codepage, e.g 22200, replacing the code page will fixing error “A theme with the name ‘MyTheme 1011′ and version already exists on the server.”
- In the titles section, rename the names to your new name. this section is to present the name in the different language.

Provide an image to give a preview of your theme. This image should be placed in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\IMAGES. E.g. tmbMyTheme.gif

Modify the c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\Layouts\1033\SPTHEMES.xml to include a reference to the new MyTheme theme

<Templates>
<TemplateID>MyTheme</TemplateID>
<DisplayName> MyTheme </DisplayName>
<Description> MyTheme has a white background with blue control areas and orange highlights.</Description>
<Thumbnail>images/tmbMyTheme.gif</Thumbnail>
<Preview>images/ tmbMyTheme.gif</Preview>
</Templates>

Modify the CSS within MyTheme folder to personalize your theme.

Run iisreset from the command prompt

Apply the new theme to a ‘test site’

Tags: Creating Theme for MOSS, Learn SharePoint Server, Microsoft SharePoint Server, Moss 2007 customization, MOSS 2007 development, MOSS Design, MOSS Skins, MOSS Templates, MOSS Themes, SharePoint Administration, SharePoint code, Sharepoint Configuration, sharepoint customization, sharepoint experts, sharepoint server 2007, sharepoint server Solutions, SharePoint Themes
Posted in .Net Development, C# Development, Microsoft SharePoint Server | No Comments »

MOSS2/Working with Web Application and Site Collection

Monday, April 14th, 2008

Team would like to share same experience. This can help who wanted to begin with the sharePoint development and Project Server development.

There are list of articles start with SP and from number 1 to …. Always start with the article SP1 and read next article to start working on MOSS easily and quickly.

Working with Web Application and Site Collection:

To start working with WA (Web Application) and SC (Site Collection), open web application we have created by entering link into browser. We need to log in by user name and password which we have given to web application.

See to the following image for home page of the web application. The most important control on the webpage is site Actions.

If you click on the site action button you will see the menu with so many options.

Go to Site Action -> Site setting -> Modify All Site Settings.

After clicking Modify All site Settings you will see following screen.

Change theme of the website:

Please go to

Go to Site Action -> Site setting -> Modify All Site Settings.

Then you will see the following screen. Then click on

Look and feel -> Site theme

Then you will see the following screen to change the theme. Select theme you want and apply it.

After applying we can see the new theme as following screen.

Working with master pages and templates:

Please go to

Go to Site Action -> Site setting -> Modify All Site Settings.

Then you will see the following screen. Then click on

Galleries -> Master pages and page layouts

On clicking master pages you will see page as shown in following image.

Master Page:

ASP.NET master pages allow you to create a consistent layout for the pages in your application. A single master page defines the look and feel and standard behavior that you want for all of the pages (or a group of pages) in your application. You can then create individual content pages that contain the content you want to display. When users request the content pages, they merge with the master page to produce output that combines the layout of the master page with the content from the content page.

How Master Pages Work:

Master pages actually consist of two pieces, the master page itself and one or more content pages.

A master page is an ASP.NET file with the extension .master (for example, MySite.master) with a predefined layout that can include static text, HTML elements, and server controls. The master page is identified by a special @ Master directive that replaces the @ Page directive that is used for ordinary .aspx pages.

In addition to the @ Master directive, the master page also contains all of the top-level HTML elements for a page, such as html, head, and form. For example, on a master page you might use an HTML table for the layout, an img element for your company logo, static text for the copyright notice, and server controls to create standard navigation for your site. You can use any HTML and any ASP.NET elements as part of your master page.

Replaceable Content Placeholders:

In addition to static text and controls that will appear on all pages, the master page also includes one or more ContentPlaceHolder controls. These placeholder controls define regions where replaceable content will appear. In turn, the replaceable content is defined in content pages. After you have defined the ContentPlaceHolder controls, a master page might look like the following.

C#
<%@ Master Language=”C#” %>

<!DOCTYPE html PUBLIC “-//W3C//DTD XHTML
1.1//EN” “http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd”>

<html>
<head runat=”server” >
<title>Master page title</title>
</head>
<body>
<form id=”form1″ runat=”server”>
<table>
<tr>
<td><asp:contentplaceholder id=”Main” runat=”server” /></td>
<td><asp:contentplaceholder id=”Footer” runat=”server” /></td>
</tr>
</table>
</form>
</body>
</html>

Working WebApplication And SiteCollections

Tags: Create Content Place holder, Create Master page, Learn SharePoint Server, Microsoft SharePoint Server, Minimal Master Page, MOSS, Moss 2007 customization, MOSS 2007 development, MOSS Site Collection, MOSS Web Applications, SharePoint Administration, SharePoint code, Sharepoint Configuration, Sharepoint Server, sharepoint server 2007, sharepoint server Solutions, Site Collections, Web Application and Site Collections, Web Application and Site Collections in MOSS, Web Applications, Working with Site Collections, Working with Web Applications
Posted in .Net Development, Microsoft Project Server, Microsoft SharePoint Server | No Comments »

MOSS1 – Create Web Application and Site Collections

Friday, April 4th, 2008

Team would like to share same experience. This can help who wanted to begin with the sharePoint development and Project Server development.

There are list of articles start with SP and from number 1 to …. Always start with the article SP1 and read next article to start working on MOSS easily and quickly.

Installation: SharePoint server 2007 must be installed to perform all the actions.

Create Web Application:

To start working with share point server we need to first install share point server 2007 if it is not installed.

After installation we need to run share point product and services configuration wizard from the

Start menu -> Microsoft office Server -> SharePoint Products and Technologies Configuration Wizard.

See the following image.

Central Administration:

First time to work with the share point server, we need to work with share point central administration.

Start menu -> Microsoft office Server -> Share Point 3.0 Central Administration.

See the following image.

The following image displays the central administration home page. There are three tabs in the central administration panel.

Home
Operations
Application Management

Home Tab:

Operations Tab:

Application Management Tab:

Creating Web Application:

To work with the share point site or to create a new share point site first we need to create share point Web Application.

A Web application is comprised of an Internet Information Services (IIS) site with a unique application pool and can be assigned to an SSP (Shared Services Provider) to enable features such as InfoPath Forms Services, Excel Calculation Services, and Workflows.

To create share point web application, go to

Central administration -> Application Management

Then click on SharePoint Web Application Management -> Create or extend web Application

Provide above mentioned information to the site like website description, Port, Configurable User Name and Password.

Then click OK.

After that we can see following processing screen.

After completion of the processing we can see following application created screen.

Creating Site Collection:

A site collection is a group of sites built on Microsoft Windows SharePoint Services that all exist under a top-level site.

After creating web application, to work with web application we need to create site collection. We cannot work in empty site collection. We have to create site collection.

To create a site collection we need to go to central administration -> Application Management.

We need to select web Application for which we need to create site collection as following screen.

This will show us the list of the site application as following screen. We need to create site application we created ex. Yahoo-1111. Click on Yahoo-1111 as following screen.

Then our web application path will be changed to our created web application’s path with mentioned port-1111 as following screen.

Then we need to feel the data like title, Description, URL, Template, primary site collection administrator and secondary site collection administrator for the site collection as following screen.

URL:

We are creating first site collection for the Web Application so we need to select base site (root site) in the URL. Select “/”.

Template:

There are many types of templates available. There are for tabs for the template. We are creating publishing site so we need to create publishing tab and then need to select publishing portal.

Site Collection Administrator:

Site Collection Administrator should be user of the current server, either from administrative group or from non administrative group.

Please see the following image for all these details.

After submitting above details we will see following processing screen.

On completion of the processing we will get message top level site collection successfully created as per following screen.

Site collection is created successfully.

Now we can work with web application with mentioned URL – http://server03:1111/.

Tags: c s, Create Web Application and Site Collections in MOSS, Learn SharePoint Server, MOSS, MOSS 2007 development, MOSS Site Collection, MOSS Web Applications, SharePoint Administration, SharePoint code, Sharepoint Server, Site Collections in MOSS, Site Collections in SharePoint Server, Web Application in MOSS, Web Application in SharePoint Server
Posted in .Net Development, C# Development, Microsoft SharePoint Server | No Comments »

Blogroll

Posts Tagged ‘SharePoint Administration’

MOSS9 / Creating Publishing Content Types

MOSS8 / Create Site Columns in SharePoint Server

MOSS4 / Create Minimal Master Page for SharePoint

MOSS3 / Creating Themes / Skins / Templates

MOSS2/Working with Web Application and Site Collection

MOSS1 – Create Web Application and Site Collections

QUICK QUOTE

CLIENT SPEAKS

Serach

Categories

Archives

Blogroll