Series

I finally got sick of writing feature.xml after feature.xml and creating new GUIDs. These repetitive things as well as those that make me take my hands off the keyboard slow me down… and that drives me nuts. Over the last few months I’ve been polishing and tweaking some stuff I’ve been working on that I use on a day-to-day basis as a SharePoint developer that speed up my development. Finally, they are at a point where I want to share them for others to benefit from them as I have (and a few folks who’ve been kind enough to test and provide feedback).

Over the last few months I've been serving as a coordinators for the ngOfficeUIFabricproject where we are building directives for Angular 1.x for the Office UI Fabric controls. We have adopted some practices and patterns, most borrowed from other projects that have helped us in managing the project. This post is one of a few in a How We Do It series of posts to share some of our guidelines that may help others. Those contributing to the project are doing so on their own time. Anyone is welcome to contribute and not be saddled with the burden of a lot of rules. My goal has always been to put things in place that make it easy for new people to get involved, to make sure the management of the project and tedious stuff is stuff contributors don't have to worry about.

As someone who's spent a lot of time working with Node.js, I thought it would be helpful to have some reference posts that helped understand what it's like to develop with Node.js, so here they go.

I did a session at Microsoft’s SharePoint Conference 2011 on integrating Office365/SharePoint Online & Windows Azure. In building out the demo for that I ran into some challenges when I tried to have my custom Windows Azure solution talk to and interact with a hosted SharePoint 2010 site collection living in my Office 365 SharePoint Online space. I ran into a few challenging spots when I tried using any of the four remote data access techniques available to developers. This blog series will talk about some of these challenges and how to overcome them.

I've worked on a few books around SharePoint in the 2007 & 2010 release. My focus is typically around core SharePoint development and the entire Enterprise Content Management (ECM) space, specifically Web Content Management (WCM) going back to my Microsoft Content Management Server (MCMS) 2002 days. I entertained plans to work on a SharePoint 2010 ECM book but took a pass this time around due to various reasons.

Soon after I learned about the introduction of the Managed Metadata Service (MMS) in SharePoint 2010, I was thinking about how you could use it in Publishing (WCM) sites. One of the ops I saw as a big win was the ability to use it for navigation purposes. In this series, learn how you can use managed metadata to implement a metadata-based navigation in WCM sites.

In October 2010 I did a bunch of posts on SharePoint 2010 ribbon development... in an effort to make them easier to find (as with other reference posts), I've added a new quick links section in the left-margin of my blog. These all came from the work I did on a paper for MSDN on customizing the ribbon. Because MSDN papers shouldn't really have opinions in them (at least in my opinion), I uses these posts on my blog for that purpose.

Over the next few posts I want to talk about a few different things related to integrating SharePoint 2010 & Windows Azure. Some of it are just opinions, musings and rants while others are more technical.

In this series, learn about the library Breeze - an Entity Framework-like library for JavaScript. Learn how you can use it with SharePoint REST queries!

In the process of developing a Publishing site (aka: WCM site) in SharePoint 2007, I've been building a few utilities that have helped me in accomplishing my goal, and I've decided to share these. This page contains my custom STSADM.EXE commands I've written for Web Content Management (WCM) developers. I'll use this page to serve as my documentation, making available the latest build of my custom commands, etc.

This page contains links and resources specific to Web Content Management (WCM). WCM part of a larger Enterprise Content Management (ECM) strategy that's part of Microsoft Office SharePoint Server (MOSS) 2007. MOSS is built on top of Windows SharePoint Services (WSS) v3.

Like many people who get into Silverlight, I quickly caught the bug and enjoyed this technology that allowed me to create robust business applications in the client relatively quickly. Over the last year I spent some time talking about leveraging Silverlight and MVVM with SharePoint 2010 at a few user groups. One thing that surprised me was that many folks in these sessions were under the impression you couldn't use MVVM with SharePoint. It seemed the CSOM or OData/REST piece of the puzzle was confusing to some. Of course you can! In this series, I'm going to talk about a few things related to Silverlight, MVVM and SharePoint. In here I'll talk about a few different challenges I ran into and some techniques I've adopted.

In this series, we’ll tackle the classic five W’s and one H (5W1H) questions to give you the best 10,000 foot perspective on the SharePoint Framework as possible. Andrew Connell wrote this series in late 2020 to help people new to the SharePoint Framework get the answers to the most common and basic questions about the SharePoint Framework.

This four-part blog post series covers the challenges developers face trying to incorporate modern Angular apps in SharePoint Framework projects, two approaches to incorporating Angular projects in SPFx project, and finishes off with the 'good, bad & the ugly' review.

This is a collection of articles related to Microsoft's VirtualPC & Hyper-V virtualization products that i've written about.

In this series of posts, I explain and explore what's changed in SharePoint Server 2010 with respect to Web Content Management.