You need to streamline the processfor debugging prior versions of your library

Your network environment includes a Microsoft Visual Studio Team Foundation Server (TFS) 2012 server.
Developers use Visual Studio 2012 to maintain a library of commercial .NET components provided for sale by
your company. You release new versions quarterly and provide support for the four most recent versions.
When issues are logged with previous versions it istime-consuming for your developers to locate and
associate the correct version of debugging symbols and source code. You need to streamline the processfor
debugging prior versions of your library. What should you do?

Your network environment includes a Microsoft Visual Studio Team Foundation Server (TFS) 2012 server.
Developers use Visual Studio 2012 to maintain a library of commercial .NET components provided for sale by
your company. You release new versions quarterly and provide support for the four most recent versions.
When issues are logged with previous versions it istime-consuming for your developers to locate and
associate the correct version of debugging symbols and source code. You need to streamline the processfor
debugging prior versions of your library. What should you do?

A.
When it is time to deploy each quarterly update, copy the release binaries into version control.

B.
Within the build definition, set the Index Sources property to True and provide a path for the symbols. Add
this path to the list of symbol file locations in Visual Studio when debugging that particular version.

C.
When it is time to deploy each quarterly update, label the source code with the version number being
released.

D.
Enable IntelliTrace within Visual Studio. Within the build definition, set the IntelliTrace option to True.



Leave a Reply 1

Your email address will not be published. Required fields are marked *