Just hours before the SharePoint Conference 2009 starts in Vegas, and all information will flood out from the conference, blogs and twitter, Microsoft released
threefour 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.
Microsoft SharePoint Server 2010 — Test Your Upgrade Process How to set up a test farm and then install your customizations, copy data and review the results.
Microsoft SharePoint Server 2010 — Services Upgrade Perhaps the most exciting poster of them all with information on how to do an in-place upgrade of the Shared Service Providers in 2007 and how these services work in 2010.
They are all a good read and should be printed by all SharePoint admins out there...
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.
Read more about Delegate Controls here.
There are several places where you can inject your own code, and very few of them are documented, hence this blog post, which has lived as a OneNote page for me for some time. This is not a complete reference, but contains the most important (imho) delegate controls.
AdditionalPageHead (allows multiple) Exists in all the default master pages and allows you to insert controls in the head element of the page. SmallSearchInputBox The search input box present on all pages. WSS automatically adds the searcharea.ascx control here. MOSS replaces this one with the MOSS Search input box GlobalSiteLink0 Exists in the default.master. MOSS uses this one to publish the variations menu GlobalSiteLink1 Exists in the default.master. MOSS uses this one to add the link to My Site GlobalSiteLink2 Exists in the default.master. MOSS uses this one to publish the My Links feature CentralAdminLeftNavBarTop Used in Central Admin by MOSS. Located in the top of the Quick Launch DelctlCreateSiteCollectionPanel Exists on the create site collection page and used by MOSS to insert the categorization of Site Collections. DelctlCreateSitePanel1 Same as above but when creating Sites DelctlProfileRedirection Exists on the userdisp.aspx page. MOSS uses this one to redirect user the the MySite.
Do you have any favorite Delegate Controls?
Inspired by the latest SharePoint PodShow topic; The SharePoint Data View Web Part-Episode 31 and Laura Rogers post on building a permissions dashboard I just had to write this post. In the last paragraph Laura quickly mentions how you can reuse the created Data View Web Part. I think this is really important to know how to export and import this Web Part. What I don't want people to do is to fire up SharePoint Designer and create these Data View Web Parts in the production environment so that the pages get's unghosted or customized. Also when you are working with solutions packages and features to deploy your applications in environments it's necessary to know how to do this.
Once you have created and finalized your Data View Web Part in your development environment or sandbox, then you can export your customizations. This is the same for all kinds of Web Parts, as long as they allow exporting. When you export a Web Part through the web interface you will get a .webpart file (read earlier published post on this), containing all the properties and metadata specified for the Web Part.
Once you saved it you will have a nnn.webpart file on your disk, which essentially is an XML file with the metadata.
Note: Your exported Web Part will contain the exact properties as you specified in your original location. For example if you connected to it to a list this list id will not be present in the location where you import it. So before importing it you might have to change some values in the .webpart file or at least edit the properties of the Web Part after uploading it.
Importing to the Web Part Gallery
If you have created a Data View Web Part that you will reuse many times throughout a Site Collection it might be worth uploading it to the Web Part Gallery. Just go to the Site Settings and then the Web Part Gallery and select Upload and upload your .webpart file. After this your Web Part is available for all authors to use.
Importing to a page
Importing the Web Part is not that difficult, though it can be hard to find where to do it. To import the Web Part, go to the page where you want to insert it and edit the page and then choose to add a new Web Part. Then you have to select Advanced Web Part gallery options, located in the lower right corner. When the page is re-loaded click on the Browse header and choose Import.
After that you can click on Browse to select your .webpart file and finally click Upload. Once the upload is done the Web Part will appear and you can drag and drop it onto your Web Part page.
Once it is on the page you may have to edit the properties of the Data View Web Part. You might have to change the data sources, if you for instance configured your Data View Web Part to work with a certain Site id or a List id.
Using the Web Part in features
You can also reuse this exported .webpart file in your SharePoint features and have them added to the Web Part gallery when activating the feature.
Another scenario, which I've used to build dashboards and dashboard sites is that you use the SPLimitedWebPartManager to create dashboards on feature activations or certain events. The SPLimitedWebPartManager has an ImportWebPart method that takes an XmlReader as input, which essentially is your .webpart file.
I hope you got something interesting out of this and if you haven't listened to the SharePoint PodShow about the Data View Web Part - do that immediately and understand the power of it!
I'm glad and proud to tell you all about that next month I will start a new job. I will start as a SharePoint Architect at Connecta. This is a fantastic opportunity for me and it will let me work with some of the finest SharePoint minds and developers here in Sweden as well as some really awesome customers.
I've been working with basically the same company now since 2000, when I and two good friends founded it, iBizkit. We all came from consultancy firms working with WCM, portals and intranet solutions and had a dream of making a really good semi-product for these kind of solutions. And we did! In 2001 we integrated our product with the first version of SharePoint. We continued this integration in the upcoming versions of SharePoint, but have since the release of SharePoint 2007 focused more and more on the SharePoint platform, and I have personally lived in that world for the latest years. About two years ago, we sold the company to Pdb DataSystem, a natural step to expand and evolve the business.
During the last years I have been headhunted (or is headhaunted?) numerous times and finally I/we found a perfect match.
So in November I will be joining the Connecta forces and have 100% focus on SharePoint and especially the upcoming SharePoint 2010. This will allow me to grow and evolve as a SharePoint architect and developer, which is what I thrive on.
The only downside with this is that I won't be attending the (awesome, fantastic and once-in-a-life-time) SharePoint Conference 2009 in Las Vegas. To all you SharePointers - have a good time and I'll follow the tweets and blogs from over here! I'll even drink a pint while reading them. I hope to join you on upcoming conferences...
But if you're anxious to meet up, then head on over to the SharePoint and Exchange Forum in Sweden (SEF09) and come listen to me talk about PerformancePoint Services 2010 or come visit the free SharePoint 2010 overview event, organized by AddSkills and Connecta, where I'll show you some cool stuff that can be done with the ECM features in SharePoint 2010.
Until next time...