Problems with Source Code Control

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • TC

    #1

    Problems with Source Code Control

    I'm using Visual Studio 2005 with SourceGear Vault. I'm having trouble
    with the integrated source code control features. I think the problem
    is entirely with Visual Studio, not Vault.

    First, let me say that I think the integrated source control features
    are wonderful. They work great, except when they don't work at all.
    Unfortunately, they don't work every time I need them, so I've had to
    turn them off completely.

    The trouble is with setup projects. I just can't bind my setup projects
    to the repository. I get a variety of symptoms. Sometimes, it binds the
    project to the correct folder, but reports the binding as "invalid".
    Sometimes, it binds the project to the wrong folder and reports the
    binding as "invalid". And sometimes it gives me an error.

    "The folder you chose is not a valid binding root for the projects you
    have selected. You attempted to retarget a solution to a source control
    folder that is not within the solution's root. In the change source
    control dialog box, specify the root for the solution. Select the
    folder 2 levels higher in the tree to change the source control
    bindings correctly."

    It is true that my project isn't within the root of the solution, but
    that's also true of other projects which are managed with no trouble
    under source code control. Also, as an experiment I moved the setup
    project under the root of the solution. I didn't get that error any
    more, but I still couldn't create a valid binding.

    Can anyone tell me what's wrong? Has anyone else encountered this
    problem?


    -TC

  • TC

    #2
    Re: Problems with Source Code Control

    I've figured out how to get this to work. When Visual Studio asks you
    to bind a setup project, it doesn't want you to match up the project
    folder, as with all other projects. Instead, it chooses a folder which
    seems to be lowest root conaining all files referenced in the setup
    project. It is confusing, but if you match up that folder to the
    repository correctly everything seems to work right.

    -TC


    TC wrote:
    I'm using Visual Studio 2005 with SourceGear Vault. I'm having trouble
    with the integrated source code control features. I think the problem
    is entirely with Visual Studio, not Vault.
    >
    First, let me say that I think the integrated source control features
    are wonderful. They work great, except when they don't work at all.
    Unfortunately, they don't work every time I need them, so I've had to
    turn them off completely.
    >
    The trouble is with setup projects. I just can't bind my setup projects
    to the repository. I get a variety of symptoms. Sometimes, it binds the
    project to the correct folder, but reports the binding as "invalid".
    Sometimes, it binds the project to the wrong folder and reports the
    binding as "invalid". And sometimes it gives me an error.
    >
    "The folder you chose is not a valid binding root for the projects you
    have selected. You attempted to retarget a solution to a source control
    folder that is not within the solution's root. In the change source
    control dialog box, specify the root for the solution. Select the
    folder 2 levels higher in the tree to change the source control
    bindings correctly."
    >
    It is true that my project isn't within the root of the solution, but
    that's also true of other projects which are managed with no trouble
    under source code control. Also, as an experiment I moved the setup
    project under the root of the solution. I didn't get that error any
    more, but I still couldn't create a valid binding.
    >
    Can anyone tell me what's wrong? Has anyone else encountered this
    problem?
    >
    >
    -TC

    Comment

    Working...