Today Erik Swensson’s book Practical SharePoint 2010 Branding and Customization came to our company. I am looking forward to read it. It’s about time to see alternatives to Randy’s starters.

There are much info about standard permission levels in SharePoint. Here is my visualization for that. Just a little bit easier to find out the right permission level. Enjoy:

Full Control (FullMask)

Design

Contribute

Read

Limited Access

Restricted Reader

Manage Hierarchy

Approve

ViewListItems

x

x

x

x

x

x

AddListItems

x

x

x

x

EditListItems

x

x

x

x

DeleteListItems

x

x

x

x

ApproveItems

x

x

OpenItems

x

x

x

x

x

x

ViewVersions

x

x

x

x

x

DeleteVersions

x

x

x

x

CancelCheckout

x

x

x

ManagePersonalViews

x

x

x

x

ManageLists

x

x

ViewFormPages

x

x

x

x

x

x

Open

x

x

x

x

x

x

x

ViewPages

x

x

x

x

x

x

AddAndCustomizePages

x

x

ApplyThemeAndBorder

x

ApplyStyleSheets

x

ViewUsageData

x

CreateSSCSite

x

x

x

x

x

ManageSubWebs

x

CreateGroups

ManagePermissions

x

BrowseDirectories

x

x

x

x

BrowseUserInfo

x

x

x

x

x

x

AddDelPrivateWebParts

x

x

x

x

UpdatePersonalWebParts

x

x

x

x

ManageWeb

x

UseClientIntegration

To remove a protected OU, go to ADUC (Active Directory Users and Computers), select the domain and enable “Advanced Features” in View. When Advanced Features are enabled, just right click you OU go to Properties -> Object and uncheck “Protect against accidential deletion”. Disable Advanced Features after that. By the way. When Advanced Features are enabled you can even see the distinguished Name of objects directly in ADUC UI.

An alternative to store key-value paired properties in appSettings in web.config we can use Sharepoint_config database by creating our own SPPersistedObject.  First we have to create a class which inherits from SPPersistedObject and decorate its properties with [Persisted]:

namespace Takana.SharePoint
{
    public class Settings: SPPersistedObject
    {
        \[Persisted\]
        public string DbConString;
 
        public LinkCheckerPersistedSettings() { }
        public LinkCheckerPersistedSettings(string name, SPPersistedObject parent) : base(name, parent) { }
    }
}
```Then we must create such an object. Let's do it in Powershell:

if(-not(Get-PSSnapin | Where { $_.Name -eq “Microsoft.SharePoint.PowerShell”})) { Add-PSSnapin Microsoft.SharePoint.PowerShell }

Want to create some organizational structure in AD, I suppose it is specifically useful in a development environment, well the best solution is powershell then. Mastering Powershell by and Powershell.nu by Niklas Goude provide examples how to do this.

$domain = [ADSI]""
$ou = $domain.Create("organizationalUnit", "OU=Administration")
$ou.SetInfo()

Be sure you write “organizationalUnit” in lower case. Otherwise you’ll get “Exception calling “SetInfo” with “0” argument(s): “The specified directory service attribute or value does not exist” when you invoke $ou.setinfo(). If you want to create an OU under another OU, just create $domain and specify the location:

First we have to create a class for our timer job which inherits SPTimerJobDefinition, build it and deploy it.

public class TakanaTimer : SPJobDefinition
{
	public TakanaTimer(){}
	public TakanaTimer(string jobName, SPService service,
		SPServer server, SPJobLockType targetType)
		: base(jobName, service, server, targetType) { }

	public TakanaTimer(string jobName, SPWebApplication webapp)
		: base(jobName, webapp, null, SPJobLockType.ContentDatabase)
	{
		Title = jobName;
	}
	public override void Execute(Guid contentDbId)
	{
		Log.Info("Running Takana Timer");
	}
}

There is a powershell example for this, but it has not been updated since MOSS.

A Sharepoint Database can become big and have unused spaces. To shrink database go to CA-> Health Analyzer:

http://takana:1337/Lists/HealthReports/AllItems.aspx

See if there is a list item about unused space in db under the Availability. Click on Repair Automatically in the opened Modal Dialog:  

In LINQ 2 SP we work with a data context. By default a data context has the property ObjectTrackingEnabled = true. This property is crucial for all other operations in CRUD except Read. I performed a mini experiment. I created 20 000 items in my task list. Every seventh item contains “pärla”. Allright, here is what I found out:

2857 / 20 000 items

ObjectTrackingEnabled = true

While working with Active Directory within SharePoint we probably don’t need to specify the domain or the root container. We can the current values. Here is a simple method from a console application just to demonstrate:

internal static void GetDomain()
{
	var context = new DirectoryContext(DirectoryContextType.Domain);
	var domain = Domain.GetDomain(context);
	Console.WriteLine("Full domain:");
	Console.WriteLine(domain.Name); //takana.local
	Console.WriteLine();
	Console.WriteLine("root container");
	var parts = domain.Name.Split(new\[\] {"."}, StringSplitOptions.RemoveEmptyEntries);
	var dcParts = parts.Select(n => "dc=" + n).ToArray();
	var d = string.Join(",", dcParts); //dc=takana, dc=local
	Console.WriteLine(d);
}

First we get get the full domain, then we split and join them again.

[slideshare id=11031050&doc=sharepointhtml5-120113215236-phpapp02]   HTML5-and-CSS3-What-About-SharePoint.pdf (968 KB) by Kyle Schaefer