SharePoint Developer Experience Present & Future


Published on

SharePoint custom development can frustrate the most seasoned .NET developer. In this session learn about the various tools and techniques that can make you a more productive SharePoint developer today. Also get a glimpse of how Microsoft intends to improve the SharePoint developer experience in VisualStudio 2010 so that you can be a more productive SharePoint developer tomorrow.

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Integration tests means you’ll spend more time debugging your tests than your code.TypeMock Isolator
  • Will aid unit testing as you can now have strongly typed access to list data
  • Notice the Fluent UI being used. The ribbon is everywhere.
  • Detailed page request information such as timings, names and resources for all stored procedures called, memory used, the authenticated user, number of SPRequest objects, any asserts and critical events and timings for web part events related to page rendering.
  • SharePoint Developer Experience Present & Future

    1. 1. SharePoint Developer Experience <br />Present & Future <br />Matt Bremer<br />Solutions Architect<br />Covenant Technology Partners<br />
    2. 2. Agenda<br />SharePoint Development Challenges<br />SharePoint Designer<br />VSeWSS1.3 CTP<br />WSPBuilder<br />STSDev 1.3<br />Unit Testing<br />Future: VisualStudio2010<br />Review<br />Questions & Discussion<br />
    3. 3. Challenges<br />Development environment<br />Many ways to create a solution and or feature but no “best” way<br />SharePoint development is not currently a first class citizen in Visual Studio<br />
    4. 4. Pros <br />No assemblies<br />Fast<br />WYSIWYG interface<br />Cons<br />Artifacts are not portable<br />Customized vs. Uncustomized<br />Limited flexibility<br />SharePoint Designer<br />
    5. 5. SharePoint Designer<br />Demo<br />See how quickly you can create a custom web part connected to a SQL datasource using the data view web part.<br />
    6. 6. Pros<br />Upgrade path for SharePoint 2010<br />Provides choice between GAC or Bin for deployment<br />Installs to 32 & 64 bit environments<br />Integrated WSP view <br />Cons<br />Does not leverage MSBuild actions<br />Not 12 hive structure based<br />Generated files stored in bin directory<br />Requires Central Admin app pool have admin priviliges<br />Only creates solution/feature manifest when execute deploy but not on build <br />Abstracts too much<br />VSeWSS 1.3 CTP <br />
    7. 7. VSeWSS 1.3 CTP<br />Demo: See how to create a web part project using VSeWSS 1.3 CTP.<br />
    8. 8. Pro<br />Visual Studio &apos;New Item&apos; integration <br />Uses Solution Explorer Project Context Menu for deployment commands <br />Integrates with SharePoint Installer<br />Options for deployment <br />Cons<br />Uses WSPBuilder.exe to execute deployments in Visual Studio<br />Cannot extend WSPBuilder actions (e.g. what happens when you Deploy, Upgrade, Uninstall)<br />Generated files stored in bin directory<br />No integrated view into wsp<br />WSPBuilder required to open VS solution<br />No visibility to status of deployment in IDE<br />WSPBuilder<br />
    9. 9. WSPBuilder<br />Demo: See how to create a web part solution with WSPBuilder.<br />
    10. 10. Pros<br />Wizard based approach<br />12 hive structure based<br />Leverages MSBuild actions<br />Not required to open a VS solution<br />Generated files stored in DeploymentFiles folder and not bin<br />Good visibility via output window in IDE on status of deployment<br />Cons<br />Solution creation wizard outside of IDE<br />Projects reliant on VS solution<br />Not frequently updated<br />STSDev 1.3<br />
    11. 11. STSDev 1.3<br />Demo: See how to create a web part solution with STSDev 1.3.<br />
    12. 12. Unit Testing<br />Difficult to say the least, but doesn’t mean it cannot or should not be done.<br />Lack of public constructors on key classes makes them unmockable thus developers will need to write integration tests instead of unit tests.<br />Because end users can change lists in production, you must write more tests to account for your data changing and validate once solid assumptions.<br />Key classes such as SPList are marked final thus developers cannot create strongly typed entities and therefore must encapsulate them for tests.<br />
    13. 13. What Does the Future Hold?<br />Will SharePoint development become a first class citizen with the release of SharePoint 2010 and VisualStudio 2010?<br />
    14. 14. Visual Studio 2010<br />All project templates for SharePoint 2010 in VS 2010<br />
    15. 15. Visual Studio 2010<br />Creating a new deployment configuration<br />
    16. 16. Visual Studio 2010<br />Editing a solution manifest<br />
    17. 17. Visual Studio 2010<br />Solution package designer<br />
    18. 18. Visual Studio 2010<br />Creating a new deployment configuration<br />
    19. 19. Visual Studio 2010<br />Authoring support, never leave Visual Studio again!<br />
    20. 20. Visual Studio 2010<br />Visual web part editor, UI no longer has to be in code behind<br />
    21. 21. Visual Studio 2010<br />LINQ is native, no more CAML queries!<br />
    22. 22. Visual Studio 2010<br />The developer dashboard can be enabled on any page<br />
    23. 23. Visual Studio 2010<br />Developer dashboard provides real time diagnostic information<br />
    24. 24. Resources<br />SharePoint Developer Introduction for .NET Developers<br /> <br /><br />Office Developer Center<br /><br />SharePoint Designer Development Center<br /><br />Tools<br />WSPBuilder:<br />STSDev 1.3:<br />TypeMock Isolator:<br />SharePoint in VisualStudio 2010 <br /><br />Shameless Self Promotion<br />Blog:<br />Twitter:<br />Email:<br />Twitter Hash Tag for Event: #stldodn<br />
    25. 25. Questions & Discussion<br />It’s now time for “Stump the Presenter”!<br />
    26. 26. Contact Me<br />Snap bar code below to download my vCard to your mobile phone<br />Visit for more information<br />