WSS 3.0

Dealing with SPListItemVersion and his cousin SPFileVersion during SPFile or SPListItem copying

Vitendy — Sat, 03 Oct 2009 15:23:07 GMT

Since I spent so many hours on this, I figured I'll post this to remember...

When copying SPFiles from one doc library to another, a few things to keep in mind:

SPFileVersion will not let you get a reference to the SPFile (per MSDN) so don't do this: SPWeb.GetFile(SPFileVersion.Url) because SPFile.Item will be null
SPFileVersionCollection (SPFile.Versions) is not in sync with SPListItemVersionCollection. SPFile.Versions actually does NOT return the current version. So, iterate through all SPFileVersions and use SPFile.Versions.GetVersionFromLabel(SPListItemVersion.VersionLabel)
To keep the check in comments with each version, use the following method to add a file to the target library: SPList.RootFolder.Files.Add(url,bytes,true,SPFileVersion.CheckInComments,false)
Iterate through versions via a SortedDictionary by Created date property -- the goal is to use SPListItemVersion information to update the newly created SPFile meta data.
SPFile.Item.Update() will create a new version; UpdateOverwriteVersion() will not; use the latter with SPFileVersions; use the former when adding a new SPListItem, to set values and incremenet versions.
Upload the current version of SPFile outside the SPListItemVersions loop
Be mindful that SPListItemVersion returns Modified and Created values as non-local time, so convert it.

Consider disabling item events during copy.

A good reference:

http://www.k2distillery.com/2007/10/copy-version-history-with_5.html

SharePoint Timer Service and custom jobs

Vitaly — Wed, 29 Oct 2008 16:17:57 GMT

When deploying custom SPOneTimeSchedule job definitions sometimes the timer service (OWSTIMER.EXE) just sorta sits there. Your job definition is created, but isn't executed. It will most likely eventually run, but I have better things to do than sit around wait for it. Setting the time for the job in the past seems to move things along faster.

// Create new job
CustomJob MyJob = new CustomJob(Constants.JOB_NAME, webApp, properties.Definition.DisplayName);
MyJob.Title = Constants.JOB_TITLE;

// Set up the job to run once
MyJob.Schedule = new SPOneTimeSchedule(DateTime.Now.AddHours(-4));
MyJob.Update();

New Theme for WSS 3.0

Vitaly — Fri, 25 Jan 2008 22:17:33 GMT

Themes are a good way to visually differentiate and/or brand SharePoint sites. Here is how to install a new theme.

1. modify an existing theme

2. add preview image to 12\TEMPLATE\IMAGES

3. modify the SPTHEMES.XML file in 12\TEMPLATE\LAYOUTS\1033 folder.

4. IISRESET

References:

http://msdn2.microsoft.com/en-us/library/aa979310.aspx

DNN And SharePoint

Vitaly — Wed, 02 Jan 2008 10:34:30 GMT

About a year ago I've started to focus on two technologies to develop websites with. Dot Net Nuke and SharePoint. Both products are .Net based and Microsoft backed. At the end of this post are links to articles that do a good job comparing the two frameworks. Needless to say, as frameworks, these products vary greatly in the way you can accomplish your goals. Nevertheless, having the common thread of .Net makes them similiar in so many ways.

I'm excited to continue to explore (and amazed at) some of the powerful tools that each product provides out of the box. As a freelance developer I find myself constantly saving time (and building better websites) by discovering new modules for DNN (thanks to the dev. community) and the power behind lists in SharePoint.

The links:

http://msdn.microsoft.com/msdnmag/issues/07/12/EndBracket/

http://www.dotnetnuke.com/community/blogs/tabid/825/entryid/1653/default.aspx