Microsoft Office SharePoint Virus Scan Engine API

check this link
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/spptsdk/html/tsovAntiVirusOverview_SV01081979.asp

Performance counter for sharepoint

Check this
http://www.15seconds.com/issue/050825.htm

How to stop the !New tag appearing when you add items to your SharePoint

stsadm.exe -o setproperty -pn days-to-show-new-icon -pv #Days -url [Your Virtual Server's URL]

refer http://support.microsoft.com/?id=825510

re-create the “Explorer View” for document library if u deleted it

To re-create the “Explorer View” the following was completed:

Take a copy of an existing WebFldr.aspx from another document library (which has explorer view) using frontpage and copy it to the Forms directory of the document library that had the “Explorer View” removed from it.
Edit the WebFldr.aspx file and make the following changes:
Around line 99 or 100
{C00DF4E5-0547-4EA0-900B-09921313BAAA}
The number appearing in braces after ListView”> must be changed to reflect the same number as the listview from the broken sites AllItems.aspx

<View Name="{46A0A6CC-F0FB-45AC-9DCB-94D8AE435B19}" Type="HTML" ReadOnly="TRUE" DisplayName="Explorer View" Url="Shared Documents/Forms/WebFldr.aspx" … (remainder of line truncated)
The numeric in this View Name=”()” needs to be unique and also replicated towards the top of the file (see next line)

Around line 75 or 76


Items in bold must match.

Ensure that the following line is modified to point to the correct Document library (as this will still contain the previous locations details):
http://xx_sitename/xx_foldername/xx_sub_folder/Shared Documents/Forms/AllItems.aspx

Save the WebFldr.aspx file go back to the site and reload it.
Should result in a nice new “Explorer View” link appearing where it should have been.

I realize this may be a simplistic way of doing this, but I am certainly no expert and this was easy enough to figure out.

How To Integrate an Existing Windows SharePoint Services Installation with SharePoint Portal Server 2003

check the below link
http://support.microsoft.com/?id=824877

Managing External Content in Microsoft Office SharePoint Portal Server 2003

check this link
http://www.microsoft.com/technet/prodtechnol/sppt/reskit/c2261881x.mspx

Sharepoint Reporting Services tool pack

Check this link

http://www.microsoft.com/downloads/details.aspx?FamilyID=03607516-cbec-4724-b4a4-aa7f09304ba5&displaylang=en

office webparts for sharepoint

http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=38BE67A5-2056-46A1-84B1-337FFB549C5C

Sharepoint Content sources

check this link
http://www.msd2d.com/msd2dsitemap2.htm

Live communication Webparts for SPS

Some interesting Live Meeting integration stuff

Download details: Live Meeting 2003 Add-In for IBM Lotus Notes
http://www.microsoft.com/downloads/details.aspx?FamilyID=daf521db-b4fb-4507-a844-c18fc17860d2&DisplayLang=en
Overview
With this Live Meeting Add-In, you can use IBM® Lotus Notes® to perform Live Meeting Web conferencing tasks, such as scheduling meetings without logging into the Conference Center. Using the Live Meeting Lotus Notes Add-In Pack, you can:
Schedule and enter a meeting in your personal place
Schedule future meetings for both Auditoriums and Web Meeting Places
Check seat availability
Display the Organize Meetings page directly from IBM Lotus Notes
Set up default preferences including text for your e-mail invitations


Download details: Live Meeting 2005 Web Parts
http://www.microsoft.com/downloads/details.aspx?FamilyID=06e51c3b-ee57-498b-823d-e5550ebc11b4&DisplayLang=en
Overview
The Live Meeting 2005 Web Parts integrate Live Meeting with Windows SharePoint Services and SharePoint Portal Server to aggregate information together within a single portal so that teams can interact more effectively.By integrating with Live Meeting Portal, users can seamlessly view their upcoming Live Meetings or recently made recordings without having to log-in or remember any passwords. Not only do the web parts provide a view into Live Meeting from SharePoint, but they also allow a user to conveniently publish meetings and recording into a shared event calendar, so that team members can interact more effectively by having everything in one place.


