Ever thought things on ASP.NET were a bit slow the first time accessing them? Many of you are aware that ASP.NET from a web admin perspective know that things have to recompile and things just aren't as fast the first time. In fact some times things are incredibly slow the first time and are incredibly slow. Ever had users say, for some odd reason some times when I hit my SharePoint site it takes 30 seconds to load, then after a refresh it goes sub second, even clearing their cache the page is fast. That's because it's not a user issue, its simply compiling, caching, etc... on the server after an IISReset or app pool reset or worker process cycle.


Joel Oleson's post is very very interesting:

Tip #1: Add Command Line Shortcut to "12 Hive"
Tip #2: Access STSADM.EXE From any Directory in a Command Prompt
Tip #3: Recycle Application Pools, not IIS

Read More

When you want your users to be able to create a mysite you might get the following error:

'Your personal site cannot be created because Self-Service Site Creation is not enabled. Contact your site administrator for more information.'

this is because default this feature is turned off. Administrator must explicitly turn this feature on in order to permit users to create a mysite.


Perform the following steps to enable self-service site creation:
1. Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.
2. On the Central Administration home page, on the top navigation bar, click the Application Management tab.
1. On the Application Management page, under the Application Security section, click the Self-service site management link.
2. On the Self-Service Site Management page, select http://MYSITE-2222/ from the Web Application drop-down list, if it is not already selected.
3. In the Enable Self-Service Site Creation section, select the On option and click OK. This enables users to create sites under the selected Web application.

problem solved.

There are several options:

For a whole site collection:
In 'Site Settings' click on 'Audit Settings' or navigate to http://xxxx/_layouts/auditsettings.aspx
Select the actions you want to audit.

For a particular document library:
In ' Document Library Settings' : 'Information management policy settings'
Click to create a local policy and select Auditing and actions

For a particular content type:
Just create a content type and click on 'Information management policy settings'
Click to create a local policy and select Auditing and actions

To view the Audit Log Reports you have to activate the Reporting feature :

Navigate to: http://xxxx/_layouts/ManageFeatures.aspx?scope=Site
Find Reporting and click on 'Activate' (if not activated)
Go to 'Site Settings' then you should see 'Audit log reports'.
You can click on the link and then you can select the report you would like to generate.

Part 1

To change Propertie fields that are not plain text fields there are some problems in addign specific data to these columns.

for example:
You want to add a user to the assigned to field from an item in a TaskList

This won't work!
oNewTask["Assigned To"] = "DOMAIN\\Tom.VanGaever";

Instead you should use

when you are in a WorkFlow you can use
m_selectItem = WorkflowProperties.Item;
newTask["Assigned To"] = m_selectedItem.Web.AllUsers["DOMAIN\\Tom.VanGaever"];

Otherwise use the SPWeb object of your sharepointsite
SPWeb oWebsite = collWebsites["Site_Name"];
newTask["Assigned To"] = oWebsite.AllUsers["DOMAIN\\Tom.VanGaever"];

Why?
A User field contains a string in the form ID;#User_Display_Name, where ID is the member ID of the associated user. The following example parses the value of an Assigned To field to return an SPUser object.

string strUserValue = oList["Assigned To"];
int intIndex = strUserValue.IndexOf(';');
int intID = Int32.Parse(strUserValue.Substring(0, intIndex));
SPUser oUser = oWebsite.SiteUsers.GetByID(intID);