4.0.5 Bug report: New projects under source controlled .sln

gmagana · Post by **gmagana** » Tue Oct 16, 2007 6:10 pm

VS2005 client issue:

The previous behavior was that when you added new projects to a source-controlled solution, the new projects would show up with a "+" icon. You did not have to check in right away, and you could close the solution and reopen without problems, you could check-in (add to Vault/Fortress) the new projects at a later time.

With 4.0.5 beta, now you must checkin (add to source control) any new projects in the solution before closing the solution, otherwise when you try to re-open the solution you get a dialog saying "The project XXX is bound to Fortress but has no valid working folder in its current on-disk location." You are then forced to work offline or locate the new projects in Fortress/Vault (of course they have not been added to source control yet, so no dice there).

You could open the solution in offline mode, remove the new projects, and then you can get the solution to open in online mode, but without the new projects. Afterward, I cannot see a way to add the existing non-source controlled projects back into the solution without causing the solution to go into offline mode. (Which implies that it is not possible to add existing projects to a source controlled solution)

EDIT: I started the Fortress/Vault client and it seems that the checkin of those new projects is marked as a "pending operation," so maybe that's the problem: the binding information is added to the project files before the actual checkin? If I do the checkin from the Vault/Forest client, then I can add the projects again from the VS2005 IDE andproceed without problems, other than adding the projects a little before I had planned.

lbauer · Post by **lbauer** » Wed Oct 17, 2007 7:02 am

Thanks for the report; we'll check this out.

ian_sg · Post by **ian_sg** » Wed Oct 17, 2007 8:11 am

Gabriel,

Thanks for the report. We saw this issue at one point during testing, and I thought we had squashed it. We're having trouble reproducing it now. It would be really helpful if you could send me a log showing:

1. Adding the solution
2. Opening the solution in this "pending add" state when you get the incorrect working folder message.

(Instructions for turning on the 2005 client's log are here.)

The binding information is written into solution/projects when you pend the adds, but this is by design. It sounds like a working folder assignment is not being made or correctly determined for you here.

Also, I remember that you'd had trouble adding a particular solution to Vault using 4.0.4. Has 4.0.5 resolved that?

Thanks very much.

ian_sg · Post by **ian_sg** » Wed Oct 17, 2007 3:58 pm

We've been able to reproduce this issue (pending add new projects gives spurious working folder warning) and I expect we'll have a fix in the final 4.0.5 build. I'll admit that this was very similar to another bug we'd recently addressed, and so our failure to reproduce it was mostly the result of misreading it, thinking it was essentially that other issue. Better late than never.

Gabriel: I'd still like to hear about your experience with Add to Vault on that troublesome solution, if you can spare the time.

gmagana · Post by **gmagana** » Wed Oct 17, 2007 6:31 pm

ian_sg wrote:Gabriel: I'd still like to hear about your experience with Add to Vault on that troublesome solution, if you can spare the time.

Thanks, the issue is fixed... I was able to add that solution to Fortress and retrieve it without problems. Thanks!