• We discussed the primary audience for this course and what we will cover.
• We also explored the entire Visual Studio Team System at a high level to understand get a grasp of the
architecture and the basic capabilities of VSTS.
• Microsoft created the Dynamic Systems Initiative (DSI) to resolve the costs and complications endured
from developing, deploying and maintaining software from its development to its move to production.
- DSI was created to increase communication between developers and IT managers, such as:
Deployment rules and constraints for the IT department.
Runtime information (logs, performance metrics, bugs, application restarts) from production back to
the developers.
• Visual Studio 2005 Team Edition for Software Architects (Team Architect) is Microsoft’s first phase in
addressing the DSI initiative.
• Team Architect offers four different Distributed System Designers (DSDs) that are used to create their
associated diagrams:
- Application Designer (*.ad)
- System Designer (*.sd)
- Logical Datacenter Designer (*.ldd)
- Deployment Designer (*.dd)
• Team Architect automatically synchronizes the projects with their associated diagrams.
• Almost all versions of Visual Studio 2005 (Standard and up) include the Class Designer for two
purposes:
- To aid in developing types using diagrams for a better visual understanding.
- To help developers and testers comprehend the existing architecture and collaboration between a
project’s types.
• Team Developer includes support for Unit testing, which can be used in conjunction with Test Driven
Development (TDD) and Code Coverage.
- Unit testing is the process of testing individual methods or properties. Visual Studio can create the
initial project with empty (stubbed) functions for testing them.
- Test Driven Development is the process of creating the tests before developing the actual methods that
need to be tested.
- Code Coverage is a tool in Visual Studio that gives the developer a visual color-coded suggestion as to
the percentage of code that is being Unit tested.
• The Code Profiler can be used to identify performance bottlenecks within a given solution.
- Sampling is performed first to identify the project that is causing performance issues. Instrumentation
is used to identify the troublesome methods within a given project (assembly).
• Application Verifier is a tool used with unmanaged code (C, C++, and Assembly) to identify heap
corruption, handle mismanagement and critical section usage for multithreaded applications.
• Microsoft has finally recognized that quality software comes from quality testing and good testing
comes with good testing tools.
• Team Tester supports eight different types of tests
- Unit, Database unit, Load, Ordered, Generic, Manual (Word), Manual (text) and web.
• Test Manager is only available in Team Tester.
- Test View, unit testing and code coverage are available in Team Tester and Team Developer (and Team
Suite, of course!)
• Team Tester supports a huge Testing API that programmers can take advantage of.
- A book could easily be written just on all the programmable APIs and capabilities of Team Tester.
• Load tests offer far more scalability and flexibility than the web stress tool, Application Center Test
(ACT), released with the Enterprise editions of Visual Studio 2003.
• A separate load testing tool, Team Test Load Agent, is available to load testing client/server
applications on an intranet/extranet environment.
- This tool must be purchased separately from Microsoft; sadly, it’s not available with an MSDN
subscription.
• Microsoft created Team DB Pro to allow database developers to create agile data solutions in much the
same techniques as used in software development.
- An offline database representation is used for database object manipulation and testing.
- The database project can be added to source control and versioned.
- Database objects can be refactored (renamed) throughout a project.
• Team DB Pro only works SQL Server 2000 and SQL Server 2005.
- Optionally, you can use a wizard to get the initial project started.
• Team DB Pro is not necessarily for database administrators.
- It was designed with the database developer in mind.
• Team DB Pro needs access to at least one SQL Server 2005 database in order to run properly.
- SQL Server 2005 Express will suffice.
• TF (Team Foundation) is the largest part of VSTS (Visual Studio Team System).
- TFS (Team Foundation Server) is the largest part of TF.
- The other three parts of TF are Excel, Project and Team Explorer.
• Installing TFS is an arduous task that should follow the latest TFS installation documentation explicitly.
- Decisions about physical architecture need to be made based on the number of users and their proximity
to the TFS server.
• Installing Team Explorer and connecting to TFS can be troublesome.
- Important tips must be followed for a connection to be successful.
• Service Packs must be installed in the proper order to receive highest potential for performance and
security.
- Installing TFS Build or TFS Proxy requires the original TFS installation media.
- It also requires TFS SP1 to be installed afterward.
• This was a big chapter describing all the different parts of a Team project.
- Creating a project is only possible through the wizard in Team Explorer.
• The Team Explorer is the nexus of a Team project, exposing all parts to the user.
- Favorite queries, report and documents can be accessed off the Favorites node.
- Experienced project managers may want to use Excel or Project for a user interface.
• Security is controlled at the Global TFS level and at the Team project level.
- It involves assigning permissions to users and groups and assigning membership to groups.
• TFS Source Control is what ties Team projects to Visual Studio projects.
- Dividing and merging Team projects is not as painful as you might think.
• We also explored the entire Visual Studio Team System at a high level to understand get a grasp of the
architecture and the basic capabilities of VSTS.
• Microsoft created the Dynamic Systems Initiative (DSI) to resolve the costs and complications endured
from developing, deploying and maintaining software from its development to its move to production.
- DSI was created to increase communication between developers and IT managers, such as:
Deployment rules and constraints for the IT department.
Runtime information (logs, performance metrics, bugs, application restarts) from production back to
the developers.
• Visual Studio 2005 Team Edition for Software Architects (Team Architect) is Microsoft’s first phase in
addressing the DSI initiative.
• Team Architect offers four different Distributed System Designers (DSDs) that are used to create their
associated diagrams:
- Application Designer (*.ad)
- System Designer (*.sd)
- Logical Datacenter Designer (*.ldd)
- Deployment Designer (*.dd)
• Team Architect automatically synchronizes the projects with their associated diagrams.
• Almost all versions of Visual Studio 2005 (Standard and up) include the Class Designer for two
purposes:
- To aid in developing types using diagrams for a better visual understanding.
- To help developers and testers comprehend the existing architecture and collaboration between a
project’s types.
• Team Developer includes support for Unit testing, which can be used in conjunction with Test Driven
Development (TDD) and Code Coverage.
- Unit testing is the process of testing individual methods or properties. Visual Studio can create the
initial project with empty (stubbed) functions for testing them.
- Test Driven Development is the process of creating the tests before developing the actual methods that
need to be tested.
- Code Coverage is a tool in Visual Studio that gives the developer a visual color-coded suggestion as to
the percentage of code that is being Unit tested.
• The Code Profiler can be used to identify performance bottlenecks within a given solution.
- Sampling is performed first to identify the project that is causing performance issues. Instrumentation
is used to identify the troublesome methods within a given project (assembly).
• Application Verifier is a tool used with unmanaged code (C, C++, and Assembly) to identify heap
corruption, handle mismanagement and critical section usage for multithreaded applications.
• Microsoft has finally recognized that quality software comes from quality testing and good testing
comes with good testing tools.
• Team Tester supports eight different types of tests
- Unit, Database unit, Load, Ordered, Generic, Manual (Word), Manual (text) and web.
• Test Manager is only available in Team Tester.
- Test View, unit testing and code coverage are available in Team Tester and Team Developer (and Team
Suite, of course!)
• Team Tester supports a huge Testing API that programmers can take advantage of.
- A book could easily be written just on all the programmable APIs and capabilities of Team Tester.
• Load tests offer far more scalability and flexibility than the web stress tool, Application Center Test
(ACT), released with the Enterprise editions of Visual Studio 2003.
• A separate load testing tool, Team Test Load Agent, is available to load testing client/server
applications on an intranet/extranet environment.
- This tool must be purchased separately from Microsoft; sadly, it’s not available with an MSDN
subscription.
• Microsoft created Team DB Pro to allow database developers to create agile data solutions in much the
same techniques as used in software development.
- An offline database representation is used for database object manipulation and testing.
- The database project can be added to source control and versioned.
- Database objects can be refactored (renamed) throughout a project.
• Team DB Pro only works SQL Server 2000 and SQL Server 2005.
- Optionally, you can use a wizard to get the initial project started.
• Team DB Pro is not necessarily for database administrators.
- It was designed with the database developer in mind.
• Team DB Pro needs access to at least one SQL Server 2005 database in order to run properly.
- SQL Server 2005 Express will suffice.
• TF (Team Foundation) is the largest part of VSTS (Visual Studio Team System).
- TFS (Team Foundation Server) is the largest part of TF.
- The other three parts of TF are Excel, Project and Team Explorer.
• Installing TFS is an arduous task that should follow the latest TFS installation documentation explicitly.
- Decisions about physical architecture need to be made based on the number of users and their proximity
to the TFS server.
• Installing Team Explorer and connecting to TFS can be troublesome.
- Important tips must be followed for a connection to be successful.
• Service Packs must be installed in the proper order to receive highest potential for performance and
security.
- Installing TFS Build or TFS Proxy requires the original TFS installation media.
- It also requires TFS SP1 to be installed afterward.
• This was a big chapter describing all the different parts of a Team project.
- Creating a project is only possible through the wizard in Team Explorer.
• The Team Explorer is the nexus of a Team project, exposing all parts to the user.
- Favorite queries, report and documents can be accessed off the Favorites node.
- Experienced project managers may want to use Excel or Project for a user interface.
• Security is controlled at the Global TFS level and at the Team project level.
- It involves assigning permissions to users and groups and assigning membership to groups.
• TFS Source Control is what ties Team projects to Visual Studio projects.
- Dividing and merging Team projects is not as painful as you might think.
VSTS Tutorial Summary
Table of Contents
Copyright (c) 2008. Intertech, Inc. All Rights Reserved. This information is to be used exclusively as an
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
Courseware
Training Resources
Tutorials