1. Extensibility

2. Extending VSTS VSTE for Software Architects VSTE for Software Developers VSTE for Software Testers Team Foundation Sever

3. Extending VSTS VSTE for Software Architects SDK Modeling Integration

4. Extending Team Architect Extensibility SDK Support the ability to add new SDM resources as additional properties on any logical server or application Associate with any existing types Fully constrainable Generic logical servers and applications Prototypes Support the ability to define new SDM types New system definitions New endpoints New relationships New constraints

5. Extensibility SDK Why… Model and visualize “other aspects” of a distributed system What you do… Add new application definitions to the Application Designer Add new host definitions to the Logical Data Center Designer Model new endpoint types Create new communication, and hosting relationships Add custom constraints to new or existing definitions Extend existing definitions with new meta-data What you get… Integration with existing drag-drop-connect metaphor Integration with existing user experience for settings and constraints Integration with existing validation experience Integration with existing user experience for deployment validation

6. Creating Generic Server Extending Application Diagram

7. Extending VSTS VSTE for Software Developers Code Analysis Check In policies Source Control Build

8. Extending Code Analysis You can import existing FXCop rules into VSTS Place you FXCop rule assemblies alongside current VSTS ones They will appear in the VS IDE Target file can be found at C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\CodeAnaly sis

9. Check-in Policies Mechanism for validating source changes prior to check-in Evaluated on the client Not a security mechanism Extensible via policy plug-ins.NET managed assemblies IPolicyDefinition – define a check-in policy IPolicyEvaluation – evaluate policy compliance

10. Extending Team Build Augment Team Build process MSBuild tasks Use Team Build store in your existing build process Team Build Web Services Build lab scenarios Command-line tools

11. Custom Check-in Policy

12. Extending VSTS VSTE for Software Testers Validators Testing Types GenericCustom

13. Extensibility Paths Validation Rules Defining custom validations for web application and web service testing. Generic Type – Lightweight solution Integrate tools into Visual Studio using metadata and loose inter-process integration. Take advantage of basic Test features. 3 rd Party Type – Heavyweight solution Programmatically integrate tools into Visual Studio with tight API-level integration. Take advantage of all Test features.

14. Custom Editor / Wizard Test Items Management UI General Results View Custom Detailed Results View Generics Test Type Hook into Run Config Settings Config Settings Context-sensitive Right-click Commands Complete Control of Test Item Execution

15. Generic Tests What’s good Quick lightweight integration method Test tools run unmodified Take advantage of basic Test features Manage and execute tests your tools in the new Test environment View basic test results

16. Generic Tests What’s missing? Authoring experience limited Cannot have custom editor or wizard No named test type Constraints on receiving results No real-time results feedback Deployment is not as robust as a custom type Results Viewing limited Not a fully-featured custom viewer

17. Extending Test Case Types Custom types and custom adaptors to fully extend test authoring and execution 3 General Extension Points Authoring experience extensions Execution adaptor and metadata extensions Results plug-in

18. Test Authoring Test Case Types: Extensibility VS types can be extended to include your type Offers first class test type Used internally to create test types Visual Studio Test Type Interfaces MS Test Types VSIP Test Types Editor Editor

19. Test Results Test Case Types: Extensibility Result summary information extensible Pass, Fail Complete, Incomplete Results viewer provides events and UI Area Summary visible by default (Pass \ Fail) Details available by test type on double-click

20. Custom Validation Generic Testing

21. Extending VSTS Team Foundation Server Architecture (Technical & Conceptual) Extending Team Foundation Process Methodology Work Item Editing Working with events

22. Technical Architecture Win 2000 (>=SP4) Win XP (>=SP2) Win 2003 Server (>=SP1).Net FX 2.0 Microsoft Office 11 – SP1 MDAC 9.0 Internet Explorer 6.0 – SP1 Visual Studio 2005 Team Explorer Win 2003 Server ASP.Net / IIS 6.0 Win 2003 Server SQL Server 2005 Win XP (>=SP2) Win 2003 Server (>=SP1).Net FX 2.0 MDAC Win 2003 Server ASP.Net / IIS 6.0 Maximally factored configuration

23. Custom reporting tools MS Excel Technical Architecture Team Foundation Data Tier Team Foundation App Tier Version Control Proxy Report Client Team Foundation Client Tier CoreDataVersionControl Work Items Team Build Data SQLReportingServicesWindowsSharePointServicesSQLReportingServicesWindowsSharePointServices Work Item TrackingServiceVersionControlServiceTeamBuildServiceCoreServicesWarehouse Adapters Team Foundation App TierWSSProxies SQL RS Proxies Team Foundation Object Model MS Excel Plug-In MS Project Plug-In Visual Studio Packages Internet Explorer BuildProcessVersionControlProxyService VSTF Clients of VSTF VSTF Adjuncts Build Machine

