I’m in the process of digesting the wealth of information that is pouring from PDC 2008 that’s in progress right now. I was unable to participate but I’m monitoring the news and blogs of the attendees.
There’s one thing that caught my attention. On day one the new cloud services platform was announced under the name of Windows Azure.
What is Windows Azure?
As I understand, it’s a cloud-services platform that exposes storage and application services that are hosted in Microsoft datacenters. It allows .NET applications to run “in the cloud” (i.e. not on-site or on-premises) and to benefit from the distributed services that it offers.
What’s in there for SharePoint?
One of the services that you can see in the diagram above is “Microsoft SharePoint Services”. First thing that should be clear is that this is not “Windows SharePoint Services” (the free, basic SharePoint platform) nor “SharePoint Online” (Microsoft-hosted SharePoint farm). I think it’s SharePoint functionality exposed as services API. It can be seen that SharePoint Online uses these “services”.
Microsoft® SharePoint® Services & Dynamics® CRM Services (from Microsoft site)
In the future, developers will have access to SharePoint & CRM functionality for collaboration and building stronger customer relationships. With the flexibility to use familiar developer tools like Visual Studio, developers will be able to rapidly build applications that utilize SharePoint and CRM capabilities as developer services for their own applications. Developers can expect a breadth of SharePoint & CRM capabilities across the spectrum of on-premises, online & the Azure Services Platform.
So, it’s still not available (but it will be). I’ll keep a close watch on it, sure.
There are official news about SharePoint 2007 and WSS 3.0 Service Pack 2 (SP2) from Microsoft TechNet. The new service pack will contain:
- Improved Read-only Content Databases
- Improved performance and manageability in variations, including STSADM commands for repairing links between source and target pages
- Improved Index Rebuild Timer Jobs
- SP2 Upgrade Checker
This SP2 will become available between February and April 2009.
Microsoft Office SharePoint Server 2007 has moved from the “Visionary” quadrant into “Leaders” quadrant, in the past year. According to Gartner’s Magic Quadrant for Enterprise Content Management (ECM) for 2008, this move has been fuelled by steady course of SharePoint and the number of the companies that have implemented it. Gartner recognizes that SharePoint OOB offers basic tools for six core ECM features, supported by a strategic vendor that is Microsoft.
Gartner also warns that SharePoint is still lacking improvements in scalability and replication management, as well as quality imaging and BPM tools.
Let’s do a quick recap about what we could expect from the next version of SharePoint from Microsoft:
||The SharePoint v14 / 2009 will be shipped only as x64 installation
||Silverlight 2.0 webparts or UI will be present.
||SQL tables-like behaviour for SharePoint lists
||If the user has Groove client installed, more options will be displayed for data synchronization, in more seamless way.
|Master Data Management
||Master data source for keeping only one version of the truth. This data can be surfaced as SQL Server views or SharePoint data. In essence, a rebranded and somewhat expanded version of Stratature product +EDM, now known as Codename “Bulldog”.
||SharePoint UI will produce clean XHTML-compliant output.
|FAST search integration
||FAST-based enterprise search as a Search replacement. Webparts that show FAST search results.
|ODF and PDF support
||Custom filters won’t be necessary to index and extract metadata from ODF and PDF files.
||Content Management Interoperability Services will allow SharePoint to communicate with other ECMs via web services.
|Claims-based Authentication mechanism
||Decouples the authentication mechanism from its implementation. It will enable SharePoint to use any interoperable authentication mechanism to authenticate the users.
Ok, I admit that the joke attempt wasn’t even remotely funny 😉
Being in SharePoint business for several years now has exposed me to lot of SharePoint-related books that exist. I remember back in the SPS 2003 times when those books were easily numbered with the fingers on one hand. Now, however, there are more than two dozen of them and the choice of which one to buy isn’t always an easy one.
I’ve divided the SharePoint books in three categories:
- Introductory (those for absolute beginners or people that hasn’t messed with SharePoint)
- Intermediate (for those that want to venture beyond the basic steps)
- Advanced (for the people that breathe SharePoint every day)
In this post I am listing three good books for beginners. In the next posts I will do the same for intermediate and advanced-level SharePoint books, too.
Introductory Level Books
|SharePoint 2007: The Definitive Guide
||Comprehensive and easily readable, it is an introduction and review of SharePoint usage and administration.
|Essential SharePoint 2007
||Nicely illustrated and fairly well written. Not so extensive as “The Definitive Guide” but good enough.
|Essential SharePoint: Delivering High-Impact Collaboration
||Concise and nicely summarized book about the business applications for SharePoint, with special attention to planning and information architecture.
Yesterday a misleading error happened. A custom layout was deployed using Features and WSP solution packages. Everything went well, but when browsing to a page using this new layout, this message appeared:
Only Content controls are allowed directly in a content page that contains Content controls.
Furthermore, SharePoint inserted this funny-looking content after our Content element:
<!--[if gte mso 9]><xml><br /><mso:CustomDocumentProperties><br /><mso:ContentType msdt:dt="string">Page Layout</mso:ContentType>
I started googling and I found a blog post by Rich Finn that in essence has the same problem.
Apparently, when a unknown or misspelled tag is found in page layout, SharePoint adds the content type information in a XML fragment, between the <asp:Content> tags. However, in ASP.NET no additional tags are allowed as first-level children, beside Content. In our case we had one <asp:content> tag, which was misspelled.
Ensure that the <asp:Content> tags are properly capitalized. SharePoint seems to freak out when <asp:content> tag is found. 😉