New Projects do not get retrieved on get latest version

We're experiencing some difficulties here.

I've added 3 new projects to our Solution and checked them in. However, no one in my team gets them when they get latest version from Source Control, or from the Solution Explorer. They have to manually go and "Add Project from Source Control" from the File menu.

What could cause this

I've checked out the solution file from Source Control, built the solution (for some reason when we build the entire solution it asks to check out the Solution File) and then checked it back in, but no one gets it.

At the same time, if we branch this solution to a new branch, it will not carry over the new projects (It will copy the code, but the projects will not be in the solution).

Is our solution file hosed or is there some way to fix it




Answer this question

New Projects do not get retrieved on get latest version

  • mon

    The Add To SCC wizard does 3 things:

    1. map all of the projects on disk to server paths
      1. if the current workspace already satisfies this, Add proceeds without prompting
      2. if not, it will prompt you for the server location where you want to store the solution, then create the necessary workspace mapping(s)
    2. pend adds on the files so that they can be committed to the server
    3. write bindings to the sln/proj files

    If a solution/project already exists on the serve -- usually because you already added it from SCE or the command line -- then you can't use the Add To SCC wizard. #2 would fail, unless you want to add it to a different location.

    Sounds like all you need to do is #3. This can be done manually in the Bind dialog (File -> Source Control -> Change Source Control).


  • Smithy196

    I checked my Source COntrol bindings and the Solution was un-bound. This is most likely because when we compile it asks to checkout the solution. It must've been overwritten when I was doing a build to release last sunday because a co-worker had it checked out :\



  • charlie_mtz

    Yes. When I choose to bind the Solution to Source Control it tells me I need to check out the file.
    Then I check the file in, put in my dev. notes.

    I close VS.NET, re-open and the solution is not bound anymore.


  • Chris Han MSFT

    The solution file still creates errors.

    We re-bound the solution to Source Control. However, whenever we restart our computers or restart visual studio, we lose the binding.

    Any thoughts


  • themuuj

    Richard, for the life of me (over the past 3 days) i have not been able to get a "lock" on the solution name in the solution explorer.

    I first noticed it when i "Right Click" + "Add Solution to Source Control", but it tells me that it's already in source control.

    It lets me "Select different location" or Cancel/Help.

    Any thoughts

    ---Also, when I open the .sln file up in notepad it does reference our project (DataAccessEntities) however it never includes it in the solution explorer.

    This is what it has in the .sln file:

    Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "DataAccessEntities", "Global\DataAccessEntities\DataAccessEntities.csproj", "{1D00435F-042B-44B0-930D-01F7F702604D}"
    EndProject


  • Delphyne

    Is the solution bound (Does it have a padlock next to it in Solution Explorer )

    If you view the history of the .sln file, was it modified in the changeset where you added the new projects Does the diff look correct


  • Joshua Tipton

    Did you checkin your changes

  • New Projects do not get retrieved on get latest version