I consider it a bug that Team Explorer does not fetch the latest version of a file when the client selects to check it out for edit. There should be at least an option in settings to enable/diable this. Editing out-of-date files is getting old.
That's my 2 cents.
In short, silently breaking your build is a lot worse than making you click the automerge button during checkin.
Given how often it's brought up on this forum, there's a decent chance we'll provide an option for VSS-style checkouts in a future version. If we did, would you want it to get:
(a) just the file(s) you tried to edit
(b) all of the active solution
(c) all of the current workspace
(d) ?
None of us are used to that workflow, so your input is appreciated.
I agree that in editing a bug you do not wish to edit out another users' errors as well (not that I would dare checking in such files!) To find out you need to merge your file on check-in anyway.
Why not give it a drop out on check out (check in the background while pressing on the file) and supply any of these options (which I'm sure can be set as default team behaviour!)
(d) All of the current project
(e) All of the current (partial) class
would be nice options.
My 2 cents.
Hi, It's so weird; you Foundation Server guys really think a lot of your merge tool. There's no denying that it is handy, but there's no denying it doesn't walk on water. In fact, if it was "all that" then I would never have considered this as a flaw in the first place.
(In fact I consider the fact that you allow multiple check-out of the same file a bug too! Tongue-in-cheek, but just barely.)
Anyway, if I am about to edit a file that has a more recent version on the server than what is in my local workspace, then I need a pop-up prompting me to either "get latest" or continue without getting latest.
I think a checkbox in the dialog allowing me to "default" all future answers is not a bad idea. However, I think a "get all project files" or "get all solution files" is *way* overkill for what we are trying to accomplish here.
If I get latest on check-out then you already "buy in" to the negative that you might break my build as a result. No need to create another area to complete a function that is already easily accomplished in the existing interface.
Thank you for your response, by the way. It is refreshing to know we are not alone in our frustration of this implementation. As a concession, I do understand why it was not originally included - but the real world is sloppier than the text book world.
Best regards,
If you don't like multiple checkout, you can always turn it off. (Team -> Team Project Settings -> Source Control)
Good to know that getting just the affected file would suffice for you. Your feedback helps us plan vNext.
Hey, I just thought something that might be a good idea.
I have started using the check-out confirmation dialog because too many things are getting checked-out behind the scenes. Anyway, that dialog would be a good location for a checkbox that reads "first get latest version from server".
Just thinking outloud.
Hey, I just thought something that might be a good idea.
I have started using the check-out confirmation dialog because too many things are getting checked-out behind the scenes. Anyway, that dialog would be a good location for a checkbox that reads "first get latest version from server".
Just thinking outloud.
