Filter
Top Products
– Port Address
v Component
v Release
v WorkArea
You also need to know the project name. The project name is used by your
development tool to relate to the TeamConnection attributes of family, release, work
area, and component by the Source Code Control DLL.
Opening a project
One of the few differences you see when using TeamConnection as your source code
control provider occurs when you open or save a project (depending on the IDE you are
using). When you open or save the new project, the TeamConnection Settings
window opens. At the top of this window is a field with your development project name.
In addition to the project name field, there are fields for family attributes, work area,
release, and component. If this is a new project, these fields are blank. If this is not a
new project, the fields contain the previous values. You can change these values only
when this window is open. If at anytime you decide to change any of these values, you
might need to first close the project and reopen it.
Once all the fields are filled in, select OK. The project will open. If you select Cancel,
the source code control system might disconnect from the development environment
until another project is opened.
Under some versions of Visual Basic, for example, projects automatically close and
open after certain operations. This causes this TeamConnection Settings window to
open at times when it may appear unnecessary. When this occurs, select OK.Ifyou
select Cancel, you might be in a state that requires shutting down and restarting Visual
Basic to reconnect the source code control system.
Integrated features
Once you open a project you can use the integrated features of the development
environment to access your files in TeamConnection. The development environment
keeps track of the files that are known to TeamConnection, and the checkout status of
each file. For example, the development environment keeps track of files checked out
to other users.
The exact steps necessary to perform each of the following actions depend on the
development environment being used. However, for a given IDE, the steps are the
same regardless of the source code control provider. For example, if you check out a
file in the Visual C++ development environment when it is connected to Visual
SourceSafe, the steps you use are exactly the steps you use when Visual C++ is
connected to TeamConnection.
270 User’s Guide