Hide Notes 

Slide 1: Developing Web Parts using Visual Studio.NET Muhieddine Chaaban Technology Advisor - Microsoft Corporation
Slide 2: Agenda Web Part Page Rendering Context Web Part Zones Programming Web Parts Deploying Web Parts
Slide 3: SharePoint Products & Technologies Consistent, connected experience Users, IT, and Developers Rich out-of-box experience Browser and Office Extranet Enterprise Flexible, economical deployment Rich platform, partners Division Team Individual
Slide 4: Windows SharePoint Services Windows SharePoint Services is great out of the box No code required for immediate value List management is in the box Rich extensibility for custom solutions Managed server object model Remote access through Web Services Web Part infrastructure for extending UI
Slide 5: Sample Web Part Page Announcements Members Events Contacts Links
Slide 6: SPS/WSS web part pages
Slide 7: Web Parts - Framework ASP.NET Page Zone 1 Zone 2 Zone 3 ASP.NET Page Web Part Framework Web Form Controls Content DB Web Parts are ASP.NET Web Form Controls SmartPage - controls on page determined by database URL of the page ID of the current user (personalization) SmartPages work in safe mode only
Slide 8: Web Part Zones Stuff on the Page… Web Part Zones are embedded directly on the page <SmartPages:WebPartZone runat="server" Title=“Left ZoneID=“…" Orientation="Vertical“ AllowCustomization=“true” AllowPersonalization=“true”/> Stuff in the db… All users and just for me web parts inside zones are stored in the SharePoint WebParts table Personalizations are stored in the SharePoint Personalizations table
Slide 9: Web Part - Base class Web Parts are ASP.NET Web Controls WebPart (base class) derives from System.Web.UI.Control Like all controls they participate in: Page rendering Property settings Post-back events State management Web Part = ASP.NET Web Control
Slide 10: Web Part Rendering Process Request ASPX Page ASP.NET starts page render Web Part WebPart.Render() CustomPart.RenderWebPart()
Slide 11: Saving Web Part Properties Properties are serialized and stored in the database Stored in two contexts: Shared Personal Storage is controlled by the WebPartStorage attribute: WebPartStorage = Storage.Shared WebPartStorage = Storage.Personal WebPartStorage = Storage.None
Slide 12: Tool Parts
Slide 13: Tool parts Also derive from Web Controls and are used to add custom functionality to the tool pane Different from web parts No mobility Limited base class property set No property storage Render only in the tool pane Rendering process similar to web parts ToolPart.Render cannot be overridden Implement RenderToolPart
Slide 14: Part to Part Connections An Introduction Allows Web Parts to send & received basic types of data; e.g. Cell, Row, List, etc. Uses standardized set of interfaces Allows completely independent parts to connect Enables end users to form connections Browser FrontPage
Slide 15: Supported Connection Interfaces
Slide 16: Interface Details Row Scenario IRowProvider Events •RowProviderInit() •RowReady() Event Handlers - None IRowConsumer Events - None Event Handlers •RowProviderInit() •RowReady()
Slide 18: Cross Page Connections Features Allow connecting parts on different pages Can only be created in FrontPage Certain interfaces supported Page 1 (Source) Page 2 (Target)
Slide 19: Web Part Code Access Security Code access security (CAS) allows box administrators grant specific rights to assemblies Goal of CAS is to separate access rights of the user from the access rights of the assembly Administrators can deny access to local resources for partial trusted assemblies Administrators can allocate trust based on signatures, strong names, and certificates
Slide 20: Deploying Web Parts Assembly located in: GAC (Global Assembly Cache) bin (sub directory under the application root) Windows SharePoint Services Controls, Namespaces and Assemblies have to be marked as ‘safe’ in web.config Class Resources and dwp’s deployed to specific locations
Slide 21: Creating a Web Part Package A Web Part Package is a .Cab file that contains: Manifest.xml Web Part Assemblies Class Resources DWPs Create a .cab file using VS.NET
Slide 22: Example Manifest.xml
Slide 23: Deploying Web Part Packages Web Part Packages are deployed using the stsadm.exe tool 3 operations related to Web Part Packages: AddWPPack EnumWPPacks DeleteWPPack
Slide 24: Building/deploying a basic Web Part Using Visual Studio.NET
Slide 25: Resources SharePoint Products and Technologies Developer Center http://msdn.microsoft.com/SharePoint Online SDK White Papers Code Samples Web Component Directory http://www.microsoft.com/SharePoint/webparts
Slide 26: © 2003 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.