SharePoint 2013 Project Templates for Visual Studio 2012

While working with the SharePoint 2013 technical preview and Visual Studio 2012 RC, you may find yourself actually want to build some stuff. You install Visual Studio 2012 RC and then install SharePoint 2013, and expect there to be some relevant project templates available for you to develop against. Too bad, no SharePoint’y templates:

You will need to grab the SharePoint and Office project templates here:

Make sure to select the download appropriate to your Visual Studio 2012 version:

But.. after installing this you just get SharePoint 2010 templates..

You’ll need to now install the Web Platform Installer 4.0 (
After installation , Open it and search for “office”:

Select the “Microsoft Office Developer Tools for Visual Studio 2012 RC” from the search result.
Add and install the selected component. During installation, it will install other supporting components also.

After installation, Install SharePoint Server 2013 Client Components SDK from the following location:
You are now done and SharePoint 2013 project template should be available in the VS 2012:

Phew! That was a lot of work. Looks like Visual Studio 2012 is out in release as I write this, so here’s hoping the SharePoint jazz we need is already baked into that one.

Incoming search terms:


Trackback from your site.

Keith Tuomi

Keith is SharePoint Consultant and problem solver with itgroove. He's been focused on Microsoft technologies as a Developer and Web Applications specialist since the beginning of the internet era in the early '90s, with formal training coming from the esteemed British Columbia Institute of Technology. He is a SharePoint MVP, which is a coveted Microsoft award for community contributions and technical excellence. Keith has wide array of international experience and is also adapt at translating your business needs into bits & bytes.

Comments (4)

  • John


    So i have done all this, and i am still unable to connect to the SP2013 instance locally.

    Got any pointers?


    • Keith Tuomi


      Hey John,

      Option 1
      This issue is very common when using Host Headers. Try adding your url to the Hosts file on your development server. The path is:
      Open the file using Notepad with Administrator rights add the IP and URL and then Visual Studio should connect to your SharePoint site.

      Option 2
      1. Add yourself as the shell admin
      $configDBName =
      $user = “domain\username”
      $db = Get-SPDatabase | Where-Object { $_.Name -eq $configDBName }
      Add-SPShellAdmin -Username $user -Database $db.ID

      2. Make sure you start Visual Studio as admin


  • Pradeep


    Thanks Keith
    Your blog helped me much.


Leave a comment

Recent Comments

  • Keith Tuomi

    Sure, this was the same question we were pondering in our internal corp infrastructure- can we consolidate these servers to maximize efficiency and resource usage? Since the official guidance is that yes, you could install Workflow Manager on a SharePoint server- I see no reason and have no evidence that it would not work for an OWA server as well.

    OWA is basically a pumped-up web application that’s sole purpose is to answer the phone on it’s web service. SharePoint is massively more complex with many more moving parts and dependencies – so logic stands that if you can make WFM work on the same box with SP, getting WFM to work on OWA should be even easier.

    I would suggest you give it a shot, monitor & test carefully, and let us know how it goes!

Follow me on Twitter

Office 365 Service Health

There is a problem - it appears you are using categories and no feeds have been put into those categories.

SharePoint & Office Patches

There is a problem - it appears you are using categories and no feeds have been put into those categories. Service Health

There is a problem - it appears you are using categories and no feeds have been put into those categories.