Creating a Web Part Page programmatically

Using Microsoft.SharePoint API is often not the most easy thing in the world. As an example adding a web part page programmatically is not an easy job - unless you're lucky and hit the right page on MSDN.

I have been trying to add a pages using the SPFolder.Files.Add(, SPTemplateFileType.StandardPage) - but the page was not added as a WebPartPage so I couldn't add web parts to the page in a proper manner.

It was not until I came across the NewWebPage method on MSDN that I managed to get the job done.

Explore SharePoint from F#

Check out this blog on how to explore SharePoint's object model from F#.

jQuery library for SharePoint services

Using AJAX and jQuery to retrieve data from SharePoint and present it to end-users in advanced end-user interfaces is certainly the way forward.Check out this library for more information. Looks quite promising and have done some tests.

Create a Wiki page programmatically

If you have ever tried to figure out how to create a web part page or  wiki page programmatically you'll find it very hard to find any information.

Microsoft MSDN doesn't have a lot of information.

Recently I came across this blog. So some information is out there - not much though.

Exformatics new logo

Working with beforeproperties and afterproperties

Great overview found in this blog.

Updating document field value in SPItemEventReceiver.ItemCheckingIn() event handler

I need to update a property on ItemCheckingIn and came across this blog. Lucky me.

I have tried method 6
     properties.AfterProperties.ChangedProperties["Field Internal Name"] = "New Value";

but I couldn't get it working.

"Field Internal Name" should be "vti_Field Internal Name". Microsoft purchased SharePoint from a company called something with VTI. Unfortunately this didn't work either.

This blog is also worth reading as it explains the sequence of events.

Exformatics og Post Danmark Datascanning er partnere

Læs mere her.

Writing to SharePoint Unified Log

Writing to Windows EventLog sometimes causes issues in SharePoint, especially if using NTLM security. In this situation you might have to allow anonymous write access to the Event log by adding information to a specific registry key (Google if you wish more info on the matter).

As an alternative you can write to SharePoint own log, Unified Log, as described here on msdn.

Btw - I wonder why people in other blogs copy the content from MSDN and place it on their own blogs. What's the idea? It doesn't add any value - it only created confusion as I tend to ask myself. What is the difference?

ItemCheckingIn and version number - MOSS SP2 behavior

Came across this blog when studying version numbering in MOSS. It's great not to be alone out here.

And in the blog it gets even better.

Creating a site-collection programmatically

How do you create a new root site programmatically in C# or VB.Net. Check out this blog for more information.

Office - There has been a network or file permission error

Some of our clients are occationally experiencing the following error in Office "There has been a network or file permission error".



It's hard to find an explanation for the issue but I found this blog quite interesting. Indexing services on Windows Vista could cause the problem.

Another great blog describes ways to solve it for Windows XP SP2 and Office 2007.

More on SharePoint 2010

Came across this blog on SharePoint 2010.

ItemAdded - setting values - Microsoft recommendation

If you wish to set property values in an ItemAdded event in SharePoint - you need to create a separate thread that sleeps 10 seconds and then set the value. SharePoint is obviously not a transactional system. Read more in this blog.

Disable property promotion/demotion

I've been looking for ways to enable/disable property promotion/demotion without luck. Finally I found someone who had worked with this - it works.

Creating a web service in F#

Check out this blog on how to create a web service leveraging Microsoft's functional programming language F#.

More on SharePoint 2010

Doing research on Microsoft SharePoint 2010 I came across various articles and I found this from Lars Fastrup quite useful. Brief and to the point.

SharePoint 2010

The MOSS acronym is going away as Office will be referred to as the client product only. Not certain I buy the reason for this. In fact I view Office as the whole lot - editing as well as storing and managing. But obviously Microsoft don't have the same view - or their customers don't.

Read the blog http://blogs.msdn.com/sharepoint/archive/2009/04/14/microsoft-sharepoint-14-is-now-microsoft-sharepoint-2010.aspx here.

MOSS Performance considerations

I just read this blog about performance considerations in MOSS 2007. Especially the section about SPList object is worth reading in detail.

Using the List.Items.Count should be avoided at any costs. It basically send a very complex and expensive SQL query, especially on large lists. If you need statistics use the List.ItemCount instead which uses the statistics information from SQL Server about the list to provide data. No absolutely correct though.

SharePoint Dispose Checker Tool

This tool is awesome - check it out.