Sharepoint (RSS)

Sharepoint Portal Server and Windows Sharepoint Services

MCMS integration into Sharepoint in Office 12

Andrew Connell points to an excellent post on the Sharepoint team blog here about how they decided to integrate the MCMS 2002 features and functionality onto the Sharepoint platform, giving birth to what's now called Web Content Management in Office 12.

If you currently work with MCMS 2002 now, you'll find some answers about migration and support for existing APIs in the new version.

Check it out here

WSS and Sharepoint Server Service Pack 2 - What's supported in each

MS have released a white paper describing what .Net Framework scenarios and enhanced features are supported for Service Pack 2 of both Windows Sharepoint Services and Sharepoint Portal Server.
In brief,

Windows SharePoint Services
with SP2
SharePoint Portal Server 2003
with SP2
Ability to run on Microsoft Windows Serverâ„¢ 64-bit versions Yes Yes
Use of Microsoft SQL Server 2005 Yes Yes
Improved extranet deployment options Yes Yes
Support for the Microsoft .NET Framework 2.0
Common Language Runtime (CLR) and ASP.NET 2.0
Yes No

Check it out Here

Best Practices - Developing MCMS and Sharepoint for the Future

With all the exciting new announcements at the PDC, the futures of both Sharepoint and MCMS have been confirmed. (were they ever in question?)

In line with this, we should all be ensuring that any development work we do will place us in the best possible position for doing an upgrade when the time comes.

Arpan has linked to a couple of MSDN whitepapers to help us out:

Designing Your MCMS 2002 Solution for Reusability 
Summary:  Use best-practice design recommendations for Microsoft Content Management Server 2002 applications and Web sites to help you create your site in a way that prepares it for future versions of MCMS technology.

Best Practices for Ensuring Application Reusability and Upgrade in Windows SharePoint Services
Summary: Revisit key Microsoft Windows SharePoint Services Software Development Kit (SDK) information to know best practices for writing code that will be optimally reusable when software updates, upgrades, or security updates are applied to a deployment.

(via Arpan)

There were several large announcements made at PDC that are very relevant to SharePoint and CMS customers. I'm personally super excited about this and to be part of this. Microsoft revealed Office "12" - client and servers and talked about our investment in ECM. This is great news for CMS and SharePoint customers that there is one integrated architecture for end-to-end document and content lifecyle.

Another huge announcement was the introduction of Windows Workflow Foundation - WinFX. http://www.msdn.microsoft.com/windowsvista/building/workflow/ Office "12" servers will build on this technology to provide some great workflow!

A lot of CMS and SharePoint customers and partners are wondering what they can do to better prepare for the next version of the technology. If you are a CMS customer, take a look at the newly published whitepaper at: http://msdn.microsoft.com/library/en-us/dnmscms02/html/CMSDesigningCMS2002Sol.asp.

If you are a SharePoint customer, make sure you follow guidelines published at: http://msdn.microsoft.com/library/en-us/odc_SP2003_ta/html/WSSSharePointCodeReuse.asp