Sometimes you are developing some serviced or administrative application for SharePoint and what to have feature on the level of Central Administration. Something like “SharePoint Administrative Toolkit”

Some Web sites may not be displayed correctly or work correctly in Windows Internet Explorer 8. There is a KB956197 on Microsoft site, explaining this problem.
This issue affects the MOSS sites to be rendered fine. The good thing of this that it’s very small fix to apply on the master page to have your SharePoint sites rendered correctly – you need to set the IE7 compatibility explicitly.
Just add the following code to the META section of your master.Page

SharePoint provides you two models for development – Web Services and API for object model. But very often developers are a bit confused about what to use and when.

SharePoint provides you two models for development – Web Services and API for object model. But very often developers are a bit confused about what to use and when.

The administrative way of getting SharePoint version is navigating to “Central Administration > Operations > Servers in Farm”. But what if you need to get version programmatically?!

There are several standard columns, like "Title" and etc, which can't be delete from lists.  The workaround for this in creating the custom content type list and hiding the "title" column there.

So, the only way to do this is via SharePoint API – Feature Receiver. Use the following code-snippet to do this:

To have Visual Studio Extensions for WSS 3.0 to be installed on Windows XP or Vista (but only with limited set of capabilities, such as creating a Web Part project) add the string registry entry at

SharePoint has predefined set of OOTB permissions level, such as: Full Control, Contributor, Designer, and etc. But those permissions not always provide you desired functionality – its either too wide or very narrow.

The most commons scenario of role customization you can meet is Design role in publishing sites. When you have an approval workflow and assigned specific user to “Design” role as approver you need to take into account that “Design” role has delete permissions.

So, what actually happens, sooner or later, is that your approver accidentaly deletes what he needs to approve :) It’s not what you expect from him.

The solution for this is to edit OOTB permissions for Designer roles and to prohibit “delete items” action, or create new role. And pay attention to roles you are using in production system just to avoid such cases.

When SharePoint creates a Web application the following actions happening behind the scene:

Web Ste:
Creates a unique entry in SharePoint configuration DB for the Web App and assign GUID to that entry; Create and configures a Web application in IIS; Creates a root folder to store the Web application pages and associated resources; Creates and configures an IIS application pool; Configures authentication protocol and encryption settings; Assign a Default alternate access mapping for the Web app; Creates the first content database for the Web application; Associate a search service with the Web application; Assign a name to the Web application that appears in the Web application list in SharePoint Central Administration; Assign general settings to the Web application, such as maximum file upload size and default time zone;
Site Collection:
Creates the top-level site based on a site definition; Sets general properties for the site, such as the site title and site owner;