solution as the topLevel of  
Author Message
Jonathan Cran





PostPosted: Team Foundation Server - Version Control, solution as the topLevel of Top

I was wondering if i could create a pure 'folder' in team system version control in which to throw documents, schemas, workflows, etc. My current understanding is that you need to create an empty solution file, then a folder containing the documents underneath. -- is this correct is there way to do this w/o creating the solution file

if not, i'm leaning toward using sharepoint for these sorts of items, which may be what the designers intended

thanks!



Visual Studio Team System44  
 
 
Michal Malecki





PostPosted: Team Foundation Server - Version Control, solution as the topLevel of Top

Hello,

You can add any documents to Version Control directly, using Source Control Explorer. The scenario you described is true if you want to use Solution Explorer (which seems a little awkward for me).

However, Sharepoint has many advantages as store of the documents, so you can still decide to use it.



 
 
Richard Berg MSFT





PostPosted: Team Foundation Server - Version Control, solution as the topLevel of Top

Yes -- unlike many systems, folders are first-class items in TFS source control. You can add/delete/rename/undelete empty folders directly from Source Control Explorer or the command line. Like Michal said, doing it from Solution Explorer would be very awkward if not impossible.
 
 
j.cran





PostPosted: Team Foundation Server - Version Control, solution as the topLevel of Top

thanks for the reply. maybe i'm misunderstanding.... i can't seem to make this happen. i'm trying to drag & drop, right-click, everything i can think of from within Source Control Explorer, but no luck. can you give a bit more detail -- maybe a step by step


 
 
Richard Berg MSFT





PostPosted: Team Foundation Server - Version Control, solution as the topLevel of Top

1) navigate to a mapped folder (text not greyed out)
2) rightclick -> new folder *or* click the new folder button (SCE toolbar, 3rd from the left)
3) repeat for other folders
4) checkin

 
 
j.cran





PostPosted: Team Foundation Server - Version Control, solution as the topLevel of Top

ah, the folders were not mapped, so they were greyed out. thanks!


 
 
Chad Hinton





PostPosted: Team Foundation Server - Version Control, solution as the topLevel of Top

I have a related question. How would one make the top-level entities in the Source Control Explorer not be soltions/projects. I would like to create a hierarchy of projects in a nice directory structure, something along the line of:

Customer1

\project 1

\project 2

Customer2

\project 1

\project 2

etc. It appears that there is not a facility to manage my projects as a hierarcy but rather as a simple list.

Thanks

Chad


 
 
Michal Malecki





PostPosted: Team Foundation Server - Version Control, solution as the topLevel of Top

Hello,

top level entities in the version control must be Team Projects. They are really croase grain and you want create a new one only if for new customer (if they are the top level dividers) you want to have new checkin notes, work item queries, another policies etc

Under the team projects you have freedom how to organize your projects, it all depends on your workspace mappings. The easiest way is probably to map team project (let say $/tp1) to root directory (c:\projects). Then structure on the local drive will be mirrored under $/tp1.

Hope this helps



 
 
Richard Berg MSFT





PostPosted: Team Foundation Server - Version Control, solution as the topLevel of Top

I don’t see any reason why you can’t do that. We have thousands of
solutions/projects in our Team Project organized by feature team and a
few other criteria. Have you tried What problems did you encounter

 
 
Chad Hinton





PostPosted: Team Foundation Server - Version Control, solution as the topLevel of Top

I've been working to establish new standards that work well in this new environment and basing my thoughts on some relatively limited first-hand experience with VSTS. I have an existing CVS repository that will be migrated to VSTS. All future development (for the forseen future) will be in VS. Given this I am attempting to predict what errors and difficulties I will create for myself and staff with these implementation details.

We are currently leaning toward a main Team Project and related source tree for each customer. Each customer project becoming a Team Project that the source is branched off of the main Team Project. Once the project is completed, it would be merged back into the main Team Project. It seems that support activities would need to be performed in the main Team Project with many source tree branches/merges.

The main concern that I'm left with is I will have an ever increasing number of projects in my Team Explorer with no good way to organize it short of a naming convention for the projects. I don't see how you view your team projects by feature or other criteria as you express in 'Team Project organized by feature team and a
few other criteria'. It seems that I am just given a list of the Team Projects in alpha order.


I hope I'm making sense to somebody other than myself....

Chad