SharePoint 2010 Development

Editor's Notes

• #3: SharePoint Designer has gone through many significant changes and is now a solid development toolSharePoint objects such as lists and workflow associations are seen as first class objects in the new UIEach SharePoint object has a summary pageThe new workflow designer is much more powerfulSPD can create reusable workflows – this was a big problem in SPD 2007Prototypes created in SPD can be migrated into Visual Studio 2010
• #5: The SharePoint team has now gotten in line with many other server product teams at Microsoft and made SharePoint Server 2010 completely administrate-able through PowerShell scriptsBoth dev’s and admins need to get to know powershell, as a dev it will replace some of the console admin apps typically written as well as setup and tear down scripts for deployments.
• #6: Windowspowershell plus load snapinSharePoint management shell from sharepoint menuISE – can limited debugVisual studio for custom cmdlet creation + third party tools
• #7: Get all sharepoint commands
• #8: The developer dashboard has been introduced with SharePoint Server 2010. It shows diagnostics and performance-related statistics.How long did the request take to run?What event handlers were fired?In what sequence did these event handlers fire?At the moment is enabled via code/powershell. Can be set to on , off or ondemand
• #9: The Visual Studio 2010 SharePoint Tools (SPT) represents a significant step forward for professional developers using SharePoint. SharePoint Explorer fallows quick exploration through a siteThis makes it possible to launch browser at specific place within siteSharePoint 2010 introduce a new project structure as well as project tmplates and project item templates. There are designers to create things like features and solution packages.One of the most appealing aspects of SPT is that it is extensibleYou can add your own custom project templates and item templatesYou can add menu commands into the Visual Studio UI.
• #12: Version Range denotes the target version to upgrade. Any feature with this version or newer, or where a version does not exist will be upgraded to the EndVersion. The feature version is updated to reflect this new EndVersion.ApplyElementManifest – allows for an additional manifest file to be added to the featureCustomUpgradeAction -- allows for the passing of one or more parameters to a feature receiver’s FeatureUpgrading method.AddContentTypeField – Adds a new field to a provisioned content type. The element takes a ContentTypeId, FieldId, and a bool PushDown which denotes ifThe system should propagates the change to child lists and content types. (Optional)MapFile – Maps a file that has not been customized to a different path on the front-end web server or to simply rename a file. V2V Upgrade most likely scenario.
• #15: Highlight that code may run well after you intended e.g. when feature is enabled on site b the first version will run, then the upgrading code.If lots of versions have been incremented this could be a lot of code to run onfeature activation.
• #16: WebAdding/ WebProvisioned only fired for sub webs, not for the root web of the site collection.Plus despite naming they are a pair sync and async.
• #17: SPF 4.0 introduces concept of synchronous post-eventsAllows developer to do a little post-processing after the commit of the action, but before user is presented with the result of the post
• #18: In WSS 3.0 when a workflow triggered an event by adding/changing something in a task list, the task item’s identity would be the system account that executed the workflowIn SPF 4.0 the same is true, but the SPEventPropertiesBase now contains properties that contain the user name & user token of the person who actually triggered the effective action (like started the workflow)
• #19: An elements manifest (eg. elements.xml) file can contain a new element section called PropertyBag. This element allows key/value pairs to be promoted into their parent object such as a web, sub web, folder, list item, or file (note no List object here). This allows the developer to avoid writing code which promotes feature properties into property bag elements of these objects. Each value is added to or updated within the Hashtable object which implements the property bag at the parent. Currently two type DateTime and Int32 are enforced in that if the current value is of either of these types for any key which exists an update to these values need to be of the same time or the value in the Hashtable will be set to NULL.Note supported: Farm, WebApplication, ..ListSo this means this will not work for a Farm or WebApplication feature, only supported scope Web.
• #20: All of the information is saved as a real solution which VS can open. Developers can build on top of.There is a tie back, they were created from the same WSP, they get the new functionality, features, etc.WebTemplate feature Element – provides a way to deploy site collection specific site definitions. WebTemplate has it’s own site definition (onet.xml), which is merged with the oob site definition template.$ListId:Lists/Announcements – replaced with list GUID when provisioned – this new options is utilize as part of the wsp saving process. You can also utilize this by your self, which provides you a way to customize the view aspx pages etc.
• #21: Finally support for joins! Joins can be implemented using CAML query, but much easier to use LINQ CAML schema updated to support LINQ based joins LINQ will generate the CAML under the covers… LINQ much easier to write than new CAML schema Can also create joins via API using two new properties: SPQuery.Join & SPQuery.ProjectedFields
• #22: Throttled lists, which is triggered by exceeding the upper limit, will cause queries with a result set in excess of the upper limit to throw an exceptionHowever, this can be overridden by users with required permissions via code
• #23: Ensure you include one of the three OrderBy clauses—ContentIterator.ItemEnumerationOrderByID, ContentIterator.ItemEnumerationOrderByPath, or ContentIterator.ItemEnumerationOrderByNVPField—that enables the index to be used.Without an OrderBy clause, your query could be blocked. SharePoint Server 2010 adds a default OrderBy clause that orders by content type, which ensures that folders are returned before list items. Unless you override this behavior with one of the three OrderBy clauses listed above, your query cannot take full advantage of using indexed fields, and it will be blocked whenever the query is not designed to be restrictive enough to return fewer than the maximum number of items. The following code example shows how to use the ContentIterator.ItemEnumerationOrderByNVPField clause. The example assumes that you are querying an indexed field.
• #24: Ensure you include one of the three OrderBy clauses—ContentIterator.ItemEnumerationOrderByID, ContentIterator.ItemEnumerationOrderByPath, or ContentIterator.ItemEnumerationOrderByNVPField—that enables the index to be used.Without an OrderBy clause, your query could be blocked. SharePoint Server 2010 adds a default OrderBy clause that orders by content type, which ensures that folders are returned before list items. Unless you override this behavior with one of the three OrderBy clauses listed above, your query cannot take full advantage of using indexed fields, and it will be blocked whenever the query is not designed to be restrictive enough to return fewer than the maximum number of items. The following code example shows how to use the ContentIterator.ItemEnumerationOrderByNVPField clause. The example assumes that you are querying an indexed field.