You could of course comment in and out (via ctrl + k, ctrl + c / ctrl + k, ctrl + u) the SPSchedule used by the timer-job during debug-mode. But this is error-prone.

When using a C# preprocessor directive you cannot forget to switch back to the “production schedule” as this is done automatically (and even with syntax-highlighting depending on the active configuration!) when selecting the “release build”.


#if (DEBUG)
var schedule = new SPMinuteSchedule();
schedule.BeginSecond = 1;
schedule.EndSecond = 59;
schedule.Interval = 5;
#else
var schedule = new SPDailySchedule();
schedule.BeginHour = 7;
schedule.EndHour = 7;
schedule.BeginMinute = 1;
schedule.EndMinute = 59;
#endif

This code tells the compiler to use the SPMinuteSchedule when compiling the “debug build” and to use the SPDailySchedule when compiling in “release build”. All automatically!

Object model?!

When looking into the SPFieldLookup-class you find the properties LookupField, LookupList and LookupWebId. LookupWebId and LookupField can easily be set via the object model. The documentation says that LookupList is read and writeable which is not true. Setting LookupList throws an exception stating out “Cannot change the lookup list of the lookup field.”.

SchemaXml and Regex to the rescue

The SchemaXml-property of a SPField can be used to manipulate the LookupList. One stumbling block is that you do not know the Guid of the LookupList currently stored in the schema. Even if you define a Guid inside your xml-field-definition SharePoint puts in an other Guid. Here a simple regular expression comes to help.

The code for connecting a site-column with a list somewhere in some web:

// Declarations (myWeb is the context given by a feature receiver scoped "web")
var rx = new Regex("List=\"([^\"]*)\"", RegexOptions.IgnoreCase | RegexOptions.ECMAScript);
var root = myWeb.Site.RootWeb;
 
// myListInstance is an instance of a SPList existing somewhere
var lookupField = (SPFieldLookup)root.Fields["MyLookupField"];
var xml = lookupField.SchemaXml;
xml = rx.Replace(xml, String.Format("List=\"{0}\"", myListInstance.ID.ToString("B")));
lookupField.SchemaXml = xml;
// Do not call update here!
// Quote from MSDN "Do not call the Update method when using the SchemaXml  property to modify a field."
 
// Fetch the field again and apply the web-id
var lookupFieldReFetch = (SPFieldLookup)root.Fields["MyLookupField"];
lookupFieldReFetch.LookupWebId = myWeb.ID;
lookupFieldReFetch.LookupField = "Title";
lookupFieldReFetch.Update(true);

This problem still persists in the beta of SharePoint 2010. I hope this will get fixed in the RTM. Creating a lookup-field-connection is far more easy by the way …

In a SharePoint project I’m working on it was necessary to get the default page of a publishing web in case where it differs from default.aspx.
 
In the environment the project takes place the “normal SharePoint user” is not allowed to use the SharePoint Designer. The page itself can be fully viewed by these users but the following code throws a SecurityException due to the missing “Remote interface”-permission.

// ... web is instantiated and disposed of course!
var pub = PublishingWeb.GetPublishingWeb(web);
var defaultPage = pub.DefaultPage;
 
// ....

In order to work in my projects environment this peace of code needs to be wrapped inside a resource-expensive SPSecurity.RunWithElevatedPrivileges-delegate. Makes absolutely no sense to me…

SharePoint 2010 has a lot of improvements for the “publishing infrastructure”. Lets hope this is fixed, too.

After I figured out why my first installation try went wrong I hit another strange issue.

When installing MOSS you have to choose which role your server is in. As I want to develop with BDC, Excel Services, Search Service I need to create a small farm (SQL Server running on the same machine in this case). But during the setup the “Complete Server Type” was missing!

Where are you my PDC?

I like development. So this installation took place on my home-machine which is not inside a domain.

A little while ago I installed MOSS successfully on Vista including the “complete role”. So one difference was the absence of a domain-controller …

