For an ISV or developer: “Foundation” represents base or entry level capabilities; “Server” represents higher level of functionality and possible higher revenue for software.
Sites = “portal” – the original reason that SharePoint existedCommunities = “social” or collaborationContent - more than just content management; including records management (classifying, storing, securing, and destruction of records.)Search - inclusion of FAST technologiesInsights – formerly known as Business Intelligence; new term is less “tech-focused” and instead implies business impact. Composites – more formal than “mashups”, but the same idea: mashing together web parts, forms, and workflow processes.
Details to follow…
Connect means write a connector
Play video here…
Extend means writing custom web parts
Build-on means building an app on SharePoint that might use connectors, web parts, or just out of the box items from SharePoint
What are the capabilities that SharePoint will provide for my applications? We’ll look at those over the next few minutes. They fall into 3 categories: InfrastructureContent ManagementUser Interface
What kind of application infrastructure does SharePoint provide?
Payback here: for simple data entry, the fact that lists automatically provide standard CRUD functionality is a huge labor savings; if those won’t do, then ASP .NET or InfoPath can provide us a better customization story. Also, for end users that are already using SharePoint they are familiar with the standard list views and ways of accomplishing things; if an application follows this approach then less training will be required for users. Support for SharePoint workspace (offline editing) where as ASP .NET could not do that. Power User might be able to create or extend InfoPath page in InfoPath designer. InfoPath already existed, but it has been more tightly integrated with SharePoint.
This slide tells a “connect” story and a “build-on” story
Example: Win Form could upload and post a document to a library.
Details to follow
Extension model – example: Replace Site Navigation Provider with a custom provider that allows site navigation information to be stored some place other than config db; could include xml, custom database, or other stores. PowerShell scriptable batch load of documents, administration, etc.
tight Visual Studio 2010 integration solves a lot of this
SharePoint designer – lies between what can be done with the SharePoint UI and what a developer could do with Visual Studio 2010. CorasWorks – app store for SharePointBamboo Solutions – webparts, custom solutionsNintex – Workflow, reporting, podcast serverQuest – migration, security, access managementThese are not only tools that might fuel the development process, they are examples of companies that have embraced the “connect/extend/build-on” strategy!!!!!!!!!!!!!
Call to action! How can we make informed decisions about moving forward?
takeaway is that ThreeWill can help you get involved in building on SharePoint 2010