Review – Pro SharePoint 2010 Development

I was given the chance to review the Pro SharePoint 2010 Development book recently and I jumped at the opportunity.  I thought that the book for 2007 was critical reading, and with the new changes that come to the 2010 platform it is even more true of the updated book.

It does an excellent job of giving an overview of what is new with SharePoint 2010, what the development tools are (including SharePoint Designer), and how to work with each of the feature areas (Workflow/ECM/WCM/Social/Search/PerformancePoint/etc). Some developers may be critical about the book because it is fairly light on code (there is additional code available on the Wrox website), and there is no comprehensive resource on the API (always up to date and available on MSDN).  With the size and scope of SharePoint at this point it is very difficult to provide deep content on each of the subject areas.  Each topic area can and should be its own book.

Who This Book is Perfect For

I would highly recommend it for Solution Architects and Developers responsible for delivering a number of different types of solutions.  I know many very good SharePoint developers that can code a web part with their eyes closed, but have little understanding on how to take advantage of many of the other areas of the platform (Social, Search APIs).  I think this can be a great ongoing reference when those projects present themselves.

I would also recommend it to ASP.NET developers making the transition to SharePoint.  In the past, the resistance I have seen from ASP.NET developers has primarily been based on their lack of understanding about the platform as a whole.  This book provides an excellent foundation for that understanding. 

I would also recommend this book for IT Decision makers trying to create standards and methodologies around the different types of customizations that will be supported in the organization.  There is good content relating to SharePoint Designer and how to manage its use in the environment.

Who This Book May Not Be For

I would like to think that this book is perfect for any SharePoint developer, but if you can only buy one book and only want to develop one thing then this may not be the right book. 

SharePoint 2010 Migration versus Upgrade

No doubt there are hundreds of companies currently reviewing or planning the move to SharePoint 2010 from previous versions.  The excitement and business interest around the technology is very encouraging.  Before picking an “upgrade” path though, I would encourage teams to compare the Migration paths in addition to the normal Upgrade paths. 

Migration Path

Taking a Migration path means you are going to build a new farm or environment and then move content to it.  There are many advantages to this approach, here are some to consider. 

Restructure Information Architecture and Design – The migration path gives you the ability to learn from past mistakes or to make changes to better suit the current set of requirements.  This opportunity does not come up often, so if changes need to be made, this is a good time to enact those changes.  Changes may include restructuring the web application and site collection topology as well as Taxonomies.

Incremental Move – Since you are moving from one farm to another it does not have to be completed at all once, you have the option of breaking the content down into smaller units that can be moved one at a time.  This is especially valuable in cases where custom applications might have been built that cannot be upgraded without rework. 

Take Advantage of New Features – There are some situations where after an upgrade it may be difficult or at least require more work in order to take advantage of all of the new features.  One great example of this is the new Claims Based Authentication model.  In the past though, I have seen other issues which were traced back to compatibility issues with site definitions.  Given the fundamental changes to the Publishing features in 2010, I expect there to be issues when people take an Upgrade path. 

The Downsides – There are costs to taking this approach.  It may take more time than an in-place upgrade and it definitely takes more planning.  There may also be software costs for migration tools which can help automate a migration.

Upgrade Path

The upgrade paths may mean you are using the same hardware, or at the very least you are moving the Content Databases which keep the Applications and Site Collection topology intact.  The main advantages include:

Quicker and Easier – It should not take as much planning, nor take as long to complete. 

The Downsides – All of your existing Site Topology, Security, and general organization issues are moved to the new platform.  The system may be difficult to administer and maintain.

Choosing the Correct Path

Both paths have their pros and cons and offer unique opportunities.  The right path is the path that helps your team meet its objectives within the constraints given.  Most IT leaders push for the regular Upgrade path because it is less complicated within the scope of the short term project, but they do not have the full picture of what the opportunity cost is or what the long term impact will be.  It is implementation team’s responsibility to educate the decision makers as much as possible so that the best decision can be reached.

Related Posts

Event – SharePoint 2010 Personalization

I am excited to announce that I will be presenting one of my favorite topics at SharePoint Saturday Tampa on June 26th.  I’ll be presenting an overview and walk through of the personalization features in SharePoint 2010 including the MySites, User Profiles, Wall, Notes, Tagging and the Newsfeed. Using these features will make it easier to find relevant information and increase team collaboration.  I will also be covering some best practices on how to approach these features within your organization.

If you are in the area and interested in SharePoint, I highly recommend this event.  The extensive speaker list is very impressive so the content will be high quality and as always, the event is free to the public. 

Additional details can be found on the SharePoint Saturday Tampa website.

Registration is available here:

%d bloggers like this: