Richards blog

I came across this very useful post outlining the internal names used by SharePoint. http://blogs.msdn.com/b/michael_yeager/archive/2008/11/03/reference-list-for-internal-field-names.aspx

I was trying to write a LINQ query to mimic a string Contains value. The code seemed easier enough: use a lamba and use the same way you would in standard c# (x => x.Code.ToString().Contains("MySearchString"). No good. LINQ complained and I was stuck. One workaround is to use SqlFunctions.StringConvert to convert the field. So, my lamba became x=> SqlFunctions.StringConvert((double)e.Code).Contains("MySearchString")

Workflows are configured a little differently in SharePoint 2013 than they are in 2010. I tried to find a good resource to take me through the installation and the best one I found was at  harbar.net A brief summation of the steps are: 1. Download workflow manager 2. Download workflow client 3. Add a binding to new web (12290 for https / 12991 for http) 4. Register the Service 5. Make sure that the port (12290/12291) is allowed as an incoming rule in the firewall. The only problem I encountered while following the installation instructions (which are excellent) was the registration if the SPWorkflowService. I found the resolution to my problem on the  Microsoft site  - my Register-SPWorkflowService command needed a –AllowOAuthHttp flag at the end.

I tried to create a new MVC 4 project in Visual Studio 2012 and was greeted with the following message: Error: this template attempted to load component assembly 'NuGet.VisualStudio.Interop, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. For more information on this problem and how to enable this template, please see documentation on Customizing Project Templates. The fix is pretty simple - download and install the NuGet Package Manager from  http://visualstudiogallery.msdn.microsoft.com/27077b70-9dad-4c64-adcf-c7cf6bc9970c

I recently configured a site to authenticate through Forms Based Authentication. The problem with this authentication method is that managing the users and roles is quite a pain. However, I found a FBA Pack on CodePlex, which provides a magnificent management interface. Get it  here .

I recently configured Forms Based Authentication for my site but soon found that my beloved people picker was not finding the users that I added. The solution was to add the membership provider I used in my configuration to the PeoplePickerWildCards section of the web.config. In my case, the following entry resolved the problem: <add key="FBAMembershipProvider" value="%" />

There are a number of steps required in FBA configuration, but they are well documented in this post: http://donalconlon.wordpress.com/2010/02/23/configuring-forms-base-authentication-for-sharepoint-2010-using-iis7/