SharePoint team and Project server team at Maven Infosoft 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.
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.
<!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>
