If I recall,moving stuff around in TFS was/is a major PITA, but I haven't done anything like that in a couple of years and even though I had *some* admin rights, I never really did much admin-wise on TFS. I would frequently get stuck trying to do something and had to ask the "uber-admin" to take care of it for me. And, since that was a few years ago and a different company, I don't know if I can recall all the details. I'm currently still using TFS (I think it's still 2008, even though I'm using VS2010), but we have only one simple app on there currently.

I'm still not clear on the structure you're trying to set up (change to). Source Safe allowed sharing, TFS does not ... the sharing sure made things easy. However, you *can* do something similar by using "Add as Link" for any "shared" items that you add to your solution projects in Visual Studio. Unfortunately, "Add as Link" only works for adding existing items (classes) to a project, you can't add an entire project that way ... that's pretty limiting actually. It's not any different in VS2010 either ... darn!

Anyway, as I said, I'm not sure I understand the structure you have vs the structure you want to have ... both on TFS and in your solutions. Can you elaborate some more? Sorry ... =0(

~~Bonnie





>>And what exactly do you mean by "sub-project"? How would this be represented in your Solution? AFAIK, you can't have sub-projects of a project (your .csproj or .vbproj), unless I am hopelessly behind the times <g>.
>>
>>~~Bonnie
>>
>>
>
>I guess in TFS terms it would be more like an 'area'.
>
>We have an application (lots of them, actually) that consists of mobile, web, and map (esri) projects. The projects in the collection are currently distinct. We would like to group them together w/o having to create a new collection (this was the way we did it in SourceSafe).
>
>When we migrated to TFS we split everything into distinct projects grouped at the collection level by customer, but this will get unwieldy fairly quickly when customers have lots of related projects. Naming convention helps, but it seems like TFS really lacks organizational capabilities.
>
>
>>
>>>(I think we could do with a Team Foundation Server Category by the way)
>>>
>>>Using TSF2010. We have a project in a collection that really should be a SUB-project of one of the other projects of that collection.
>>>
>>>So far, all I see for moving projects is the (complicated) ability to split a project.
>>>
>>>Is there a way to simply or not so simply make an existing project into a sub-project of (move it under) another project?