Custom software developer. IT consultant. Geek.
Windows Sharepoint Services v3 Development (1)
June 12, 2006
My notes from attending this Microsoft Tech Ed 2006 session…
- Site columns: represent name of column and meaning. These are useful because youc an use site columns in more than one Content Type and then they’ll share columns if they’re displayed together.
- Content Type: Item schema (set of columns), TEmplate, Parent content type, scope, workflow.
- Lists define: Navigation, settings like history, attachments, permissions, workflow.
- Content types are hierarchical.
- Site columns are definted at the site livel.
- You can have multiple content types in a view. The Content Type determines what the data entry form will look like.
- Changes can optionally be pushed down (granular control over how much gets pusehd down).
- Admins can “seal” a content type so it can’t be inherited / changed.
- Change content types: add/remove columsn, read only, workflow, template
- Excel 2007 can no longer 2-way sync with WSS. Access 2007 does this now.
- To access SharePoint data from within a VS project, reference Microsoft.Sharepoint.DLL.
- Create SpSite object, then SpWeb object
- In example, presenter created SpContentTypecollection, SpContentType, SpFieldCollection, SpField to list out the fields.
- Document Template in a Document Gallery: The properties panel is edited by InfoPath.
- Event Framework: Item/List/Web, Before and After Events
- Inherit from SpItemEventReceiver, SpList, Spweb
- Receivers have to be strong-named and put into the GAC
- Create Feature.XML and Elements.XML files that describe the event.
|
Follow comments to this post through RSS 2.0. Both comments and pings are currently closed. |
Comments are closed.