Over here in the skunk works division of our company… we’ve been busy the past few months working on some prototypes that will allow us to integrate physical data with the usefulness of SharePoint.
This one is for my own reference so I can find it later…a really useful one-page list of common tasks when writing mocks for unit testing and an accompanying line of sample code to do it with TypeMock Isolator: http://www.typemock.com/files/CSharp_API_for_Isolator.pdf. It’s not SharePoint-specific, but quite useful nonetheless.
I noticed an odd thing while working with some JavaScript and Custom Actions in SharePoint 2010…the URL tokens (“~site”, “~sitecollection”, etc.) appear to be case sensitive when used in a ScriptBlock attribute (lower-case works, mixed-case does not) but NOT case sensitive when used in the ScriptSrc attribute. In other words, “~sitecollection” works in either, but “~SiteCollection” only works in ScriptSrc, not ScriptBlock.
I’ll be delivering a FREE webinar for Critical Path Training next Thursday, June 14. The topic will be the Developer’s Approach to Search Applications. Space is limited, but be sure to register since they will be sending a link to the recording to everyone who registers for the webinar.
Last night at the final @TSSSPUG meeting of 2011, Michael Mukalian and I presented an informal couple of sessions covering various tips that we’ve learned over the years of beating our heads against the SharePoint wall. Here’s a quick review of what I covered…
CKS:API is still moving along. It’s a little behind schedule due to work constraints. Two new developers have joined the project and I’m looking forward to some additional eyeballs on the code to help tighten it up. I’m also looking into Aspect-Oriented Programming (AOP) to overcome one of the big hurdles in CKS:API – littering all of that logging code throughout your codebase. I’m hoping that AOP will work as advertised (I’m using PostSharp, which seems to be the standard for AOP in .Net) and if it does, then parts of CKS:API will be refactored to make this an option. PostSharp has a free “community” edition so it won’t necessarily shut anyone out. You’ll still have the option of manually inserting the logging code on your own, so this is not a show-stopper requirement for using CKS:API if we do go that way.
This year’s SharePoint Conference was probably one of the most interesting conferences that Microsoft has hosted in the past few years. The attendance was solid and presentations covered the spectrum from 101 fundamentals over all the way over to nitty-gritty details.
In an earlier post, I briefly touched on the value of creating your own InsertWebPartIntoWikiPage method. Part 1 – solved. Now comes Part 2 – where am I injecting my web part?
Before I begin my rant, let me qualify this by saying this only applies if you are building an *application* on top of SharePoint. If you’re just using it largely out of the box for simple collaboration and content storage then this post likely doesn’t apply to you. If you’re pushing things a bit and using SharePoint as an application framework, read on…
