September 2007
Beginner
448 pages
10h 2m
English
Content preview from Essential SharePoint 2007, 2nd EditionBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Converting Existing Projects
Web parts developed for the previous version of SharePoint need to be rebuilt if they:
Access the SharePoint object model
Require enhancements that use the .NET 2.0 Framework
Need to be deployed as solutions rather than as DWP files
In other words: you'll probably want to rebuild existing web part projects. Because the web part project template has changed as well, it's best to start fresh and move your existing web part classes over to a new project, rather than trying to upgrade the original project.
To convert an existing WSS 2.0 web part project to use the new Visual Studio web part extensions template:
Create a new web part project using Visual Studio 2005 web part extensions.
Copy the class files (.cs or .vb) and any supporting files (.htm, .dwp, etc.) from the existing project to the new project's code folder.
Add the files to the new project.
Change the namespace for the classes to the current project's namespace.
Build the project and resolve any errors or warnings.
Much of the existing code will compile successfully using the new SharePoint and ASP.NET references. However, there is some overlap between the ASP.NET and SharePoint WebPart classes, so you may get errors like the following:
'MenuItem' is an ambiguous reference between 'System.Web.UI.WebControls.MenuItem' and 'Microsoft.SharePoint.WebPartPages.MenuItem'
You can fix those errors by fully qualifying the class, as shown here:
_mnuSave = newMicrosoft.SharePoint.WebPartPages.MenuItem("Save Settings", ...Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.