Conclusion

After my machine became a member of a domain (and a reboot) the “Complete Server Type Role” became available during installation! SharePoint development on Windows 7 x64 is pure fun …

If you only want to display that field-value you can simply use the ControlMode-property and set it to Display. If you want to display only the date-part of that datetime just set the DateOnly-property to true…

Thats the theory. If you do it like that you get a nice Object reference not set to an instance of an object-error. The cause is

DateTimeField.set_DateOnly

Reflectoring the control reveals that when the control is in “DisplayMode” the inner DateTimeControl is not created and that is why DateOnly cannot be set.

Its seems this control was developed by a drunken programmer as my friend stated out a bug in this control a while ago.

The start is essential

I reconfigured everything, I checked the database-security, rebooted the virtual machine, re-created the content-sources. Nothing helped …

After some digging I found out that the start page of that site-collection (default.aspx) throws an exception due to a faulty web part…
This can’t be… Can it?! I removed the faulty web part from the default.aspx and the start page runs normal … and so does the crawler!

Because of an erroneous start page the whole crawling process for that site-collection is not working!

Conclusion

Make sure that the “entrance” to your site-collections is wide open and totally working …

PS: Excluding the default.aspx via “Crawl rules” does not work. The crawler still stops.

We do not support modifying a custom site definition or a custom area definition after you create a new site or a new portal area by using that site definition or area definition. Additionally, we do not support modifying the .xml files or the .aspx files in the custom site definition or in the custom area definition after you deploy the custom site definition or the custom area definition.

So site definitions are a one way ticket. All your requirements (even future ones) must be implemented before you actually create sites based on your site definition! This is far from “real life”.

This “supported and unsupported-link” is not referenced within the SDK (MOSS or WSS). The SDK describes the nice way of creating site definitions, how to deploy them e cetera. Once deployed your site definition has to be immutable! But this fact is not mentioned inside the SDK!
Even more confusion is spread when you want to lock down SharePoint Designer (which is now available for free) following Microsoft’s kb article filed under http://support.microsoft.com/kb/940958/en-us. If you read the article you will see that it suggests to modify the existing onet.xml files so that the changes also affects already provisioned sites.

Microsoft tells us that changing the site definition after sites have been provisioned with it is unsupported but on the other hand writes a kb article where site definitions should be modified to reflect changes to already provisioned sites! Another example of how difficult communication is!

Conclusion

SharePoint is a static environment when you rely on the “xml-ways” of customizing SharePoint. This issue also appears when using Content Types. Once a Content Type is deployed Microsoft “does not support” changes in the Content Type xml-definition.

What gets clear when reading the kb article (http://support.microsoft.com/kb/898631/en-us) is that changing/updating via code is always supported. Perhaps its time to move away from the xml-based declarative approach to the code-based approach.

Lets hope SharePoint 2010 will fix all these issues!

Disguise

Unfortunately the list where the pages reside is hidden to the UI. So the user has no option to check-in the created page. The only way to access the list is to retrieve the id of the “pages-list” (e.g. via SharePoint Manager). Now you can pass it to the ManageCheckedOutFiles.aspx inside the _layouts-folder. Alternatively you can connect via SharePoint Designer and uncheck the “hide in browser”-option.

Your url looks like this: http://myserver/myweb/_layouts/ManageCheckedOutFiles.aspx?List=%7B6F145CFF%2D8779%2D4D38%2D8B11%2D6B37EBA0A76C%7D

You are now able to “overtake” the checked-out page for yourself for further editing. But your odyssey is not yet over!

If you want to check-in the document you get an error. It’s simply not possible! What helps is:

1. Copy the affected page with SharePoint-Designer
   
2. Paste it into the “pages-list”
3. Delete the old checked-out page
4. Rename the pasted page to the old page name
5. Now your page is fully visible!

Prepare for the future

Because the pages-list does not have any views defined its hard to help users. If you have the list-id of this list you can use every management-page to customize this list (e.g. _layouts/listedit.aspx?List=%7B6F145CFF%2D8779%2D4D38%2D8B11%2D6B37EBA0A76C%7D).

Conclusion

I believe this is a bug. Perhaps there will be a fix. But don’t rely on it … What is really annoying is the fact that this list is a “special list” and you cannot add views to it. So if you ever get a page that does not show: use your SharePoint tools!-)

