|
|
|
Instructor
Notes
|
|
Now it's time to
talk about how WSS V3 layers on top of the ASP.NET Web Part infrastructure.
|
|
|
|
First, point out
that Web Part customization data needs to be written not to the ASP.NET
services database but to the content database of the hosting WSS site. For
this reason, the WSS team was not able to directly use the WebPartManager
control or the WebPartZone control. Instead these used these classes as base
classes and dirived two specialized class named SPWebPartManager and
SPWebPartZone.
|
|
|
|
One of the main
reasons to point this out to students is that Web Part pages contain
WebPartManager and WebPartZone from an ASP.NET application cannot be used
inside a WSS site unless it is modified to use SPWebPartManager and
SPWebPartZone.
|
|
|
|
Finally, mention
that the SPWebPartManager is placed on default.master so that it doesn't need
to be placed on content pages.
|