| There was a session on SharePoint Composites and integration with BCS. It started with a good set of points of interest to developers. Here are my takeaways:
• Composites. I'm still looking for a nice detailed definition of this, but one way of looking at composites is, "stuff in SharePoint that doesn’t fit in another box."
• Why develop in SharePoint? SharePoint gives Data Storage, Presentation (UI and nav), Clustering, Security, Disaster Recovery, Web Services, and API. All already done out of the box in SharePoint. In straight .net, you can write this stuff, but it’s not value-add if SharePoint already does it.
• The SharePoint API is the largest API Microsoft has everwritten.
• Kinds of custom code in SharePoint: workflow, web parts, event receivers, site definitions, data forms.
• Packaging does not change with SP2010 – use WSP’s. Even though the packaging doesn't change, there are better tools for customizing and deployment. (Note that WSPs are required for sandbox solutions).
• F5 now works to kick off debugging, and breakpoints work.
|