Useful links - old: SharePoint

{ SPWorkflow.CreateHistoryEvent(workflowProperties.Web, workflowProperties.WorkflowId, (int)SPWorkflowHistoryEventType.WorkflowComment, this.workflowProperties.OriginatorUser, new TimeSpan(1), Outcome, Description, OtherData);

}

http://www.sharepointbuzz.com/archive/2009/01/21/how-to-create-a-sharepoint-workflow-history-event.aspx

Thursday, January 14, 2010

"One or more field types are not installed properly. Go to the list settings page to delete these fields."

I received this error while using an SPQuery CAML query string. the problem was that I had renamed my Title column in the list to “Document Library Name” and in the SPQuery i was using

query.Query = "<Where><Eq><FieldRef Name='Document Library Name'/><Value Type='Text'>" + this.workflowProperties.List.Title + "</Value></Eq></Where>";

after some research I found out that the internal name of the column was still ‘Title’ so i used

query.Query = "<Where><Eq><FieldRef Name='Title'/><Value Type='Text'>" + this.workflowProperties.List.Title + "</Value></Eq></Where>";

and the error was gone :D

Wednesday, January 13, 2010

Access web.config from a Visual Studio WOrkflow

http://stackoverflow.com/questions/1592574/access-config-file-from-a-vs-sharepoint-workflow

Create a SharePoint feature in Visual Studio

http://code-journey.com/2009/03/25/how-to-create-a-new-feature-in-sharepoint-using-visual-studio/

Sharepoint feature receiver

http://www.nnihlen.com/blog/archive/2006/12/04/724.aspx

http://code-journey.com/2009/07/05/add-an-event-handler-feature-receiver-to-a-sharepoint-feature/

http://ivydotnet.spaces.live.com/blog/cns!F0ADF64956CA5930!291.entry

http://blog.tylerholmes.com/2008/03/walkthrough-creating-sharepoint-feature.html

http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/24f5e19c-4496-4f11-89be-2e24242a2e4e

http://dkeeling.spaces.live.com/blog/cns!1FF0B17B869C973!146.entry

Tuesday, January 12, 2010

‘Access denied’ when deploying VS 2k8 Sharepoint workflow

(I couldnt get a resolution to this error but following is a workaround)

1. Create a directory in the features directory [C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\TEMPLATE\FEATURES] and drop both the feature.xml and workflow.xml files into the directory.
2. Install the feature on your farm, using the following command line statements
stsadm -o installfeature -name <<name>>
4. Activate the feature to a site collection
stsadm -o activatefeature –name <<name>> -url <<url>>
Replace <<name>> and <<url>> with the actual value

http://www.codeproject.com/KB/WF/sharepointworkflow.aspx?msg=2656569

***EDIT: Strange enough, I added System.Configuration reference in the project for some other purpose; and this error was gone :D

Tuesday, November 24, 2009

Cannot Find SharePoint Site or SharePoint Server Instance

This problem can occur when the workflow deployment process cannot open the SharePoint site.

Error Messages

SharePoint Server not available.
Cannot find a SharePoint server instance.
Cannot find the specified SharePoint site: <site URL>.

Resolution

Ensure that SharePoint Server is running.
In the Properties window, ensure that the site specified in the Target Site field is a valid SharePoint site.
Examine the SharePoint diagnostic log files. The default location of these log files is drive:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS. If you cannot find the log files at this location, refer to the diagnostic logging settings in the SharePoint Central Administration Tool. For more information, see the documentation for Office SharePoint Server 2007.

http://msdn.microsoft.com/en-us/library/ee231594(VS.100).aspx