SharePoint in 2010

Notice the title of this blog entry in SharePoint IN 2010, not SharePoint 2010, subtle huh?  OK I was spurred on to write this little missive, by reading Furuknaps latest blog entry here.  It’s a nice little entry and I thought I’d put my own spin on it as he raises some great points.  SharePoint is all the buzz at the moment, Microsoft are excited by it as it’s one of their biggest movers. Partners love it as it’s an easy sell, as people just seem to want it.  Users seem to like it as it’s pretty easy to use and they can play around with stuff themselves.  Developers love it … well they love it and er… they hate it then they love it … erm .. then they hate it almost on an hourly basis.  It’s almost as if SharePoint developers are on a kind of permanent SharePoint PMT and there is no let up.

So, should you consider learning SharePoint development and by this I mean learning SharePoint not just knocking up a WebPart or two?  Well as ever, it depends.  Personally I love it, yes there are days when I hate it, but some parts of SharePoint are just so damn cool it’s outrageous, those bits gang up IMHO to outweigh the bits that drive you barmy!  I’ve recently been putting together a framework for Custom Site Provisioning for the company I work for Ridgian. It’s really cool to be able to churn out websites at the drop of a button to your own specifications. 

Anyway I’m off topic here a bit.  Should you learn SharePoint development. I think yes. The reason?  From where I’m standing, you’re only going to see more and more of it spreading across a whole raft of other Microsoft Server Products.  It’s already sucking in Team Foundation Server and Project Server, I can see others in the future also getting in on the act.  I remember the late, great Patrick Tessigham in an interview I did with him for NxtGenUG saying that SharePoint is The Next Microsoft Developer Platform. At Ridgian we certainly see it as the next platform and even the current one whenever we can use it.  It provides nearly all of the plumbing any ASP.NET application requires.  You can add in just about any other functionality you want with relative ease.  It’s all scalable for most 80-90% of situations you will be running it in.  And it’s only going to get better.  What I’ve seen of 2010 is just the DBs as far as I’m concerned, we’ve an exciting 2010 ahead in the SharePoint world that is for sure …

And in reality it ain’t that hard.  As Bjorn points out, you do need to have a reasonable grasp of:

  • ASP.NET 2.0/.NET 3.5 onwards
  • Javascript/HTML/CSS
  • XML and XML Web Services

If you can’t knock up even basic code in each of these then go do those first then come back to SharePoint.  Going further, I’d recommend getting a good grasp in particular of MasterPages, CSS and ASCX Controls in ASP.NET if you’re remotely interested in customising the SharePoint Web Front End.

For Developer resources to help you I’d recommend:

Scott Hillier’s great book here, Microsoft SharePoint: Building Office 2007 Solutions in C# 2005 .

Bjorn Furuknaps great book here Building the SharePoint User Experience.

And in addition although it’s not a Developer Resource, for an overall view of SharePoint Architecture and Configuration, Bill English’s great (and thick!) book here MOSS 2007 Administrators Companion.

Have a Happy Christmas a great New Year!


Dave Mc



Bookmark and Share

About davemcmahon81
Software Developer & Architect, User Group Leader, Speaker, Writer, Blogger, Occasional Guitarist, Man-made Global Warming Sceptic, Climate Change Believer, General Optimist but most of all proud Husband and Dad ...

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: