In this series, we will explore what it takes to build and manage a custom service application in SharePoint 2010. The most attractive reason to me for building a service application is to logically bundle a set of services and/or capabilities provided by in-house and 3rd party applications and systems within the SharePoint infrastructure.
Code generating a Python web application with LLBLGen, SqlAlchemy and the Tornado Web Server
Validating and binding PeopleEditor and custom SharePoint Editor/Picker controls
Building a Web API in SharePoint 2010 with ServiceStack
Scripting your SQL database (using SMO and the command line)
Adding LLBLGen to the Dapper performance benchmark test project
Using Autofac in SharePoint 2010
Up till now in my SharePoint 2010 projects, I’ve been using the very nice SharePoint Service Locator implementation, from the patterns & practices group. This has been really useful, and works great. If you’re not familiar with the service locator pattern, you can read up on it here. Using this pattern, it’s easy to build a lightweight common library that you pass out to your team (or as is often the case “teams”) of developers without them having to mess around with the implementation of every interface..net, autofac, di, ioc, sharepoint
Extending Quartz.NET – A sequential plugin execution engine
LLBLGen Pro, Entity Framework 4.1, and the Repository Pattern
My name is Matt. I love lots of things, and one of these is coding. If you know me, shoot me an email and give me some suggestions on things to blog about :-). I’m looking forward to coding up some interesting projects and getting your feedback. I will also be keeping a list of my favorite books, favorite libraries and favorite tools up to date if you’re interested.