Course info
Jun 19, 2012
2h 1m

This course walks through how some basic and some advanced Visual Studio tools can be enhanced by integrating them into Team Foundation Server. As they tools are integrated, how the team uses the tools changes, especially due to the increased communication between team members. This course will show how to perform the integration and some of the benefits of the integration of Visual Studio and Team Foundation Server.

About the author
About the author

John Brown is a Software Craftsman continually looking for intuitive designs, agile architectures, and streamlined processes. With degrees in Computer Science from Johns Hopkins and Aerospace Engineering from Purdue, John is always up for a challenge, especially in his areas of interest in Artificial Intelligence and Machine Learning.

More from the author
Build Excel Add-ins with Office JS APIs
2h 16m
Apr 5, 2017
Ghost Blogging Engine: First Look
3h 32m
Mar 14, 2016
More courses by John Brown
Section Introduction Transcripts
Section Introduction Transcripts

Integrating Visual Studio and Team Foundation Server
Hello. This is John Brown and welcome to this module on integrating Visual Studio and Team Foundation Server. In this course, we're going to look at the advantages of including Team Foundation Server in your overall development environment. In this course, we'll specifically talk about why we would want to start moving some of these features from visual studio to Team Foundation Server. Visual Studio is made up of a lot of different features. Many of those features can provide quite a lot of value to the development process. With Visual Studio, we can do things like create setup projects, we can immigrate with MSDN. There are extensions to Visual Studio. We can perform debugging tasks. We can perform profiling and unit testing, static analysis, architectural tools, IntelliTrace. The developers have access to code coverage. We can perform load testing, analyze that test impact. We can even develop for mobile platforms and we can perform modeling. We also have access to things like coded UI test and lab management. Visual Studio is a rich environment but it is only one piece of a larger puzzle. Visual Studio is actually made up of a larger family called the Visual Studio Family. As we can see from this diagram, Visual Studio plays a central role and it has multiple, different skews providing value. We have the professional, the premium, the ultimate skews that provide the developer tools. We have the test professional also under the Visual Studio names face. In addition, we also have additional things, such as share point, expression and the expression tools, Microsoft Office, the Team Explorer and the Team web access, all providing the external client facing tools that work through the process template to provide that project management, requirements management version control, test case management, build automation and reporting that provide a cohesive end to end application life cycle management tool suite. And recently they've added the lab management that allows us to even extend that further. What we'll see though, is that each of these tools are very valuable on their own but because Visual Studio is part of a larger group of systems here, some of the features of Visual Studio can integrate into TFS and really help share the information among all the team members and all of the different clients that are available. Sharing of data is one of the key features of Team Foundation Server.

Integrating Visual Studio Developer Tools and Team Foundation Server
Hello, this is John Brown and welcome to this module on Integrating Visual Studio Development Tools with Team Foundation Server. In this module, we will review how to enhance the tools that we have available by integrating them in Team Foundation Server for extra communications. In this module, we'll look at how the development tools integrate with Team Foundation Server. We'll see how we can take the unit test that we have written to validate our code in Visual Studio can be transformed and executed as part of the build process. From there, we can see the test impact analysis and some of the build reports in the Team Foundation Server reports, we'll also be able to see how the code coverage and the code analysis both can be transformed over into the build process and surface in those same reports.

Integrating Visual Studio Testing Tools and Team Foundation Server
Hello, this is John Brown and welcome to this module on Integrating Visual Studio Testing Tools with Team Foundation Server. In this module, we'll review how the Testing Tools integrate with Visual Studio and Team Foundation Server. We'll cover manual tests and how we can send back the information from the manual test through Team Foundation Server and aggregate the data. We'll show how through the manual testing process, we can capture IntelliTrace and video files, and provide those files to the developers to help trace down what happened during a failed test. We'll also show how to enable the test impact analysis so that we can understand which manual tests need to be rerun based on changes to the code. We'll also see how to run the automated test called Coded UI Tests and see how those integrate into the overall testing process. And finally, we'll surf some of the code coverage of the testing tools back into Visual Studio so that we can really understand what areas of the code are being tested by the test that we have run in both manual and Coded UI Tests. ( Pause )

Integrating Visual Studio Architecture Tools and Team Foundation Server
( Silence ) John Brown: Hello. This is John Brown, and welcome to this module on integrating Visual Studio architecture tools with Team Foundation Server. If we look at the role of the architect, the architect really needs to look at a system holistically. He's making sure that all the parts and pieces are working together. As part of that, he will pursue quality at every chance. He'll check to see if the code is of the quality that we are striving to meet. Is the team following the architectural rules? In fact, what he will do is often coordinate and integrate activities of the developers because it is not just a one-person effort. There's often lots of moving parts that we need to track and integrate. And during that time, he will look to see if we can create efficiencies within the development process. He'll look to make sure that the environment is completely portable and movable from one development machine to another so we can quickly and easily add new members to the team and have them be productive. In this module, we're going to look at how we can analyze the code from an architectural perspective through code metrics and layered diagrams and integrate that in the Team Foundation Server process so we can share all of that information with all the team members. We're also going to look at how the architect can help coordinate the work through UML diagrams and work items attach directly to those UML diagrams so we can share the vision of the architecture and the specific work with all the team members. At the same time we're also going to look at how we can improve our development efficiencies by integrating the development of database projects directly within our solution, and as part of the build process of Team Foundation Server.