Skip to main content

Highlights from SharePoint 2010 - from SPC2009

I'm here at Microsoft's SharePoint Conference 2009 with lots of cool info about SharePoint 2010. I will start by saying the new release is cool. Lots of annoying things about 2007 have been fixed, and there's lots of useful information.

I thought I'd quickly list out some of the highlights that I hold dear...

  • You've probably seen this already - the Ribbon interface is EVERYWHERE. This includes all web part pages, publishing pages, list forms, and admin pages. Like it or loathe it, you probably should embrace it or get out of the Microsoft Office ecosystem.

  • A new Dialog Framework has been introduced, so editing item properties does not take you away from where you were. Interestingly (perhaps lazily?) this has been implemented via an absolutely positioned div tag with an iframe inside - the UI benefits for users on this is tremendous (IMO)

  • SharePoint and SQL need to run on 64 bit operating systems

  • The requirements for SQL is 2005 SP2 or 2008 SP1 Cumulative Updates 2 or later

  • You can now design web parts as ASP.NET Server Controls (.ascx files)

  • Web parts are being moved away from legacy "WSS" Web Part APIs, and instead everyone is encouraged to develop web parts against the ASP.NET WebPart class. WSS will still be supported in 2010, but are being phased out

  • If you're into making your own Office documents (.docx, .xlsx, etc), the Office Open XML SDK has a new version (v2) which means no more creating XML yourself - all operations are done via the API.

More to come later on the remainder of sessions I'm attending.


Popular posts from this blog

Thoughts, shortcomings, gotchas on SPFx Dynamic Data capabilities

It's the festive break, and I thought I'd try the new Dynamic Data capabilities that recently went to General Availability in SharePoint Framework 1.7. I've been building a lot of React components lately, and all the SPFx web parts and application customisers with visual elements we create at Engage Squared, are built on React.  Dynamic Data in SPFx introduces a whole new world of modularity that we haven't had before. We can now split up the page elements into multiple web parts that, in the past, have been combined as one web part so state can be passed between them.  Doing this gives control back to the page author, with the ability to position components how they wish. Breaking components up in to individual web parts also changes the way the components are designed, and forces the developer to leverage the responsive capabilities of modern pages.  Modern pages are designed from the ground up to work on many different screen sizes, and as long as each individual

Apps for SharePoint 2013 - Client and Server-side code

It's about time I blew the dust off this blog. Tonight I did a presentation at the Melbourne SharePoint User Group entitled Apps For SharePoint (2013). It included two demos based on the App For SharePoint 2013 solution template in Visual Studio 2012. The two demos illustrated how you can create a separate ASP.Net Web Application. Demo 1 showed how easy it is to hook in to SharePoint to obtain List properties via server-side code (populating an ASP.Net Repeater Control). Demo 2 showed what you can do with SharePoint 2013's Javascript hooks. Specifically, using SP.UI.Controls.js from the /_layouts/15/ SharePoint folder to pull chrome elements out of SharePoint, and render them in your ASP.Net web app. No animals were harmed in the making of these demos, but a few articles kindly provided on the Microsoft MSDN site helped put it together: How to: Set up an on-premises development environment for apps for SharePoint How to: Create high-trust apps for SharePoint 2013 usin

SharePoint User Profiles and Properties error

I recently encountered an issue with the Shared Services Administration page for User Profile and Properties (the page where you schedule an Active Directory profile import). The page in question is in the Shared Services Provider site, e.g. http://server:port/ssp/admin/_layouts/ProfMain.aspx The error that gets displayed is: An error has occurred while accessing the SQL Server database or the Office SharePoint Server Search service. If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator. The error was odd, because I knew SharePoint Search was functioning (search crawls were running as normal, and search queries were being filled in the web front end). After a bit of investigation, I found the following table to be missing some records that were required. So in actual fact, the error being referred to when accessing the SQL Server database was that some expected records weren't in the table being looked up,