New Edition of Beginning SharePoint Development

If you’ve seen me less the past couple of weeks, it’s not from lack of want to post, but rather from lack of time.

You see, I’ve been working on upgrading one of the most popular USP Journal issues to a second edition. The issue, Beginning SharePoint Development, deals with, well, what you’d want to learn if you’re starting out as a new SharePoint developer.

A while back, I wrote a blog post on why SharePoint versions and tools don’t matter, where I said that I don’t see a point in upgrading screenshots when the purpose of learning is to learn the fundamental topic. In other words, because the core technology changes very little between SharePoint versions after 2007, what you learn in SharePoint 2007 applies equally in SharePoint 2010 and 2013, and vice-versa, for the most part. Granted, the .NET Runtime is different in SharePoint 2013, but that’s a different story and not one specifically related to SharePoint development.

So, why write a new edition? Well, first of all, I’ve learned a lot and gained valuable experience over the past couple of years since I wrote the first edition. Second, some parts of the issue, for example SharePoint Designer workflows, are definitely different between the versions. Third, I wanted to focus on the mentality of development in addition to the techy stuff.

These three reasons alone, at least the first and last, are not related to version at all, but are enough to make me want to write a second edition. So, having decided that, I could strike two birds with one stone by taking the screenshots from SharePoint 2010. I even used Visual Studio 2010 to cover all the bases, although I’m still a fan of WSP Builder so I’ve used that for the exercises.

You can use any tool, though, or SharePoint version. I’ve included a report titled “What’s New for SharePoint 2010 Developers” that show you how to use the, in my opinion, horrible Visual Studio 2010 Tools for SharePoint.  In fact, to ensure that even if you want to have the screenshots and exercises in SharePoint 2007, the purchase includes the entire first edition of the issue, including all the 21 videos that show exercises, tips, and tricks.

So, if you’re starting out as a SharePoint developer, don’t hesitate but pick up your issue today. There’s a ton of content, including over seven hours of video, all available for $14.95 at


Found this article valuable? Want to show your appreciation? Here are some options:

a) Click on the banners anywhere on the site to visit my blog's sponsors. They are all hand-picked and are selected based on providing great products and services to the SharePoint community.

b) Donate Bitcoins! I love Bitcoins, and you can donate if you'd like by clicking the button below.

c) Spread the word! Below, you should find links to sharing this article on your favorite social media sites. I'm an attention junkie, so sharing is caring in my book!

Pin It

Microsoft: SharePoint 2013 Will Suck at Social – Get Something Else!

Of course, I’m blowing this slightly out of proportion, but really the message remains the same. Microsoft touts the next version of SharePoint as a breakthrough in social computing, but then turns around and say that they’re not really expecting to get it right and that you’ll need something else to really get social going. In fact, social in SharePoint 2013 won’t be good at all so you might as well just buy SharePoint 2010 now and then get the third-party add-ons that you’ll need to get anyway.

Oh, yeah, I forgot to tell you what I’m talking about.

Last week, I picked up on an article citing Jonathan Barrett, a Microsoft employee in Australia, in which the main message was that if you want to get going with social in SharePoint, you want to buy Newsgator (and thanks to Alex Machester for reminding me)

Mr. Barrett said, according to the article, “We do have basic social features in SharePoint; they will be improved in [SharePoint 15], but that will not be at the level of feature richness that Newsgator has.”

Further, he said “I would say as a customer don’t wait for Wave15, unless you’ve got a really slow social media strategy or unless you want to use some really baseline features, I would start going ahead with our platform and Newsgator on top”

Now, this was said at an event heavily influenced by Newsgator, but unless Mr. Barrett really has no idea what he’s talking about, it’s a great message from Redmond. As late as March this year, Jared Spataro was chatting about the virtues of SharePoint as a social platform, and although he did mention the importance of third-party vendors, it was pretty clear that the next version would be oh’ so great on its own.

Spataro’s message rhymes with the official marketing chit-chat we would expect to hear at this point, which is essentially “Yeah, what we said a couple of months ago regarding how great SharePoint 2010 is, well, that’s bollocks. What you really, really want is to get the next version, which is going to be amazing and come with small cute kittens”.

Speaking of which, I’m also anticipating Spataro’s 2015 chat on to be something like “Yeah, we know SharePoint 2013 social features suck, but just wait to see what’s coming in the next version”.

Hold on, did you just say ‘a great message from Redmond’?

Yes, I did, and thanks for picking up on that. You see, I think Microsoft is on the completely wrong track with social. SharePoint has a three year product cycle, and before that at least two years of development, and the companies need at least a year for upgrading. Essentially, what customers get when they open up their newly upgraded SharePoint site is what was current five to six years ago. That’s why, when we got ‘social in SharePoint 2010’ we essentially got a glorified RSS reader and an innovative idea of tagging content (you know, like we did back in 2003).

So, if Mr. Barrett is right, he may not be the most popular guy in Microsoft these days, but he’s also sending a very important message of good news: Microsoft realizes and publicly says that it sucks at social and that you need to get something else if you want anything but the basics.

If this can be the start of a trend in which SharePoint becomes a platform first and product last, then the focus should shift from selling licenses to providing a stable and viable platform for long-term evolution. Today, because of Microsoft’s focus on selling licenses for SharePoint, the product cycle has become a ‘run like hell for one year, speculate about what’s coming for one year, be a newbie like everyone else for one year’.

Want to learn more about my thoughts? Check out my article on why SharePoint Server isn’t ready for the enterprise.


Pin It