24. Meta Data Repositories Work Items TestsTests SourceCodeSourceCode BuildConfigsBuildConfigs ThirdPartyToolThirdPartyTool

25. ProjectStructureProjectStructure IterationStructureIterationStructure TestResultsTestResults BuildBuild LabelLabel VersionedItemVersionedItem LatestItemVersionLatestItemVersion ChangesetChangesetWorkItemWorkItem TFS “Virtual Repository” Version Control Core Data Work Items Team Build TFS Enablement * ******** * * * * ProjectStructureProjectStructureIterationStructureIterationStructure WorkItemWorkItem LabelLabelVersionedItemVersionedItem LatestItemVersionLatestItemVersionChangesetChangeset BuildBuildTestResultTestResult

26. TeamFoundationServer Team Foundation Core Services Team foundation core services LinkingServiceUserGroupsServiceNotificationServiceRegistrationServiceCommonStructureService Team Foundation Object Model VisualStudioIDE External tool (Partner or MS) VersionControl IntegrationInterface WorkItems IntegrationInterface Team Build IntegrationInterface

27. Customization vs. Extension Customization: What?Tailor Team Foundation to your environment Who? End users, project managers Why?Adjust basic Team Foundation capabilities to your needs How?Config through UI, author XML, maybe some automation Extension/Integration What?Add new functionality to Team Foundation Who?Partners, internal IT orgs Why?Deeply integrate complementary features into the Team Foundation platform How?WS development, database development, VSIP integration, etc.

28. Example Customizations Process Template Modify / clone ours Build your own Work Item Types Modify ours Build your own Automate using WIOM Source Code Control Select policies to enforce Reporting Modify our SQL RS reports Add your own SQL RS reports Use a different reporting tool (Excel, OWC, …) Project Portal Customize the template Add your own libraries

29. TFS Customization Process Methodology Work item editing

30. Example Extensions Core services Add a new tool with new artifact types, link types, database, WS’s Link to other tools’ artifacts Raise, subscribe to events Integrate into Team Explorer Add pages to Project Creation Wizard Work Item Tracking Write against OM Respond to events Link to Work Items Integrate with WI Picker Source Control Write against OM Add new file type support (keyword expansion, diff/merge) Participate in integrated check-in Define new policie Respond to events Reporting Extend warehouse Portal Build new web parts Build Add new Build tasks

31. Scenario Take Order Extensibility Sample Work item spawning Task Take Order: Write Spec Task Take Order: Test Plan Task Take Order: UI Design Task Take Order: Dev Schedule

32. Extensibility Sample Work item spawning Scenario Take Order Task Take Order: Write Spec Task Take Order: Test Plan Task Take Order: UI Design Task Take Order: Dev Schedule Listen for WorkItemChanged event for new Scenario.Listen for WorkItemChanged event for new Scenario. Use work item object model to create new TasksUse work item object model to create new Tasks Use work item object model to link new Tasks to original ScenarioUse work item object model to link new Tasks to original Scenario Listen for WorkItemChanged event for new Scenario.Listen for WorkItemChanged event for new Scenario. Use work item object model to create new TasksUse work item object model to create new Tasks Use work item object model to link new Tasks to original ScenarioUse work item object model to link new Tasks to original Scenario Listen for WorkItemChanged event for Completed Task.Listen for WorkItemChanged event for Completed Task. Use work item object model to update parent ScenarioUse work item object model to update parent Scenario Listen for WorkItemChanged event for Completed Task.Listen for WorkItemChanged event for Completed Task. Use work item object model to update parent ScenarioUse work item object model to update parent Scenario

33. Registering and Subscribing RegistrationAPISubscriptionAPI At setup time, a tool registers the types of events it will raise. TFS Work Item Tracking raises a WorkItemChanged Event Another tool may subscribe to receive events of that type when they are raised. We’ll use a utility that is delivered with Team Foundation. subscribesubscribe unsubscribeunsubscribe TFS Work Item Tracking SpawnDemo EventTypesSubs

34. Raising an Event EventTypes Subs TFS Event Engine Subs Events matched to subscriptions Demo “WorkItemSpawn” WS invoked. TFS Event Client fireAsyncEventfireAsyncEvent callback method specified in subscribe callcallback method specified in subscribe call Rules Processor Events matched to subscriptions TFS Work Item Tracking raises a WorkItemChanged Event TFS Work Item Tracking SpawnDemo

35. Work Item Spawning

36. © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.