Why is Recursive greyed out when doing Check-out...

[dist0rti0n]

...from the project level?

Prior to the latest version I didn't have an issue with this.

See attached screenshot.

http://picasaweb.google.com/zack.beadle ... 1611699154

[jclausius]

Is it possible there is a file checked out within the branch? You won't be able to get an exclusive, recursive check-out to work if there is already a lock on an item in a sub-folder.

I'm not sure that is the problem you're seeing, but it seemed like a good guess.

[dist0rti0n]

Nope - no files checked out.

[dist0rti0n]

Could I get an update on this issue?

Here's a screenshot of what I'm talking about:



This is the dialog I was presented when right-clicking and selecting checkout on a project.

[ian_sg]

Good question. I was able to reproduce this: you can't recursively check out from a project. I've logged a bug to get it fixed.

[dist0rti0n]

Good question. I was able to reproduce this: you can't recursively check out from a project. I've logged a bug to get it fixed.

Thanks!

[thx1200]

I am having the exact same problem and it's pretty annoying... Is there any status on when an update might be available to fix this problem?

Thank you!

[ian_sg]

We don't have an ETA at this time. Note that you can select multiple nodes and checkout an entire project/solution this way.

[thx1200]

I'm currently using the standalone client to do full-project check-outs. I wasn't able to recursively check out multiple nodes using Visual Studio. It would only check out the project file (vbproj) and not any of the vb source files underneath. So to check out the entire project, I would have to individually click on each file, which would be a pretty major waste of time. heh.

I hope this issue is fixed in the next release, whenever that is... The standalone client works fine, so I can't imagine this being a huge issue to fix in the Studio client. The problem is that the standalone client is yet-another-window I have to have open, which defeats the purpose of the integrated solution.

Thanks for making an overall amazing product, despite this one mildly annoying bug.

[ian_sg]

I agree that it's annoying, but it's not quite as annoying as clicking every file in a project:

Expand the project node. Click on the project node. Shift-click on the last file in the project. Checkout. Done.

Sorry for the inconvenience.

[lodani]

is this bug still alive after almost a year since it was detected? My checkout is grayed out if I use the Advanced Client, but works fine with the classic client.

very anoying

[thx1200]

I never use the advanced client for this very reason. I still find it unbelievable that it's not fixed yet. It seems so simple.

[ian_sg]

Thanks for the feedback, this one did slip through the cracks. I've bumped up the priority on the bug.

[lodani]

I never use the advanced client for this very reason. I still find it unbelievable that it's not fixed yet. It seems so simple.

wow thank you!. I was hoping that this issue could be fixable throught configuration but now I realized that is not.

Then, this slowness in bugfixing is scary. I'm still in the evaluating process (Vault vs TFS) and I don't know if this the usual response time from SourceGear, but is quite worrying.

lo

[AjarnMark]

Lodani, I wouldn't let this influence your decision much. We have been using Fortress (and Vault/Dragnet before it) for a couple of years and we love the products, and have always found the support at SourceGear (the FEW times we have needed it) to be exceptional! And if you're comparing it to Microsoft's track record...well...let's just say that you will get superior personalized support from SourceGear.