Update

The customer had a lot of workspaces where this has happened. This bug is really annoying! I have colored (yes that nice orange) the important part to fix this problem.

Error

Clicking through the installation wizard went fine but then the installation cancelled with “nice” red error icons. A look into the logfile showed the following.

Property(S): ACTION = INSTALL
MSI (s) (08:D0) [23:01:25:354]: Note: 1: 1708
MSI (s) (08:D0) [23:01:25:354]: Produkt: MSXML 6.0 Parser (KB933579) -- Die Installation ist fehlgeschlagen.
 
MSI (s) (08:D0) [23:01:25:354]: Das Produkt wurde durch Windows Installer installiert. Produktname: MSXML 6.0 Parser (KB933579). Produktversion: 6.10.1200.0. Produktsprache: 1031. Erfolg- bzw. Fehlerstatus der Installation: 1603.
 
MSI (s) (08:D0) [23:01:25:385]: Cleaning up uninstalled install packages, if any exist

I downloaded the MSXML 6.0 Parser from the Microsoft Download page and tried to install it. Error! A newer product is already installed. A short look into “Software Installation” revealed that I have MSXML Parser 6.0 SP2 installed. Okay looks good for me but not for SQL Server 2008.

Being up-to-date is not always good

The installation routine depends on the installation of the MSXML Parser 6.0… In the end I uninstalled MSXML Parser 6.0 SP2 and started the installation again. Tadaaaa! It works. SQL Server was installed successfully. Now I can “re-apply” SP2 for the MSXML Parser 6.0

Woohoo

I started the windows command-line and entered date. It showed 2009-01-28. As you can see the year is 2009!
Having to do such steps to get an installation of SQL Server 2008 made me think I am in the year 1998! Wtf?!

Update: A friend of mine had problems with SQL Server 2008 installation, too.

Flow of actions

Here is what I did…

	Enable ContentType-Management
	List-Overview with enabled ContentType-Management. The ContentType “Task” is attached to the list.
	Field overview of the ContentType inside the “Task-List”. The field Status is named “Status”.
	Properties of the Field of the ContentType “Task” inside the list. The StaticName of the field is “Status” as one can see inside the red ellipse.
	The fields available when navigating to the properties of the ContentType “Task” inside the “Site Content Type Gallery” of the site collection. Note: One can already see that the “Status-Column” is named “Task Status” here.
	If you navigate deeper into the field properties of the base ContentType “Task” you see (inside the red ellipse) that here the StaticName is “TaskStatus”.

Bug

This is definitely a bug. These StaticName properties of the fields should be the same! What is even more weird is the fact that the Id’s of the fields are identical! Both have a guid of “c15b34c3-ce7d-490a-b133-3f4de8801b76″!

If you look inside the schema.xml of the default task list (found in 12/Template/Features/TaskList/Tasks/schema.xml) you see that the StaticName is set to “Status”. If you take a look inside the ContentType-definitions of the sharepoint-core (found in 12/Templates/Features/ctypes/ctypeswss.xml) you will notice that the name of the field with the id “c15b34c3-ce7d-490a-b133-3f4de8801b76″ is set to “Status”, too.

So I cannot explain why the fields in the ContentType “Task” are prefixed with “Task”. The field DueDate is also affected. Inside lists its StaticName is “DueDate” inside the ContentType its named “TaskDueDate”.

Conclusion

It seems that you can’t even rely on the StaticName! Instead always make use of the Id of a field!