This blog outlines some helpful tips for troubleshooting the “Sorry, this app is not supported on your server” error.

This post will show you a working example of how you can save a HyperLink column to a SharePoint List in SharePoint 2010 using the Javascript Client Object Model.

This post will quickly cover how to configure the spshortcuticon tag within your app.master page so that it resolves correctly.

So I’ve done a couple of SharePoint 2013 App Catalog set-ups in the past couple of weeks, and I’d like to just quickly review my steps and outline one particular issue I ran into.

This post is really about documenting a really trivial, and often blogged about, feature within SharePoint: adding custom actions to the Site Actions menu.

Why another post? Simply because, for me, the final solution to my particular problem involved the amalgamation of a couple different posts. Six months down the road, this becomes difficult to track down or recreate, so I like to document the entire experience, what worked, what didn’t. If anyone is not clear on a piece of it, let’s discuss in the comments.

Scenario: I’d like to add a custom action menu item to the Site Actions menu, positioned below the New Document Library link.

When clicking on links to documents within a SharePoint 2010 environment, users aren’t prompted for whether or not they want to open the documents in Read Only or Edit mode. Instead, the files are opened directly in Read Only mode. Attempting to save a document after making edits, will only result in an error that the document is a read only document. This can be confusing for users.

This post will outline how to get around this issue and what the potential options are.