Posts Tagged ‘SharePoint 2013’

After setting up my SharePoint 2013 Development Environment and creating a the simplest possible SharePoint-hosted “Hello World” application to test out my store and App Catalog settings, I was surprised and disappointed to find that my application, while successfully deployed, was missing all of the common SharePoint script and style resources.

As it turns out, the problem was that I did not create a Site Collection at the root level when I was running the initial setup. Thanks to Prem for the simple solution.


Here are some resources to help with setting up SharePoint 2013 development environments:

SharePoint 2013: Creating a Development Environment — a TechNet wiki with numerous topics related to setup and configuration, part of a larger Best Practices posting.

Setting up a SharePoint 2013 Development Environment 101 — a TechNet blog post with other helpful hints

SharePoint 2013 Development Environments — Matthew Bailey’s blog with lots of links to other posts and information about pre-configured virtual resources

Set up the development environment for SharePoint 2013 — an MSDN article with still more resources and guidelines

A very comprehensive outline

SharePoint Dragons

This blog post discusses the installation of a SharePoint Development Environment from A to Z. Over the years, creating one is becoming more and more complex and although this blog post is quite long, we can’t pretend to be complete. Because of this, there’s an accompanying TechNet Wiki page that will be updated and extended at:


First of all, you need to think of the hardware you require. Go for an i7 quad core processor, equivalent or higher. Also make sure you have at least 32 GB memory, since SharePoint 2013 dev machines require at least 24 GB of memory. Having a RAID 0 hard disk is also a good idea.


Our ideal set-up is this: Run Windows Server 2012 on Hyper-V on a Windows 8 machine. At a high level, you need to have access to the following software:
– Visual Studio 2012 Premium edition (or…

View original post 3,083 more words