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.
2. Agenda SharePoint Development Challenges SharePoint Designer VSeWSS1.3 CTP WSPBuilder STSDev 1.3 Unit Testing Future: VisualStudio2010 Review Questions & Discussion
3. Challenges Development environment Many ways to create a solution and or feature but no “best” way SharePoint development is not currently a first class citizen in Visual Studio
4. Pros No assemblies Fast WYSIWYG interface Cons Artifacts are not portable Customized vs. Uncustomized Limited flexibility SharePoint Designer
5. SharePoint Designer Demo See how quickly you can create a custom web part connected to a SQL datasource using the data view web part.
6. Pros Upgrade path for SharePoint 2010 Provides choice between GAC or Bin for deployment Installs to 32 & 64 bit environments Integrated WSP view Cons Does not leverage MSBuild actions Not 12 hive structure based Generated files stored in bin directory Requires Central Admin app pool have admin priviliges Only creates solution/feature manifest when execute deploy but not on build Abstracts too much VSeWSS 1.3 CTP
7. VSeWSS 1.3 CTP Demo: See how to create a web part project using VSeWSS 1.3 CTP.
8. Pro Visual Studio 'New Item' integration Uses Solution Explorer Project Context Menu for deployment commands Integrates with SharePoint Installer Options for deployment Cons Uses WSPBuilder.exe to execute deployments in Visual Studio Cannot extend WSPBuilder actions (e.g. what happens when you Deploy, Upgrade, Uninstall) Generated files stored in bin directory No integrated view into wsp WSPBuilder required to open VS solution No visibility to status of deployment in IDE WSPBuilder
10. Pros Wizard based approach 12 hive structure based Leverages MSBuild actions Not required to open a VS solution Generated files stored in DeploymentFiles folder and not bin Good visibility via output window in IDE on status of deployment Cons Solution creation wizard outside of IDE Projects reliant on VS solution Not frequently updated STSDev 1.3
11. STSDev 1.3 Demo: See how to create a web part solution with STSDev 1.3.
12. Unit Testing Difficult to say the least, but doesn’t mean it cannot or should not be done. Lack of public constructors on key classes makes them unmockable thus developers will need to write integration tests instead of unit tests. Because end users can change lists in production, you must write more tests to account for your data changing and validate once solid assumptions. Key classes such as SPList are marked final thus developers cannot create strongly typed entities and therefore must encapsulate them for tests.
13. What Does the Future Hold? Will SharePoint development become a first class citizen with the release of SharePoint 2010 and VisualStudio 2010?
26. Contact Me Snap bar code below to download my vCard to your mobile phone Visit http://www.microsoft.com/tag for more information
Hinweis der Redaktion
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.