Download details: Live Meeting 2005 Add-in Pack
http://www.microsoft.com/downloads/details.aspx?FamilyID=d1984810-117a-45ff-bfec-2756c6111097&DisplayLang=en
Overview
The Live Meeting Add-In Pack consists of three distinct add-ins: the Live Meeting Add-in for Outlook, the Office Collaboration Add-in, and the Live Meeting add-in for Instant Messaging, each which offer unique features. Live Meeting Add-in for OutlookWith the Live Meeting Add-in for Outlook, you can:
Schedule a Live Meeting from Outlook
Identify individual meeting participants as attendees or presenters
Send separate invitations for attendees and for presenters
Specify default meeting options and override those defaults for specific meetings
Live Meeting Add-in for Office Collaboration
With the Office Collaboration Add-in, you can start a Meet Now meeting directly from Word, Excel, PowerPoint, Visio, or Project. The document appears in an application sharing session.
Live Meeting Add-in for Instant Messaging
If the recipient also has the Live Meeting Add-in Pack installed, you can start a Live Meeting from Windows Messenger or from MSN Messenger.

Recycle bin for sharepoint

Check the below links
http://www.sharepointexperts.com/software_undelete.htm
http://www.nintex.com/Product-SmartLibrary.aspx
http://msdn.microsoft.com/msdnmag/issues/05/02/RecycleBinforWSS/default.aspx

Integrating Documtum with SPS

check the link below
www.vorsite.com

Deleting Files from Document library

SPSite site = new SPSite("http://localhost");

SPWeb web = site.OpenWeb();



// get a collection of all sites that are under root

SPWebCollection webColl = site.AllWebs;



// iterate through all sites

for(int i=0;i< webColl.Count ;i++)

