Microsoft Office Tutorials and References
In Depth Information
Silverlight The Silverlight web part is meant to contain Silverlight code to display
something made in Silverlight. Because Microsoft is hoping that Silverlight will be as ubiquitous
as Flash, this could be a useful little web part. However, this web part is not for people who
don’t know how to code for Silverlight.
The Social Collaboration category contains two web parts, Site Users and User Tasks. I’m not
sure why User Tasks is there (I think it would be much better placed in the Content Rollup
category), but there you go.
Site Users I have a feeling the Site Users web part is finally going to come into its own with
this version of SharePoint. This web part is meant to display the users on the site and indicate
(if you have online presence or smart tagging enabled and set up properly) their online
status. Back when People And Groups was available in the Quick Launch bar, this web part was
redundant. If the users wanted to know the account names of other site members, they could
just use People And Groups. It would also show their online status.
Now, however, People And Groups is not that easily available, since it has been removed from
the Quick Launch bar. But this means that having an easy way to click a member of the site
(and see their user information) or see whether they’re online on the home page could be
kind of useful. This web part is on the home page of a Document Workspace by default.
If the web part is added to the top-level site or to a site set to not inherit permissions from its
parent site, it will have an Add New User link. This link will take the user to an Add New
User page, even if they do not have the right to add users (and therefore will fail to be able to
do so, no matter what they type in, even though it lets them ill in all the fields as if they were
going to succeed). I’m not crazy about that, but at least you know what you’re getting into.
User Tasks The User Tasks web part, like Relevant Documents, filters its display by the
logged-in account, showing only the tasks for that user (essentially personalizing it), as well
as aggregating all relevant tasks for the user on the site, regardless of which task list (if there
is more than one) the task was actually created in. It is because of this aggregating or “roll-
up” behavior that I think it should have been put in the Content Rollup category.
SQL SERVER REPORTING
You might have noticed an additional category, SQL Server Reporting, for web parts. This category
contains the web part template to create a Reporting Services Report Viewer web part (and can be
used to display reports). Reporting services has considerable configuration requirements, and is
pretty non-standard at this point.
Although we might not explore every single one of the types of web parts individually, we
are going to do enough that you can get the hang of them and work with them on your own.
To that end, let’s insert a few web parts and see what happens. To start, we’ll work with the
Relevant Documents web part. This web part, as was listed earlier, lets the users see all the
documents they are working on in the site, regardless of what library they might have them in. Of
course, once this web part is set up, we won’t be needing the Shared Documents library anymore.