Add ServiceStack + SharePoint example
Create a starter template showing how to use ServiceStack + SharePoint together.
We are using SS with SP 2013 and it works great. By far the most time consuming part was getting a signed version of SS working so that alone will make it much easier.
Awesome, great to hear - thx for the feedback! Releasing signed-builds should improve the SP story too - sounds like you're the point of reference to talk about SP as well :).
Funny story is in my last job as a financial contractor where a whole team of WCF devs couldn't get WCF to work within an existing (old) IIS+SharePoint installation, only vanilla ASP.NET would work, so we ended up going with SS instead which as it was just based on standard ASP.NET IHttpHandler's, pretty much works everywhere.
Just another tale of the complexity of merging 2 tech behemoths products together - not even the same company can provide a working solution.
Matthew Cowan commented
A large client of mine is using ServiceStack extensively within their SharePoint environment now, so putting a vote in on this one, as this is already slated to be a paying client.
The way we have it working is to have the app host intelligently configure itself during application startup. We do this by providing an interface (that's backed by the SharePoint service locator) to the development teams so that they can work with the AppHost at startup (since most things are in the GAC, we don't do auto-discovery, we do discovery based on registered interface classes which we call at startup). While we use a custom service application and database, a regular database could be used, or even just web.config mods. A single feature to install ServiceStack generically for all web applications in the farm on all web front-ends, and then an extension to allow re-use of the ServiceStack infrastructure for new development efforts across product and development teams was key. Most of the actual ServiceStack setup in my experience followed the existing SS documentation for asp.net web forms out-of-the-box. What's awesome, is to be able to call services locally to your web (/<spweb_server_relative_url>/_layouts/api/myservice), keeping context to the SPWeb, which means using SPContext.Current.Web works just fine within the services, and SP authentication requirements can be fully respected natively. The SharePoint story with ServiceStack is AWESOME! I have no experience at the moment yet with SP 2013 and ServiceStack, but I'm sure more can be done there too. Almost every dev I've worked with that started working with the ServiceStack implementation within SharePoint raves about it's simplicity over the WCF alternative, especially the ease of registering a new service into their dev VM and incorporating services into their web parts and layout pages, etc... (click, deploy, done! :-) ).