{

// get all lists for current site

SPListCollection listcoll = webColl[i].Lists;



//iterate through all lists

for(int j=0; j< listcoll.Count;j++)

{

// check if its a doc lib

if (listcoll[j].BaseTemplate == Microsoft.SharePoint.SPListTemplateType.DocumentLibrary)

{

// iterate thru all and delete

for(int k=0;k
{

listcoll[j].Items.Delete(k);

}



}

}

}

Templates for wss site

check this link for templates for wss sites
http://sharepoint.bilsimser.com/pages/templates.aspx

download the .stp
http://www.microsoft.com/technet/prodtechnol/sppt/wssapps/default.mspx

Applying Permissions to Lists in Areas

A nice feature of SharePoint Portal Server are areas. Think of an area as a mini-WSS site of it's own. You can create document libraries, custom lists, discussion threads, etc. all within an area. Items in the portal, including entire areas, have the added advantage over WSS sites of being able to use audience filtering and thereby only show content to those that it's aimed for (remember audience filtering is just what's presented, you still need to apply appropriate security to deny access to something to someone).

Security for areas is the same as you would apply security anywhere else in SharePoint. You can add new users, change permissions, etc. (although when you select the advanced permissions for an area you get more options like being able to apply stylesheets, browsing directories, etc.) One of the issues security in an area is that if you have say several document libraries in that area, the security is the same for all libraries.

When you select a list or document library (through the Manage Content option) in SPS, you'll see the typical interface like Change general settings, Delete this list, etc. What you won't see is the option that you see when you go into the settings in a list or library in a WSS site. Namely the Change permissions for this list option. When you apply permissions to an area (using the Manage Security option), you'll see the typical SharePoint interface to add users, etc. but no option to set permissions for a list or library. You can however still use a feature of SharePoint to apply individual permissions to a document library or list in the area, it just takes a little typing to get there.

If you hover over the Change permissions for this list option in a WSS site, you'll see a url similar to the following:

http://servername/sites/sitename/_layouts/1033/ShrOpt.aspx?obj={1234567A-BBBB-C999D9999999},list

This is the page where you can set permissions for a list or document library (for document libraries, the end of the url will say ",doclib" instead of ",list"). The page exists in a virtual directory that's available to any WSS site and... portal area! This same url format can be used for an individual document library or list at the portal. You just need to know the GUID (the 1234567A number above). To find this out:

Select Manage Content from there area where your document library or list lives in the portal
Select the document library or list from the ones available
Select Modify settings and columns for that list
Take a look at the url you've gone to. You'll see listedit.aspx?List={... The numbers between the {} characters is the GUID for that list. The easiest way to get from this page to the ShrOpt page is to change the URL from this:
http://servername/_layouts/1033/listedit.aspx?List={30BDBE4A-829A-4FD1-A237-D1D3D60EFF02}
to this:
http://servername/_layouts/1033/ShrOpt.aspx?obj={30BDBE4A-829A-4FD1-A237-D1D3D60EFF02},list
Now you'll be at the Change Permissions: Document Library (or list) page
Modify the permissions as you normally would, adding or removing users and setting up permissions.
These permissions will only be applied to the document library and not to the entire area so you can now create read-only areas

WSS Web Services Web Reference

WSS Web Services Web Reference
Administration Service http:///_vti_adm/admin.asmx
Alerts Service http:///_vti_bin/alerts.asmx
Document Workspace Service http:///_vti_bin/dws.asmx
Forms Service http:///_vti_bin/forms.asmx
Imaging Service http:///_vti_bin/imaging.asmx
List Data Retrieval Service http:///_vti_bin/dspsts.asmx
Lists Service http:///_vti_bin/lists.asmx
Meetings Service http:///_vti_bin/meetings.asmx
Permissions Service http:///_vti_bin/permissions.asmx
Site Data Service http:///_vti_bin/sitedata.asmx
Site Service http:///_vti_bin/sites.asmx
Users and Groups Service http:///_vti_bin/usergroup.asmx
Versions Service http:///_vti_bin/versions.asmx
Views Service http:///_vti_bin/views.asmx
Web Part Pages Service http:///_vti_bin/webpartpages.asmx
Webs Service http:///_vti_bin/webs.asmx

WSS Web Services Description
Administration Service This Web service provides administrative capabilities like creating a new top-level site, deleting a top-level site and getting the list of available languages.
Alerts Service Provides access to the list of active alerts and allows to delete active alerts.
Document Workspace Service This Web service is used to manage Document Workspace sites. It allows you to create new document workspaces, delete document workspaces, create new sub-folders, delete sub-folders, and so forth.
Forms Service Each list has forms associated which are used to display list items, create new list items, and update or delete existing list items. This Web service allows to get the collection of forms associated with a list and then get detailed information about each form.
Imaging Service SharePoint has picture libraries that users can use to manage pictures. This Web service allows to upload pictures, download pictures, create new folders, delete folders and pictures, and the like.
List Data Retrieval Service Allows you to run XPath like queries against a list.
Lists Service This Web service is used to work with lists and list data. You can obtain the collection of lists, add new lists, remove lists, add new list attachments, remove attachments, and so on.
Meetings Service This Web service is used to work with Meeting Workspaces. You can create a new Meeting workspace, remove an existing Meeting workspace, add new meetings, add new meetings using ICal files, and so forth.
Permissions Service Sites and lists have permissions assigned to them. This Web service is used to obtain the permissions assigned to a list or site, add new permissions, and update or removing existing permissions.
Site Data Service The Site Data Web service can be used to return meta-data about a site or list, get the collection of lists, get the attachments for a list item, get the collection of items in a list, and so on.
Site Service This Web service can be used to return the list of site templates. When you create a new site using the Administration Web service you need to specify the site template name to use that you can obtain through this Web service.
Users and Groups Service This Web service is used to work with users, site-groups and cross-site groups. You can add, update or remove users, site-groups, and cross-site groups. You can also add users or cross-site-groups to a site-group.
Versions Service Document Libraries and Picture Libraries can have versioning enabled, which stores a copy of every single file version. This Web service can be used to get the list of available versions, delete versions, and also restore a file version.
Views Service Lists have views associated that define what fields are shown, what filtering and sorting is applied, what grouping is applied, and so on. This Web service is used to work with list views. You can get the collection of views, add new views, remove views, update the Html code used to display a view, and the like.
Web Part Pages Service Web Parts are objects that you can place on Web part pages. This Web service is used to work with Web parts and Web part pages. You can get the list of Web parts on a page, you can add or remove Web parts, and so forth.
Webs Service This Web service is used to work with sites and sub-sites. You can get the list of list-templates, get meta-data about a sub-site, get the list of sub-sites, and so on.

Rendering a webpart inside another webpart

code for rendering a webpart inside another webpart

protected override void RenderWebPart(HtmlTextWriter output){ SPSite site = new SPSite(webSiteURL); SPList docLib = site.RootWeb.Lists[libraryName]; SPView view = docLib.DefaultView;
output.Write(view.RenderAsHtml());}

Option Strict Off on .NET web project

you can use the

Sample themes for ASP.Net 2.0

link for sample themes
http://www.dotnettreats.com/tools/Default.aspx
http://www.dotnettreats.com/SampleThemes/Default.aspx

Accessing Webpart Maintaince Page

Add ?contents=1 to the portal url this will navigate to the Webpart Maintaince Page

Site Usage Report in Sharepoint

To access the WSS Usage on Portal and areas and not on WSS sites. This is not exposed in SPS , but you can browse to the link directly.
/_layouts/1033/usageDetails.aspx">http:///_layouts/1033/usageDetails.aspx

Antivirus Softwares for Sharepoint

1.
Antigen for SharePoint
Company: Sybari Software, Inc.
Summary: Sybari’s Antigen for Microsoft Office SharePoint™ Portal Server 2003 and Windows® SharePoint Services is an antivirus and document-filtering solution specifically designed to meet the security needs of SharePoint administrators.Solution Type: Products: Microsoft Office SharePoint Portal Server 2003, Microsoft Exchange Server, Microsoft Windows SharePoint Services

2.
McAfee PortalShield for Microsoft SharePoint
Company: Network Associates
Summary: McAfee PortalShield provides comprehensive virus protection and content management for Microsoft SharePoint™ Portal Server 2001, SharePoint Portal Server 2003, and Windows® SharePoint Services. Solution Type: Products: Microsoft SharePoint Portal Server 2001

3.
PortalProtect for Microsoft SharePoint Portal Server
Company: Trend Micro, Inc.
Summary: Trend Micro PortalProtect provides comprehensive virus protection and content security for enterprise information portal (EIP) systems and their users. Designed for specific use with EIP systems built using Microsoft SharePoint™ Portal Server 2001, PortalProtect offers tight integration with the Microsoft virus scanning application programming interface (API) and other Microsoft technologies.Solution Type: Products: Microsoft SharePoint Portal Server 2001, Microsoft Exchange Server, Microsoft Windows XP TabletPC Edition

Rename a team site from http://portalname/sites/testsite to http://portalname/sites/teamsite.

Rename the subsites using Microsoft Office FrontPage 2003. To rename the root of a site, you have to request this from the server administrator and ask him or her to back up this site using STSADM, and then restore it back as whatever name you want, such as http://portalname/sites/teamsite.

Hosting ASP or ASP.NET pages in a SharePoint site

Active Server Pages (ASP) pages hosted in a SharePoint site go through the SharePoint Internet Server Application API (ISAPI) filter, which does not parse ASP. Therefore, you will only get the raw source of the file if you attempt to browse to it.
In contrast, you could set up an exclusion on your virtual server that is extended with Windows SharePoint Services and put your ASP pages in that exclusion. Then you can turn on the Internet Information Services (IIS) ASP filter and have it parse those pages.

Setting Max Webparts Per WebPartPage

Change the

in Web.Config file.

Share Point Farm Configuration Moving From Small To Large Farm

Backup your small farm using spsbackup.exe (you may also want to backup the databases themselves using Enterprise Manager as well, just in case)
Add each of the new servers to the farm (Install SharePoint, set the database connection to the existing database)
NOTE: At this state on the Add Components page you will have a warning saying you are not using all of your servers.
For the server which hosts all the roles, de-select all but the one role you wish it to keep
For each of the additional servers, select only one role for each. Make sure you have at least 2 servers with the Front-End Role, 2 servers with the search role and 1 server with the indexing role otherwise you will not have a supported topology and SharePoint may not function correctly. (you can have more servers of each role and still have a larger server farm, so long as you meet the minimum for a large server farm I listed above. Just make sure each server has ONLY one role).
Make sure you do not have a red error at the bottom of the page (I think this is on the Add Components page) which says your farm topology is not supported. It should report your farm status is fine.
Configure network load balancing on each of the Front Ends (you can refer to the SharePoint Resource Kit or other documentation for how to do this. If you need more info, let me know)
Restore your backup.

If you are OK with losing your Index Catalog and having to recreate all of your content sources and re-indexing them, then you can skip step 7 (I would still recommend making a backup before you start just in case.

Performance settings with Sharepoint

None of these are hard limits enforced by the system. They are guidelines for designing a server that has good overall performance.
Site collections (Database scope) 50,000 ... Total throughput degrades as the number of site collections increases. Web sites (Web site scope) 2,000 ... The interface for enumerating subsites of a given Web site does not perform well muchbeyond 2,000 subsites. Web sites (Site collection) 250,000 - You can create a very large total number of Web sites by nesting the subsites. For example, 100sites each with 1000 subsites is 100,100 Web sites. Documents (Folder scope) 2,000 ... The interfaces for enumerating documents in a folder do not perform well beyond a thousand entries. Documents (Library scope) 2 million ... You can create very large document libraries by nesting folders. Security principals (Web site scope) 2,000 ... The size of the access control list is limited to a few thousand security principals, in other words users and groups in the Web site. Users ( Web site scope) 2 million ... You can add millions of people to your Web site by using Microsoft Windows security groups to manage security instead of using individual users. Items (List scope) 2,000 ... The interface for enumerating list items does not perform well beyond a few thousand items. Web Parts (Page scope) 100 ... Pages with more than 100 Web Parts are slow to render. Web Part personalization (Page scope) 10,000 ... Pages with more than a few thousand user personalizations are slow to render. Lists (Web site scope) 2,000 ... The interface for enumerating lists and libraries in a Web site does not perform well beyond a few thousand entries.Document size (File scope) 50 MB ... The file save performance degrades as the file size grows. The default maximum is 50 MB. This maximum is enforced by the system, but you can change it to any value up to 2 GB (2047 MB) if you have applied Windows SharePoint Services Service Pack 1.

An asterisk (*) indicates a hard limit; no asterisk indicates a tested or supported limit.
Portal sites (full) - typically 2 ... maximum 15 * Portal sites (child) - typically 10 ... maximum 100 * Areas - typically 1,000 ... maximum 10,000 Best Bets - typically 1,000 ... maximum 25,000 Area depth - typically 5 ... maximum 20 * User profiles - typically 50,000 ... maximum 1,000,000 Audiences - typically 500 ... maximum 10,000 Audience memberships - typically 500,000 ... maximum 5,000,000 SSO credentials - typically 100,00 ... maximum 100,000 Search indexes - typically 3 ... maximum 32 Content sources -typically 25 ... maximum 250 Search scopes - typically 25 ... maximum 250 * Indexed documents per content index - typically 100,000 ... maximum 5,000,000 Indexed documents - typically 2,500,000 ... maximum 20,000,000 Thesaurus entries - typically 1,000 ... maximum 10,000 Alerts - typically 50,000 ... maximum 1,000,000 Team sites - typically 10,000 ... maximum 250,000 Personal sites - typically 10,000 ... maximum 250,000

Communication between Portlets and Sharepoint Webparts

The Java world has portal standards called WSRP (Web Services for Remote Portlets) and portlets. Major Java portals seem to support it. It allows you to write a portlet using web services and defines standards for local portal component behavior. Some of the most important vendors in the J2EE world like BEA and IBM provide supports for portlets in some prodicts like WebLogic Portal.

Portlet is basically an extension of servlet but with some fundamental differences like a web page can consist of mulitple portlets but can have only single servlet, portlets cannot do browser redirect but servlet can.

Portlet is a an extension of servlet, can write html output, can forward but within the same portlet context, access to HTTP objects like session, request, response, along with similar Portlet objects like session, request, response.

Portlet is a concept of Java/J2EE technology and Microsoft SharePoint is based on .NET technology. They are competitive for each other.

WSRP will allow remote portlet Web services to be implemented in a variety of ways, including Java/J2EE and Microsoft's .NET platform. If we use WSRP release local Portlet as Remote Portlet, we can use “WSRP Web Service Toolkit for SharePoint Products and Technologies” to enable developers to load them.

Displaying custom webparts in FrontPage

To display the custom webparts in FP
Your custom webpart should implement
IDesignTimeHtmlProvider interface provides design-time HTML for Web Form controls for use in Web development tools such as Microsoft FrontPage.

Check this example

using System;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.ComponentModel;
using System.Xml.Serialization;
using System.Runtime.InteropServices;
using Microsoft.SharePoint.WebPartPages;
using Microsoft.SharePoint.WebControls;
using Microsoft.SharePoint.Utilities;
namespace MyWebParts
{
[XmlRoot(Namespace = "MyNamespace")]
public class DesignTimeHTMLSample : Microsoft.SharePoint.WebPartPages.WebPart, IDesignTimeHtmlProvider
{
private string designTimeHtml = "This is the design-time HTML.";
private string runTimeHtml = "This is the run-time HTML.";

public string GetDesignTimeHtml()
{
return SPEncode.HtmlEncode(designTimeHtml);
}

protected override void RenderWebPart(HtmlTextWriter output)
{
output.Write(this.ReplaceTokens(runTimeHtml));
}
}
}