Mechanism to create a source control folder without creating a Project?

Hot Topic

How does the test pick up values from List Boxes
Error message for December CTP - Error 28925.TFServerStatusValidator: UnexpectedError
Project Creation Problem: Unable to connect to the Windows SharePoint Services
Remote access to TFS
Email Alerts in Workgroup mode
LIB/INCLUDE Settings for C++ Builds
Best Pracices for concurrent development.
problem with public nested class
Unassociate mpp with a team project
SystemDefinitionModel and Databases

VS Team System

Team Build Failure (test execution) with IBM.Data.DB2
Problems installing TFS Beta 3 Refresh
TFSB3r security issue
Change Management and Deployment features
Calling Declarative Tests
Code coverage / signed assemblies / unit tests fail
Best Pracices for concurrent development.
TFS in a workgroup
Large solution performance (Was: Useless output from TFS source control)
Profiler quits generating reports (or gets stuck on the same one)

Mechanism to create a source control folder without creating a Project?

Is there a mechanism to create a source code control folder without first creating a Team Project in Team Foundation Server Beta 3 Refresh

I suspect perhaps via the command line




Answer this question

Mechanism to create a source control folder without creating a Project?

  • Eliyas Yakub

    No, all root level folders must correspond to Team Projects.  You can create folders under them at will.  This was a controversial design decision and one we may reverse in a future version if we get a lot of feedback that it is too problematic.

    Brian

  • Robert Hemmings

    Put me down as thinking it's a bad idea. We are considering using TFS and its version control, but we have needs for version control beyond just MS technology. (Imagine! ;-) I'll probably be asking about this in a new thread after I finish checking out these existing ones, but this answer doesn't bode well for the answer I'd be hoping for.

  • Kalim_a

    Good to know. Thanks for the info. I'll withhold any judgement at the moment. I am torn as well on if it's a good thing or not

    But good to have the information.

    Thanks,


  • Echo_94

    Ditto thinking this is short-sided.  I think there are several things like this where there is failure to see the forest through the trees - like not being able to browse to a document outside the tree when adding to source control, not being able to automatically get the latest version of a document upon checkout, not being able to do a 1-click checkout and edit.  Why make all these deviations from VSS from how many of us have been using it  It should do everything VSS does and more - not less and at many times the price!

  • migueldc01

    What you use the folder for should be orthogonal - we have customers that create a team project and then stuff the folder full of Java projects and do their check-out's and check-in's via Eclipse.  Can you explain in more detail your scenario

    Creating a team project should be a relatively quick operation (a few minutes), and once the team project has been created, you can use the source control for whatever purpose you want.

  • Mechanism to create a source control folder without creating a Project?
Answer this question