Office Business Applications (OBA) Workshop – Day 2

Agenda:

• The SharePoint Web Site and Security Framework
• The SharePoint Storage Engine (Parts 1 & 2)
• Defining Business Process and Workflows

Important links discovered during the second day of training:

• SharePoint Community Portal
• Customizing and Branding WCM-Enabled SharePoint Sites
  • Understanding Web Content Management and the Default Features
  • Extending WCM
  • Creating and Configuring WCM-Enabled Sites
• U2U Community Tools
  • Specifically look at the CAML Query Builder!
• .Net Reflector
• Create custom activities for use in SharePoint Designer workflow wizard.
• Office Developer How-To Center
• SharePoint 2007 Visual How-Tos

Notes:

• Execute the following command when demoing without an active network connection: net stop sens
• Create features for all modular pieces of functionality. Then make features dependant on one another. Turning on/off a feature with dependencies will disable the dependant features as well.
• Custom list definitions treated as separate features when expected to be used in more than one site.
• Feature stapling is done by one feature connecting a group of sub-features.
  • Blog describing the use of feature stapling
• When developing feature:
  • Mimic the 12 hive directory structure starting from the “Template” directory and creating any necessary sub directories and files (i.e. Features, Layouts, etc.)
• Aspx files stored in the Layouts directory can contain inline server side code.
• Kerberos not used that often in real world, because it is complicated to setup and maintain. (At least this is what Patrick said when I spoke to him about this.)
• BDC custom actions that require authentication could point to an application level aspx page (in the layouts directory) that speaks to the SSO credential store and forwards the request to the OSM application server after attaching the credentials.
• Excel integration to create SharePoint list content! Could we utilize this for BOM creation?
• How can we utilize Access’s built in offline functionality?
• Versioning scheme cannot be customized (at least not like Model Manager). It is only number based with major and minor parts.
• In Word, use InsertàQuick Parts to insert document properties in document.
• Content type field generation tricks:
  • Create a custom list in SharePoint UI and use solution generator to reverse engineer custom list and use schema.xml
• SharePoint Visual Studio Extensions are good for development, but not so good for final build and packaging for real world deployment. Currently not enough control over solution packaging process.
• Need to make sure you dispose of SPSite or SPWeb objects (use a using statement).
• Use SPSiteDataQuery class to execute a cross list and cross site query of specific data.
  • Could be used for profile page web part to display tasks associated to the specific Masterdata
• Web services are faster than the object model a lot of times.
  • Web services utilize a lot of the in memory cache that SharePoint provides, and the object model always goes to the database and ignores the cache.
• XmlFormView can display InfoPath forms inside a webpart or any other ASP.Net based page.
• The workFlow history list is hidden, but can be accessed via the following URL: http://<site>/workflow%20history/

Advertisement