Making Sense of the SharePoint World

Mar-72010

It's a Date!

MCj04260900000[1]SharePoint and Office 2010 to Launch on May 12th

On Friday, Arpan Shah announced the official debut date for Microsoft Office 2010 and, of course SharePoint 2010, on the Microsoft SharePoint Blog. In the same post, he mentioned that the RTM (Release to Manufacturing) will come a few weeks earlier, some time in April.

There are a lot of changes coming in the new versions, so there is also lots of planning to do. I know many of you are planning to move forward aggressively, while many of you will also be on older versions of SharePoint long into the future. Whichever path you choose, it might be helpful to keep the following in mind:

  • Your current stuff will still work, even once the new software comes out. You don't "need" to upgrade immediately.
  • SharePoint Server 2010 requires Windows Server 2008. It also requires that your entire stack, including both Windows Server and SQL Server, be 64-bit.
  • Although you will always get the best results when keeping both the Office client and SharePoint versions in sync, you will still get reasonable functionality with staged upgrades. (Look for information about just how the different version combinations interact soon.)
  • One exception to the previous statement is SharePoint Designer. SharePoint Designer 2007 will not work for SharePoint 2010 sites. Conversely, SharePoint Designer 2010 will not work with anything except SharePoint 2010 sites.
  • On the Office client side, even if you are using 64-bit Windows, you can still use the 32-bit Office. This is critical, because you cannot mix and match 32 and 64 bit versions of Office on the same system. Naturally, you can't use 64-bit Office on 32-bit Windows in any case.
  • No matter what version of SharePoint you are on, a failure to plan is a plan to fail. Think about how you want to use SharePoint in your company before you deploy it.

This is going to be an exciting Spring in the SharePoint world, and I can't wait to help you make sense of it!


Dec-282009

Looking Back on 2009

New Year TimeThe Obligatory Year-end Report

It is now the last week of December, and you know what that means. Lying in wait among the crumpled wrapping paper, danced-out sugarplums, and pine needles (not to mention the feathers and other "presents" from all those birds your true love gave to you) you'll find year-end wrap-ups from every corner imaginable.

This is mine. :) I'll get to the more general stuff in a moment, but there was one personal SharePoint-related thing that stood out for me in 2009, and that happened the very first day.

I Became a Published Author

While I (along with Asif and Bryan) did all of the work in 2008, my book Professional Microsoft Office SharePoint Designer 2007 was officially released by Wrox Press on January 1st of 2009 (December 31st, 2008 in some markets). I'm honored by the very positive reviews, and want to thank everyone who has purchased it.

Ironically, its importance is going to continue on into 2010, and possibly beyond. While SharePoint 2010 is top-of-mind for many people right now, the fact is that SharePoint 2007 is going to be around for a long time to come. But, SharePoint Designer 2010 cannot work with SharePoint 2007 sites, so SPD 2007 will still be needed if you want to customize older SharePoint sites. Since SPD is now a free download, there isn't much in the way of printed documentation, other than (you guessed it) third party books - like mine.

The Year of the "Community Conference"

One amazing thing that stood out about 2009 was the popularity of independent SharePoint-related conferences and seminars. I personally presented at two - the "Best Practices SharePoint Conference" in San Diego, and the "SharePoint Technology Conference" in Boston.

But the big trend was the emergence of the "SharePoint Saturday" mini-conferences. These are one-day, free to attend conferences, that are held all over the world. Here you will find breakout sessions by the very same experts that present at the larger venues, like Tech-Ed and the official Microsoft SharePoint Conference. Check out the SPS site, and plan to attend one of these events near you!

And, of course, no mention of the "Community Conference" would be complete without mentioning the "Conference Community" on Twitter. This is a bit less formal, but essentially you will find a play-by-play for almost every conference being happily tweeted by the attendees with hash tags like #SPC09, or #SPSINDY.

SharePoint 2010

