Wictor Wilen

SharePoint 2010 comes equipped with a set of new tools to improve the monitoring of your custom applications, there are built-in functionality to check how long your operations take, how many SQL Server calls are done etc. All this is logged and can be visualized in the Developer Dashboard. Another good thing with this is that it’s not something that just automatically is there but you can also hook yourself into the monitoring and the actual Developer Dashboard.

Yesterday we had a Swedish SharePoint User Group meeting, hosted by Connecta (yes, my new employer). We had a new record with number of participants, over 60 interested SharePointers of all kinds showed up to listen to MVP Göran Husman, Humandata, talk about the news in SharePoint 2010 and Peter Karpinski, Microsoft Services, talk about how to do Rapid Application Development with SharePoint 2010, SharePoint Designer 2010, Visio 2010 and InfoPath 2010 and how to script you SharePoint 2010 installs. Thank you for great shows and thanks to everyone who showed up.

Working with SharePoint 2010 is really a joy, you stumble upon great things all the time. The API has not had any revolutionary changes to be backwards compatible; but small changes here and there, both publically visible and internally, really makes the API better than before. SPListItem.SPContentTypeId To get the Content Type Id of an SPListItem you had to first get the SPContentType from the SPListItem.ContentType and then get the Id of the content type. This method was one marked as internal in version 12, but is now marked 14. It’s those little things. There are actually a lot of previously internal properties and methods that now are public, for example the CanBeDisplayedInEditForm property on the SPField class.

SharePoint 2010 is one greedy beast and you can’t settle with your plain old laptop; first of all you need a x64 bit environment and second of all you need some RAM. Developing for SharePoint 2007 required just a 32-bit machine, less than 4 gigs of RAM and Virtual PC and you could do most of your work without complaining to much. SharePoint 2010 requires some more thought through development environment .

Visual Web Parts are a nice addition for SharePoint 2010 developers. A Visual Web Part is essentially SmartPart revisited and is one of the project types of the new SharePoint extensions for Visual Studio 2010. Sandboxing is one of the most interesting features of SharePoint 2010, especially for large scale implementations and hosting providers. The Sandboxing feature, or User Code Solution, allows you to easily upload a SharePoint feature into your farm into a special controlled environment – called a Sandbox. These Sandboxed features can be controlled by the SharePoint administrators so that they do not consume to much resources and automatically disable them if the exceed their limits. Sandboxed solutions also have severe security restrictions – you cannot access all objects or resources that you would like.

SharePoint and Exchange Forum 2009 (#SEF09) is over and I’m pretty tired but really excited. Two full days, here in Stockholm, Sweden, of SharePoint 2010 information with some awesome speakers and topics. SEF09 was a great conference, about 200 participants – just about the right size to have the time to chat with a lot of people and having a good time. This year the SEF conference also was the official launch of Exchange 2010 and the first larger showing of SharePoint 2010 bits in Sweden. As an extra bonus the SharePoint 2010 beta 2 bits were released during the Monday night party, and during the Tuesday sessions everybody was downloading the bits.

Just hours before the SharePoint Conference 2009 starts in Vegas, and all information will flood out from the conference, blogs and twitter, Microsoft released three four posters that should help you in planning and updating your SharePoint 2007 installation to SharePoint 2010. Microsoft SharePoint Server 2010 Upgrade Approaches (added since original posting) Visually describes the different upgrade approaches Microsoft SharePoint Server 2010 Upgrade Planning Takes you through how to upgrade hardware and software on your servers. Shows the available upgrade paths.

The long awaited service pack for PerformancePoint Server 2007 is now released to the web - Service Pack 3. This is the last service pack for PerformancePoint Server since the PerformancePoint Server bits will from next week be turned into PerformancePoint Services in SharePoint 2010. Service Pack 3 is the last update to the standalone version of PerformancePoint, which was announced in January this year when Microsoft changed their BI strategy. After this update Microsoft will not invest any further into the 2007 version and as you hopefully are aware of - the Planning module will not exist in the upcoming 2010 version. The Planning module is instead offered as source code - now called the Financial Planning Accelerator, so that you can safely still use any investments in the Planning Module.

Delegate Controls in SharePoint is a blessing when you are customizing the features and interface of SharePoint. The Delegate Controls are areas in the out-of-the-box SharePoint pages where you are allowed to inject your own controls. This is heavily used by Microsoft Office SharePoint Server 2007, which essentially is a set of features on top of Windows SharePoint Services. For example the standard WSS user information page redirects to the MOSS My Site, this redirection is done by inserting a delegate control into a specific delegate control on the userdisp.aspx page. This nifty delegate control can be used in a WSS solution when you want to create a custom profile page, without modifying any of the OOB files and easily reverts to it’s original state when you deactivate the feature.