It’s Official Now: SharePoint Server 2010

Finally, the official words from Microsoft: the new incarnation of SharePoint server product will be named “Microsoft SharePoint Server 2010”. The “Office” is dropped from the title (as “Portal” was dropped from SPS 2003) since many users associate it with client-side software. The bad side is that we won’t be using “MOSS” as a synonym any more. 🙁

The other news is that the first wave of new products is coming: Exchange Server 2010 is available in beta version now. We still have to wait for SharePoint 2010, though.

Well, it seems that the new version definitely won’t see the light this year. Let’s hope it won’t be too late in 2010.

More details:

Review: Five Ways SharePoint Can Save You Money

Microsoft released few months ago a business-oriented guide that explains how businesses can actually save money in these times of crisis using SharePoint.

The essence of the whitepaper is that you can either reduce the total cost of ownership (TCO) or increase the return on investment (ROI). SharePoint can help the company to achieve both objectives.

The actions that reduce TCO are:

  • Reduce IT costs and complexity
    • Use a single platform for your enterprise applications
    • Single license and support
  • Reduce development costs
    • Use out-of-the-box features to save time
    • Leverage your existing ASP.NET knowledge
  • Simplify management and training
    • Single interface for IT Administrators and Power Users

The actions that increase ROI are:

  • Improve employee productivity
    • Collaboration tools, Web 2.0, workflows, business forms
  • Enhance the effectiveness of sales and customer service
    • Aggregate the business information across the enterprise


Download the guide from Microsoft Download Center

Detecting a SharePoint Designer Workflow Association

In a recent project, I had to find out which of the workflows in the site collection were made with SharePoint Designer. I did a recursive code that checked in all SPList instances in every SPWeb for the following combination:

  • For each SPList.WorkflowAssociations
    • SPWorkflowAssociation.BaseTemplate == null
    • SPWorkflowAssociation.InternalName.Contains(“Xoml”)

I also checked to see if the workflow association was active (SPWorkflowAssociation.Enabled == true) because the previous versions of the SPD workflows are also stored as associations, but they are disabled.

I hope this little snippet can help you in similar cases. Have a nice coding!