Developing SharePoint Server 2013 Core Solutions Jump Start – Free Class


  • SharePoint as a Developer Platform
  • Managing Custom Components
  • Working with SharePoint Objects using a Client Side Object Model
  • Developing SharePoint and Auto-hosted and Hosted SharePoint Apps
  • Developing Remote Hosted SharePoint Apps
  • Publishing and Distributing Apps
  • Automating Business Processes

Microsoft Office can remember your My Site… Why are you still asking?

Have you seen this pop up message and no matter how you answer it continues pop up?

Microsoft Office can remember your My Site to show it when opening and saving files. Do you want Office to remember this site (http://site/) Only select ‘yes’ if you trust this site.

It can be corrected by running an Office repair. I’ve seen some other posts about updating a registry key, but that approach might get you into trouble.

SharePoint 2010 – Save site as template missing

add the following to the root of your site…


SharePoint 2010 – Find out which site template was used to create a site

via powershell…

$web = get-spweb http://MyURL


Wizard style InfoPath forms?

I took a look around to see how people how people have been creating wizard style infopath forms. I found a ton of examples and a few that really stood out. Check them out…

Creating a Wizard-Style Browser-Enabled InfoPath Form

InfoPath 2010 – one form, multiple views

Codeplex – Microsoft Ajax Minifier

You can find a lot of promising projects on codeplex. I’m going to document as I try out these solutions.

Project Description: The Microsoft Ajax Minifier enables you to improve the performance of your web applications by reducing the size of your Cascading Style Sheet and JavaScript files.

Rating: Pass


My Thoughts: I’m not sure why the css and js files aren’t already minified in SharePoint, but with this tool you can get it done quickly. This is a simple tool to use and even allows you to un-minify your files so you can edit them. It is an extra step to minify your files, but you get the best possible performance when you do.

Codeplex – Image Resizer for Windows

You can find a lot of promising projects on codeplex. I’m going to document as I try out these solutions.

Project Description: Image Resizer for Windows is a utility that lets you resize one or more selected image files directly from Windows Explorer by right-clicking.

Rating: Pass


My Thoughts: This is a huge time saver. Getting images ready for SharePoint can be time consuming, but with this tool it’s easy.


Codeplex – Scrum Template for SharePoint

You can find a lot of promising projects on codeplex. I’m going to document as I try out these solutions.


Project Description: Scrum Template for SharePoint is a free open source scrum Agile Software Development tool, that helps Scrum teams to manage the backlog/stories/tasks in their sprint planning

Rating: Fail


My Thoughts: This looked like a useful way to track tasks even if you weren’t using the agile methodology. It would be a great visual representation of a task list. I was able to upload the sandboxed solution, but it fails when I try to add it to a page. It looks like a lot of other people had the same issue. I hope the project gets picked up and completed.

SharePoint Scrum Board



SharePoint 2010 Application Pools

I found a blog that describes the app pools created by default. Check it out here.

Details from the blog…

What are the Application Pools that SharePoint 2010 creates?      This has been the most common question. My previous post deliberately ignored one and also skimmed over some details as well. Once we’ve installed SharePoint, run the Configuration Wizard and the Farm Configuration Wizard, we will have six Applications Pools in addition to those on the machine already. These are detailed below.

  1. SharePoint Web Services Root Identity: LocalService       Status: Stopped
    This guy hosts the SharePoint Web Services IIS Web Site and is on every machine in the farm. This is the host web site for Service Applications, it is analogous to the old “Office Web Services”. Service Applications WCFs are hosted in here as Applications which can (and should) be run in a different Application Pool. Whilst the IIS Web Site is important for bindings and other configuration, it’s absolutely OK that this Application Pool is stopped. If you try and browse the site, you will get a 503.
  2. SharePoint Central Administration v4 Identity: SharePoint Farm Account       Status: Started
    This one is pretty straightforward. It’s responsible for Central Administration on the machines hosting it. It will include at least three applications (root, images, inc) plus an app for each Language Pack you have installed
  3. SharePoint Web Services System (which is named with a GUID)       Identity: SharePoint Farm Account       Status: Started
    This guy hosts the Topology Service Application, which is known as the Application Discovery and Load Balancer Service Application.
  4. SecurityTokenServiceApplicationPool (which is named with a GUID)       Identity: SharePoint Farm Account       Status: Started
    The guy hosts the Security Token Service Application, required internally even on a single server farm as well as for supporting inter-farm operations, and external Claims.
  5. SharePoint Web Services Default (which is named with a GUID)       Identity: SharePoint Services Account       Status: Started
    This is the big daddy. It hosts all the other Service Applications. You will have as many applications in here as you do service applications deployed unless you configure their hosting manually.
  6. SharePoint – 80        Identity: SharePoint Services Account       Status: Started
    This is the default application pool used to host end user Content Web Applications having used the Farm Configuration Wizard to get up and running quickly.

Should I stick with those, I should I do it “properly”?  It’s Beta – so yes, you should really, unless you are looking at “advanced” farm topology and other design aspects. If you are a developer, step away from the console! Also, be patient and wait for the real RTM guidance. But the bottom line is the first four are required. You don’t want to be fiddling about with them. The last two are what the Farm Configuration Wizard produces and in a real world deployment you would certainly not create the last one, and you would probably change up the service apps one as well.

What is up with the crazy GUIDs?     Horrible aren’t they! An IIS Application Pool can have but one unique identifier, it’s Name, for which uniqueness is enforced. It works perfectly. However SharePoint has decided to use GUIDs for this Name. Within Central Administration the Application Pools are displayed using a SharePoint only property – Name, which is actually a Display Name (e.g. SharePoint Web Services Default).

Moreover, the GUIDs used are, wait for it, yes – unique. These aren’t “well known GUIDs” like class ids. They will be different on every installation. It would appear the GUID love from SQL server has found it’s way into IIS thru the back door.

One hopes this will be changed in the future. In the meantime if you want to find out which App Pool in IIS is which App Pool in SharePoint (crazy I know!) without fiddling around in the Internet Services Manager, you can do so with the following PowerShell:

Get-SPIisWebServiceApplicationPool | select Id, Name

Not your average InfoPath 2010 form

I found this blog post that details a graphical way to use an infopath form.