In the first part of the SharePoint People Search – Lessons learned article we’ve discussed the basics of configuring SharePoint People Search. We have also looked at how it could be used for a facebook solution and what the shortcomings are. In this part we will explore different aspects you are very likely to face while creating a custom facebook solution based on SharePoint People Search.
SharePoint Dispose Checker Tool aka SPDisposeCheck is finally available! You can download it from MSDN Code Gallery @ .
While developing custom SharePoint solutions there is a big chance you need to look into the SharePoint SDK on regular. To keep off continuously surfing to the on-line reference, the SharePoint Team have provided us with the compiled CHM files. I admit that the off-line help files do simplify finding the information on a particular class, method or property. They have however two serious flaws: the content is outdated and there is no community content included in the off-line SDK.
If you delete a document in SharePoint 2007 using the User Interface, it’s being moved to the Recycle Bin, so that it can be restored if necessary. There are situations when you want to include deleting list items and documents in your custom solutions. The most commonly used approach I’ve seen is calling the SPListItem.Delete() method. While this does the job, and deletes the item, it deletes it permanently instead of moving to the Recycle Bin.
By default WSPBuilder builds solutions with the DeploymentTarget attribute set to GlobalAssemblyCache. All assemblies provisioned by the solution will be deployed to the Global Assembly Cache (GAC) of the target web server which might not always be desirable/doable. There are a couple of ways of how to change the DeploymentTarget to the bin directory of the target Web Application.