SharePointers

For months now, ever since seeing some glimpses of the integrated SharePoint functionality in VS2010 I've been salivating at the prospect of a cohesive SharePoint development experience that it promises. Check it out here on Channel 9. Although the really interesting stuff is going to come with the release of the VS 2010 Tools for SharePoint , I was very excited to see what SharePoint surprises were tucked inside of the Visual Studio 2010 Beta that was released this week on MSDN. When first choosing a SharePoint project template, nothing is available. This is because the default framework version selected is 4.0. Switching to version 3.5 yields the SharePoint 2007 Sequential and State Machine Workflow templates. Ultimately, attempting to create either of these projects failed. The folders were created in the file system, but there were no project, solution or workflow files to be seen. I'm looking forward to the beta 2 / RC!

A client of mine recently had an issue where he wanted to insert a direct link to a FileMaker Pro document (e.g. fmp://...) in SharePoint. Both the rich text and source editors were stripping out the link, making life even more miserable for my FileMaker Pro-dependent client. It turns out that SharePoint controls the list of allowed protocols in a static .js file, and not in Central Administration, as one might be inclined to assume. Here's the solution: Open Core.js in Program Files\Common Files\microsoft shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\INC Look for the line with the text "Hyperlink.arrAllowedProtocols" Add the necessary protocol to the list of protocols below Return to a web browser and press Ctrl + F5 to force a reload of cached javascript files Insert the previously outlawed protocol link to test