SharePoint has forsaken me, at least that’s what it feels like every 3 years or so when they release a new version. When it went from STS to WSS 2 it was “What, I can’t use the SQL DB directly any more?” Then came SP 2007 and, “What, I can’t make post release updates to my Site Definitions?” SP 2010: “I can’t develop on with Virtual PC anymore?”
Am I ranting here? Nope. I love it. I’ve been a SharePoint developer a long while now and each time I begin to get a little bored with the job, Microsoft introduces a new version of the product that upends the community. There are always new, exciting features and ‘features’ to learn, many of which are improvements .
Now SP 2013 is here and it’s awesome, so what’s moved my cheese this time around? Apps for SharePoint. I explained earlier why I think SharePoint Apps are critical and why I think they’ve killed Farm and Sandbox solutions (RIP SharePoint Features 2007-2010). So now I’m trying to create an SharePoint App for a common business scenario and I’m finding myself stuck rather early in the process.
I want to create a list template and deploy it as a SharePoint App. I want to be able to roll up content from multiple instances of my list, so all instances of my list must use a common content type. Creating a SharePoint App that includes my site columns, content type, list definition, and list instance is pretty straight forward, but here’s the big catch: I want instances of my list to live in right in the user’s site so the user can interact with it just like the OOTB lists they’ve added, including creating lookup fields. SharePoint Apps run in the application infrastructure, which is a separate site collection from the user’s site. Using all the simple methods in Visual Studio (Add Item) leaves a barrier between the user’s site and my list instance.
If When I figure this all out, I’ll turn it into a few step by step articles and maybe publish the final product to the store.
Oh, and Happy New Year!