Of course, the big news was the announcement of Office and SharePoint 2010, and the availability of the public beta. The official release is currently set for the "first half" of calendar 2010. As many articles have pointed out already, much has changed. There will probably still be some significant changes between now and the final release, though what they might be, nobody can say.

Other Significant Events

Some of the other SharePoint things that happened to me in 2009

  • I became Michael Gannotti's very first "Backseat Driver"
  • I was once again awarded as a Microsoft MVP for SharePoint Server
  • I autographed and gave away almost 500 copies of my book while working the Microsoft Technical Learning Center booth at Tech-Ed in Los Angeles

SharePoint, the Target

No post about SharePoint in 2009 would be complete without some mention of another buzzphrase that started appearing in 2009 - "SharePoint Killer". Almost every new application that had the slightest thing to do with collaboration or content management seemed to earn headlines of "Is X the Next SharePoint?" or "Y will make SharePoint Obsolete". From Google Sites to Google Wave. From Drupal, to Alfresco, to the classic DotNetNuke. Yet while each may have one area where it shines, none of them really has the versatility or power to match SharePoint, assuming they are even truly comparable.

Blog Highlights

For those of you new to my blog, here are some of the articles I wrote this year that you might find particularly interesting:

Looking Ahead

With the planned official release of SharePoint 2010, 2010 the year looks like it will be just as exciting as 2009. One thing that is very clear is that Microsoft is putting a lot more effort into the supporting infrastructure for SharePoint. From native support in Visual Studio, to online documentation, to partner training.

While people may have been shocked by SharePoint's meteoric rise, nobody is going to be surprised by its continuing momentum.


Dec-132009

SharePoint 2010 - Everything Old is New Again

image "You Must Un-learn what You Have Learned!"

The public beta of SharePoint 2010 has been out for a few weeks now. Many people are discovering and blogging about some of the great new features you're going to find. Yet there have also been some significant changes to existing features. These are things you may have been using every day in SharePoint 2007 and WSS 3.0, but which in SharePoint 2010 have moved or changed in ways could cause confusion to experienced users.

In this article I'm going to focus on changes the typical end-user would see. In future articles I'll talk about changes for site owners and administrators.

If it Ain't Broke…

SharePoint 2007 took a lot of heat for having certain "quirks" in its user interface design. For 2010, much as they did for the Office clients in 2007, Microsoft put a lot of R&D into what it would take to make SharePoint easier for typical users. This resulted in a lot of changes.

Human beings are creatures of habit. With certain notable exceptions, we don't much like change. Despite having worked through a non-intuitive learning curve, or sometimes because of it, we would rather keep doing things the way we are used to than learn new ways - even if those ways are better.

...Fix it Anyway

Only time will tell if the changes Microsoft made truly are for the better, but they've definitely been made. Let's start by looking at the basic team site page in SharePoint 2010 side by side with its SharePoint 2007 equivalent:

image

image

