Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / General / May 2006

Tip: Looking for answers? Try searching our database.

Team Explorer / TFS Newbie Help

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
quortex@hotmail.com - 23 May 2006 09:08 GMT
Hi all,

I have got Team Foundation Server up and running and have to say I am
very impressed. I have a couple of questions however which I am sure
will have simple answers:

A)  Solution Management

I have a decent sized solution (32 projects) which I have checked into
the repository.  Other users who need to use the entire solution can
obviously do so by simply opening the .sln file and then the projects
are imported into their workspace.

However a lot of the time people do not need (or want) all of these
projects on their machine. They would just want to pull down the
projects that they are working with along with any referenced projects
not necessarily the whole solution.  What is the best way to achieve
this? I have had a play and looked online and there doesn't seem to be
a simple answer.  Any guidelines or thoughts would be appreciated.

Also is it possible that when projects are pulled down the other
projects they reference remain on the repository? i.e. a project
reference located in the repository. I can understand if this is not
possible as it would make sense if that doesn't work.

B) To branch or not to branch...

Is it recommended for each of my colleagues to work with their own
branch and when they are happy with their code merge it with the main
trunk?  Or is it best to just to all work on the same and check in at
the end of each day for nightly builds?

Sorry for the stupid questions ;) Thanks in advance for your
assistance.

Kind Regards,
Mark

Note: I have reposted this from microsoft.public.vsnet.general as I
didn't get a response...
Constantine - 29 May 2006 14:29 GMT
Hi Mark,

1. You can setup filtering on your workspace to determine what to copy and
what not from FS.
2. Branching for individual developers is always better solution as
developers can commit their changes at the end of the day into their own
areas. This approach is better than shelfing. It supports history and
everyone can track all changes in repository. You can impose a stricter
policy on merging to a "integration" branch.

Cheers,
Constantine

> Hi all,
>
[quoted text clipped - 36 lines]
> Note: I have reposted this from microsoft.public.vsnet.general as I
> didn't get a response...

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.