Thursday, December 13, 2007

SharePoint Object Model

SharePoint is much more than just an application, it is an application framework. That essentially means that SharePoint doesn't truly shine until you begin extending its reach and influence and integrating it with other applications and solutions.

  • The Microsoft.Office.Server namespace is the root namespace of all Office Server objects.
  • Microsoft.SharePoint is the root namespace for all WSS objects.
  • Another reason you might find yourself creating code that utilizes the SharePoint object model is if you are creating Web Parts.
  • The only practical way to consume SharePoint data and functionality from a remote client is to use the SharePoint web services.
  • You might still want to expose specific SharePoint functionality contained in the object model in your own custom web service.
  • The object model is not designed to support Remoting. If you need to expose a portion of the object model that you can't easily access with one of the stock web services, you should create your own web service rather than attempting to use Remoting.

Setting Up a Local Development Environment:

  • The biggest advantage to the local development environment is the debugger.
  • Developers will often have their own Windows Server 2003 installations that are rough approximations of the target environment so that they can have the benefits of coding locally.
  • Browse to C:\program files\common files\microsoft shared\web server extensions\12\isapi, select the Microsoft.SharePoint.dll Assembly and add a reference to your solution.

Setting Up a Remote Development Environment:

  • A remote development environment is a development environment that is not on a SharePoint server.
  • Just need to copy the Microsoft.SharePoint.dll Assembly from the server to your development PC, and reference it from there.

Microsoft SharePoint 2007 Development Unleashed

blog comments powered by Disqus