At first glance, they're pretty similar. The WSS logo has been replaced with a "real" picture, but there's still a banner, title area, quick launch, and content space. But look a little closer. The Site Actions menu has moved. No big deal there - lots of custom master pages move that around. But, the new placement is comparable to the Backstage/File menu in the new Office 2010 client applications, thus making it a "natural" place for users to look for "application"(site)-wide functions. This analogy becomes even more obvious when some of the other tabbed interface options start showing up. (You'll see that later in the article.)

Where's MySite?

Another subtle change is the "personal" section of the banner. In SharePoint 2007, you had separate entries for User ID, links, and a direct link to your "My" site.

image

All of these options are now accessed through the menu under your name. There is also no reference to My "Site", rather it simply calls it your "Profile".

image

I think the hope here, is that by de-emphasizing the "independent site" aspect of the profile and personal storage, while actually expanding its function (the new profile features could fill up several articles on their own), resistance to deployment in certain enterprises would be reduced.

Bread-Crumbling Navigation

Getting around from site to site, and from place to place within a site, has received a LOT of attention in SharePoint 2010. In many cases, this has meant "reimagining" the concept of a breadcrumb.

In the case of 2007 site navigation, a breadcrumb stretched across the top of the page content area:

image

For large site hierarchies, this could become unwieldy as it stretched across the page. For 2010, Microsoft replaced it with a folder icon in the tab banner, which produces an indented hierarchical view of your current location:

image

Going the other direction, in SharePoint 2007 lists and libraries selecting a view was accomplished by selecting it from a drop-down list on the toolbar.

image

In SharePoint 2010, there is no list toolbar. While you can drill into the ribbon and find the view settings, then select your view, that's a lot of clicking. Fortunately, Microsoft has turned the title panel into an in-site breadcrumb. When looking at a list or library, the last item in that breadcrumb is the name of the current view. If you look carefully, you'll notice that there is a "down triangle" arrow. That's your hint that this element is actually a dropdown menu, where you'll find all of your view selecting goodness.

image

Tied up with a Ribbon

Of course, the rest of the stuff that used to live on a list or library's toolbar:

image 

has been moved into the Library tab of the new ribbon interface:

image

By the same token, individual items that lived in an individual item's dropdown:

image

have been moved into the Documents (or other appropriate item's) tab:

image

Note: In this case, the individual item dropdown is still there as well.

Summary

Some folks say, "The more things change, the more they stay the same". There have been a lot of changes in SharePoint 2010. While there are some things that have stayed the same, they are actually in the minority. In this article, I have gone over some of the many changes to "carry over" functionality you will find when moving from SharePoint 2007 to SharePoint 2010. There are many more than I could hope to address in a single posting. I hope, however, that this article has given you some ideas of where to look if you can't find your favorite function where it used to be.


Oct-272009

SharePoint 2010 Hits the Jackpot

MCj02345130000[1]

SharePoint Conference 2009 Wrap-up

The show is over, but the adventure is only beginning. As stated before, SPC09 in Las Vegas was the coming out party for SharePoint 2010. While we will still have to wait a few weeks for stable bits to play with, over 7000 attendees came away with a treasure trove of knowledge and documentation.

In my previous installments, I talked about the venue, the atmosphere, and the keynotes. I've also touched on some of the new Office integration story.

Of course, the star of the show was SharePoint 2010 itself. So, I'm going to dedicate the rest of this post to a punch-list of changes/improvements. I know I've missed a few (or more than a few) new elements, or misunderstood a detail or two, but even so the list is impressive. You'll see that the SharePoint team at Microsoft have not been resting on their laurels during the three years we've been waiting. Over the next few months, I'll fill in more details on the individual features, correct what I got wrong, or update you on the inevitable feature changes as things get closer to release.

The Basics

It seems Microsoft can't release a new version of SharePoint without tweaking the names a bit. Just as "SharePoint Portal Server" and "SharePoint Team Services" became "Microsoft Office SharePoint Server (MOSS)" and "Windows SharePoint Services (WSS)" in the 2007/3.0 wave, For 2010/4.0, they're simply called "SharePoint Server" and "SharePoint Foundation" respectively.

The Public Beta of SharePoint 2010 is to be released in November 2009.

The actual product release is planned for the first half of 2010.

It is still "SharePoint". Although many weaknesses have been addressed, core functionality remains essentially similar, with lists, libraries, site model, etc... Since "form follows function", many of the visual elements will be very familiar.

Infrastructure and Administration

  • Requires 64bit throughout the stack
  • Windows Server 2008 as a baseline OS
  • Complete redesign of Central Admin
  • Shared Services: No more monolithic "Shared Services Provider". Instead things formerly grouped under an SSP are individual Shared Service Applications.
  • Search architecture changes: index role can be spread across multiple servers
  • "Normal" SharePoint search now scale-tested to around 100 million items.
  • Business Data Catalog transformed into Business Connectivity Services, and becomes part of SharePoint Foundation (no more enterprise CAL required).
  • BCS info becomes available throughout the Office 2010 suite, not just SharePoint, and offers read/write capability.
  • FAST Search is available as an add-on for Enterprise CAL users at per-server pricing.
  • Enterprise-wide metadata support
  • Lists are more scalable, and can be "external" to the SharePoint content database. Admin can set maximum returned items to prevent bogging the system down.
  • Servers can be upgraded without enabling the new UI by default. Site owners can then switch over when their members are ready for the change.
  • AD Group Policies can prevent installation of SharePoint on unapproved systems.
  • Even more databases.
  • Better auditing and reporting in-box.
  • "License" logging to see which features are used.
  • Allowed to read log/report database to build custom reports.

Client Facing

  • UI: No IE6 support for collaboration/team sites. Can still make IE6 friendly publishing sites.
  • Firefox 3.x is a Level 1 browser.
  • "Accessible" CSS-based layouts, and XSLT-based list views.
  • Table-based layouts are gone
  • Cleaner, modernized themes.
  • Ribbons are primary control mechanism, just like Office.
  • There is no longer a separate basic "Wiki" site type in SharePoint Foundation. (However, there is now a publishing-based "Enterprise Wiki" site in SharePoint Server.)
  • All team sites can have wiki functionality enabled, and made the default.
  • Theme colors can be imported from PowerPoint themes for compliance with corporate standards.
  • The GroupBoard template is available out of the box.
  • List lookups can pull multiple fields
  • List lookups support referential integrity (blocking/cascading deletes)
  • Field validation

Social

  • Major overhaul of profiles and My Sites.
  • Includes "status" functionality (i.e. FaceBook/Twitter style updates)
  • Unique org-chart presentation
  • "Folksonomy" to support user-created shared tags in addition to Enterprise "Taxonomy" metadata.
  • Can tag non-SharePoint content

Search (Standard)

  • Improved handling of metadata
  • Faceting (now called "refinement") is built-in
  • Social input to ranking

Search (FAST)

  • All standard SP Search features
  • Deep refinement (polls entire result set to get actual counts)
  • Concept metadata from unstructured content
  • User-role tailored result sets.
  • Massive scalability
  • Superset of standard SP Search API
  • Managed through the same admin UI

SharePoint Designer 2010

  • Complete UI redesign, based on SharePoint "artifacts" rather than file structure.
  • SPD 2010 tied to SP 2010. Will not work on older versions or non-SharePoint sites, and old SPD won’t work against SP 2010 sites.
  • Much better Visual Studio integration – exports Solutions that can be imported into VS for both site designs and workflows.
  • SPD Workflows can be independent of specific lists.
  • SPD Workflows can easily be exported into either Visio 2010 or Visual Studio 2010
  • Finer administrative control over what SPD users can do.
  • Page model is the same, but many changes based on new CSS layouts and Theme engine.

Development

  • The "platform" aspect of SharePoint receives a lot of emphasis with this version
  • Use Visual Studio 2010 for full visual web part design and other SharePoint integration points
  • Can install SharePoint on a client OS (Vista or Windows 7, 64-bit) for dev sandbox.
  • Much better developer documentation out of the gate
  • Client Side object model to make Silverlight controls and web parts easier to develop.
  • REST, ATOM, and other web service interfaces fully supported.

Conclusion

In his keynote and his write-up from a couple weeks ago, Jeff Teper pointed out that the vision and purpose of SharePoint hasn't really changed much from the original 1-page proposal over 10 years ago. Yet the implementation of that vision has grown by leaps and bounds over the succeeding versions. I hope I have shown you that SharePoint 2010 will continue in that tradition. As I said earlier, I'm sure I've missed things. These were just the elements that stuck out as I was going through sessions and reading material. But I have to admit, I'm excited.