March 30, 2010 - 09:22, by Steven Van de Craen
Categories: General, SharePoint 2010, SharePoint Server 2010, SPF 2010
BIWUG is organizing the first SharePoint Saturday in Belgium ever. It’s held in Hof Ter Elst, Edegem on the 8th of May 2010.
Topics include Visual Studio 2010 Tools, LINQ to SharePoint, Client Object Model, Sandbox solutions, Managed Metadata and WCF and REST in SharePoint.
I’ll be there presenting on Sandbox solutions, so feel free to drop in !
For more information and registration visit http://www.biwug.be.
March 18, 2010 - 15:28, by Steven Van de Craen
Categories: Search, MOSS 2007, Search Server 2008, SharePoint 2007
The Scope Item Count gives an approximate number of items matching the scope. However at one of my customers it showed only six items for their entire file share !?
There were no Crawl Rules and the Crawl Logs showed tens of thousands of successfully crawled items so what could be wrong ? I played with the scope rules (recreated them, inverse logic, etc) but no luck. I opened up Reflector on the Scope Count property to find that it is calculated through a Search Query. Then it hit me that the account I logged in to to perform Search Administration was a local account that didn’t have access to the file share, thus the Query for returning Scope Count would security trim those results for me.
I’d expect any SharePoint Administrator to get a correct count of items in the Scope so this seems like a minor design flaw to me.
March 17, 2010 - 13:11, by Steven Van de Craen
Categories: General
It took about a week to resolve the DNS issue but now this site is back online to provide you with the occasional posting on SharePoint, .NET, Silverlight and alike.
Regards,
Steven
March 10, 2010 - 20:13, by Steven Van de Craen
Categories: Content Types, InfoPath, MOSS 2007, Search Server 2008, SharePoint 2007, WSS 3.0
When you have multiple Form Content Types with each their respective form templates assigned to the same Form Library by some magic it will automatically save a new form in the correct Content Type. How it does this ?
The new form’s XML contains an InfoPath processing instruction with a “href” attribute set to the XSN template URL. At save time the Content Types configured in the Form Library are iterated and a match is made based on Template URL. If no match is found it will use the default Content Type.
Even works in code if you do a SPFileCollection.Add() so no need to specify the Content Type explicitly during saves !
It doesn’t seem to take Alternate Access Mappings into account so that’s a bit of a downer, but still powerful.
March 10, 2010 - 20:13, by Steven Van de Craen
Categories: .NET, MOSS 2007, Search Server 2008, SharePoint 2007, WSS 3.0
You can add pages to meeting workspaces through the User Interface (browser) and then you get the options to manage them. It is also possible to add pages through code, but there’s one catch you need to be aware of and that is the InstanceId of the meeting. This ID is used in meeting workspaces to distinguish content per instance of a recurring event. So each meeting instance has its own set of documents and list items througout each List or Library on the site.
Consider the following code:
string url = "http://moss/meeting1";
string newPageUrl = String.Empty;
using (SPSite site = new SPSite(url))
{
using (SPWeb web = site.OpenWeb())
{
SPMeeting meeting = SPMeeting.GetMeetingInformation(web);
meeting.AddPage(String.Format("Page {0}", DateTime.Now.ToString("HHmmss")), meeting.InstanceId, out newPageUrl);
}
}
By adding the page using the InstanceId of the current meeting workspace it will be added to a folder named after the InstanceId in the Pages library. This has the following effects (also applies to items in the other lists and libraries on the meeting workspace):
- the page cannot be managed through the UI (sorting, removal, etc)
- the page is visible only in a single meeting instance in case of recurring events
If you want to add a page regardless of instance you can provide a zero (0) to the instanceId parameter of the AddPage method and it will behave identical to pages added through UI.