This is the second presentation I decided to attend. Presented by speaker; Paul Andrew from Microsoft. I’m posting the highlights from the presentation in the form of notes. As time allows over the coming months, I look forward to providing more in depth information on many of these:

  • Steve Creates a custom Web Part using Visual Studio 2010
  • Inserts the web part outside of a web part zone, in the content/wiki area of a page (very cool!)
  • Business Connectivity Services (Replaces Business Data Catalog)
    • Ability to Connect to .NET Data / .NET Types
  • SharePoint List Improvements
    • Cascading and Restricted Deletion (shown in demo)
    • Formula Based Validation (Excel like)
    • Lookup to multiple columns
    • List Index Auto Creation
    • List Query Throttling (allows IT Admins to set limits/restrictions on number of items in views)
    • Allows you to specify validation messages on fields for list… In other words, you don’t just specify that a field is required, or the format; but you can also specify the message that gets displayed to the user if it doesn’t meet the requirements. (Fantastic)
    • XSLT based View creation rather than CAML
  • Client Object Model which runs on remote machines. Helps overcome issues with network load. Sample: Create reference to SharePoint Context > Load > Execute Query (call gets made which gets context info) > Execute Logic (such as UpdateTitle or AddItem) > Item.Update > Execute Query (call gets made again and change is applied)
  • Events Improvement
    • After-Synchronous Events
    • Site Scoped Events
    • Web Creation Events
    • List Creation Events
  • Workflow Improvements
    • VS 2010 Initiation and Association Forms (shown in demo, much much easier than it was before)
    • Import SPD Workflows in Visual Studio
    • Visio 2010 Workflow Design
    • Many more, at least another 15… (could not get them all, changed slide to quickly)
  • Sandboxed Solutions
    • Easy Deployment
    • Iterative Deployment
    • Solution Gallery
      • Way of Uploading the WSP into SharePoint
        • Does not sit on the file system of the machine until someone uses that piece of code until someone approves
    • Monitors Process and Restricts API Calls using code access security
    • If the code uses more resources than its permitted it gets shut down
    • There are several rules that can be created and applied to the solutions to make it easier to test these without bringing down the farm.
    • Processes run against proxy instead of directly against SharePoint API (will need more info about this, but sounds impressive)
      • Able to log the commands that are being routed through the proxy to among other stuff.
digg_url = “https://blog.rafelo.com/2009/10/overview-of-sharepoint-2010-developer.html”;digg_title = “Overview of SharePoint 2010 Developer Platform – SPC 2009 Presentation Highlights”;digg_bgcolor = “#FFFFFF”;digg_skin = “compact”;digg_url = undefined;digg_title = undefined;digg_bgcolor = undefined;digg_skin = undefined;
Advertisements