WSS And Share Point For Developers

54 %
46 %
Information about WSS And Share Point For Developers

Published on December 5, 2008

Author: mannysiddiqui



This presentation is for the developers who want to embark upon the SharePoint development and don\'t know where to start, how does it differ from traditional ASP.NET development, etc.

Brief introduction to WSS/MOSS  WSS/MOSS Architecture   Integration with ASP.NET Development in WSS/MOSS   Development options  Security  Deployment Tips and Tricks  Tools  Real World Application 

WSS/SharePoint together provide   A collaboration and information sharing platform  A site provisioning engine  Business Intelligence and Business Process Automation  Search  Many more features WSS is part of Windows Server 2003 (free)  MOSS is a separate installation (not free!) 

How many people know   The basic WSS/MOSS architecture concepts  How to use the WSS/MOSS Central Admin Site The following are some of the basic architecture  concepts in WSS/MOSS  Farm (and Configuration database)  Web Application (and Content database)  Site Collection and Sites  List

One or more servers which provide the  WSS/MOSS functionality A Configuration Database for storing the Farm  wide configuration information

An IIS Web Site configured to run WSS sites   Add some IIS meta-base entries  Add a web.config file to the root of the IIS web site IIS handles incoming requests for WSS/MOSS  More than one web applications in a Farm 

Site Collection is a container for the sites  More than one Site collection in a Web  Application A Site Collection has a root Site  Site can’t live along; it must be created within the  scope of a Site Collection

Conditional Demo

WSS/MOSS is nothing but an ASP.NET application!  WSS/MOSS add value to ASP.NET by hooking into  the ASP.NET request processing pipeline by virtue of:  Wildcard Application Mapping  SPHttpApplication  SPRequestModule  SPHttpHandler  SPVirtualPathProvider  Virtual directories in web application

Wildcard Application Mapping 

Custom Global.asax file with SPHttpApplication  class

SPRequestModule as the first module in the  ASP.NET pipeline This gives WSS a chance to perform some  initializations.

SPHttpHandler as the final destination for almost  all of the requests to the web application

SPVirtualPathProvider   WSS stores pages in the content database!  Those pages are retrieved on demand and processed.  This is drastically different from typical ASP.NET application where the pages live on the file system.  No fear, SPVirtualPathProvider is here!  Uses a new feature of ASP.NET 2.0 called Virtual Path Provider.  SPVirtualPathProvider is responsible for loading pages either from the file system or the content database.

Couple of virtual directories are created under  the IIS web site.  _controltemplates  _layouts  _vti_bin  _wpresources

Virtual directories under the IIS web site. 

See do we develop applications in ASP.NET?  Compare that to WSS/MOSS development   Paradigm change (new concepts and constructs)  XML based development  Different way of deployment

Site Pages  Application Pages  User Controls  WSS/MOSS Object Model and Web Services  Event Receivers 

Custom Site/List Definitions  Custom InfoPath Forms  Custom Workflows  Extending BDC (Protocol Handlers, etc)  Excel Services 

Site Pages 

Application Pages 

User Controls 

WSS/MOSS Object Model and Web Services   Assembly based object model is for the code that runs on the same server  Web Services are for managing WSS/MOSS through remote clients  Assembly based object model is richer and faster than web services  Most of the WSS/MOSS functionality is available

Event Receivers   As the name implies; these classes receive events.  Five types of event receivers  Item Event Receivers  List Event Receivers  Email Event Receivers  Feature Receivers  Web Event Receivers  Two main types of events captured by an event receiver  Before events (Synchronous)  After events (Asynchronous)  Must live in GAC

Item Event Receivers   Derives from SPItemEventReceiver class  Events are raised for the list items

List Event Receivers   Derives from SPListEventReceiver class  Events are raised when the list schema changes

Email Event Receivers   Derives from SPEmailEventReceiver class  Event is raised when a list receives an email message

Feature Receivers   Derives from SPFeatureReceiver class  Events are raised whenever a Feature is manipulated by WSS.

Web Event Receivers   Derives from SPWebEventReceiver class  Events are raised whenever changes occur to sites or web applications.


Features   Unit of Deployment  WSS/MOSS provide many of the their functionalities through features

Deployment   WSP  Consolidates all of the artifacts into one deployment package file (.wsp)  A typical CAB file created using makecab.exe  Some ad-hoc tools available for creating the supporting .ddf file needed by makecab.exe  The deployment of the package can be scheduled using the stsadm or Central Admin tool.


SPSecurity.RunWithElevatedPrivileges   Allows the code to perform administrative tasks which would not be possible to perform under normal execution  Runs the delegate method as the WSS SYSTEM identity (means no authorization in WSS/MOSS!)

WSS/MOSS Log   Contains tons of information for debugging issues  Log File Content

Change the .config file in order to get rich error  messages during development (No more “An unexpected error has occurred” message)  Turn the CallStack to true (it is false by default)  Turn off customErrors

Add 12 folder to the task bar 

Windows SharePoint Services 3.0 Tools: Visual Studio 2005  Extensions, Version 1.1  CD-1CCA-433A-BB4D-97B96BF7AB63&displaylang=en User Guide and Samples for Visual Studio 2005 extensions for  Windows SharePoint Services 3.0  5-074D-4451-BE39-459921F79787 STSDEV: Simple Tools for SharePoint 2007 Development   SharePoint Manager 2007   SharePoint Developer Explorer   SharePoint SmartTemplates for Visual Studio  

PowerShell Extensions for SharePoint   SharePoint 2007 List Membership Provider   SharePoint AJAX Toolkit   Community Kit for SharePoint   Accessibility Kit for SharePoint   SharePoint 2007 WCM Field Controls   WSPBuilder   SharePoint Cross-site Configurator  

Add a comment

Related pages

SharePoint general development -

... training, videos, code samples, and SDKs for SharePoint and SharePoint Add-ins. ... Use SharePoint to engage with people, share ideas, ...
Read more

SharePoint for Developers – BenkoBLOG

Based on what I did for my version It thought I would share ... SharePoint for Developers Webcast ... for Developers ( ...
Read more

SharePoint 2016, Team Collaboration Software Tools

Share, organize, and discover information with Microsoft SharePoint. Learn about SharePoint Online, OneDrive for Business, ... For developers .
Read more

Posts | @WonderLaura | SharePoint for Non-Developers

SharePoint for Non-Developers @WonderLaura SharePoint for Non-Developers. Twitter; Facebook; YouTube; LinkedIn; ... Tomorrow on my FREE SharePoint Power ...
Read more

SharePoint – Wikipedia

Abhilfe schaffen hier Zusatzprodukte von Drittanbietern, beispielsweise Control Point von Axceler. Authentifizierung SharePoint ... (WSS). Mit Version 2010 ...
Read more

SharePoint Training & Certifications -

Microsoft SharePoint 2010 Search for Application Developers ... Share this page with your friends and family. Product sites; Windows; Office; Surface ...
Read more

development - Sharepoint 2013 Developer Edition ...

Business Learn more about hiring developers or posting ads with us ... Sharepoint 2013 Developer Edition. ... share | improve this ...
Read more

The SharePoint Web Developer Experience

The SharePoint Web Developer Experience. Applies to: WSS 2 ... This course is designed for client-side web developers; ... It has been around since WSS 2.0
Read more

Download Windows SharePoint Services 3.0 from Official ...

Microsoft Windows SharePoint Services helps your team share and manage information and documents in a Web site. ... Developers ... point to Settings and ...
Read more