Now that pages are the topic of discussion, master pages and a little branding fits in too. SharePoint 2010 ships with a number of master pages. Important topics to discuss on this slide is how application pages can now also make use of branded master pages, and how there is a default.master that ships the (non-fluent) v3 UI for backwards compatibility.
This chronicles the process of using a custom "bugs" Web Part and solution in a particular site.The SPSite adminuploads a new solution package (*.wsp) into the Solution Gallery of the SPSite. The SPSite admin"activates" the solution. This activates the features within the solution. Web Part files are copied into the Web Part gallery.As part of the activation, solution is validated using the validation framework. Custom validator can be added for example to check that only solutions signed with certain key can be activated. Customers and partners can develop their own validators based on their needs.Some time later, a user decides to add a Web Part to their home page. They go into Web Part edit mode, and click "Add a Web Part". They notice the additional Web Part options, and click Add. SharePoint now checks to see if the bugs.dll file, which backs this Web Part, is installed into the assembly cache. It is not. The assembly is faulted into the assembly cache; it is extracted and copied from the solution file to temporary folder in disk and loaded to memory (disk is cleaned immediately). Now the Web Part is about to be used. It is loaded into Sandbox Code service host.Processes deliver the Web Part to be executed to the service.
Developer Platform Workstation : Windows 7 or Vista SP1 64 bit OS only Not supported on production SharePoint Foundation or SharePoint Server Single Server Install
Developer Tools Dev Life with SP 2007 VS is Limited Edit CAML files Understanding RootFiles directory of WSS Manual edits to manifest.xml file WSP packaging nightmare
Developer Tools Dev Life with SP 2010 End to End Development Story Visual Studio 2010 SharePoint Designer 2010 Developer Dashboard SharePoint SDK
Visual Studio 2010 Instant Debugging SharePoint Project Project Items Feature Designer Workflow Designer Server Explorer Package Designer Package Explorer Import WSP Import from SharePoint Designer 2010 Team Foundation Server Support
SharePoint Designer 2010 No code tool for SharePoint Free for creating and editing SharePoint artifacts New Tools BDC Entities List Schema Custom Actions Task / Approval Designer Improved Tools Workflow Designer Page Editor SharePoint Designer work can be imported in Visual Studio 2010
Client Object Model Major request to increase web services Client OM is Simple API an abstraction layer to return results as recognizable SharePoint objects Consistent developer experience across platforms .NET ECMAScript Silverlight
Master Pages Page must derive from Microsoft.SharePoint.WebControls.LayoutsPageBase
Ribbon and Dialog Framework Replaceable SharePoint OOB forms Open as Web Page or as Dialog Client Site Custom Actions in Ribbon Context Sensitive Ribbon
Sandbox Solutions SharePoint 2007 No proper hosting model defined Hard to control what is being done in custom code SP 2010 Allow a subset of ‘full’ solution features Code executes in sandbox Are deployed by a Site Collection administrator Stored in the Solution Gallery
Sandboxed Solutions Process 2 1 5 6 7 4 3 Per-WFE AssemblyCache RootSPWeb of SPSite <siteguid>company.intranet.webpart.wspcompany.intranet.dll Solution gallery Web Part gallery Sandboxed Code Serice WebParts.wsp
Upgrade Your Code SharePoint 2007 code that runs within IIS should work without recompilation Anything Recompile Binding Redirect Deprecated APIs Compiler Warnings No future investment Path issues (14 hive)
Learn More MSDN (http://MSSharePointDeveloper.com) TechNet (http://MSSharePointITPro.com) Twitter Search #SP2010