SourceGear Support

Ok, we turned on VS2005 client logging per http://support.sourcegear.com/viewtopic.php?p=5375 . I attach the generated log, it covers opening and closing the solution without doing anything else.

Sure, here is a screen capture of the dialog... The bindings look messed up (root folder for all?). If it helps any, everything is displayed OK in the Fortress client.

EDIT: Forget my comment above of the bindings looking messed up, it is the same way on a machine that works fine...

We have a weird situation on 4.0.5 beta (it's really Fortress 1.0.5 beta). There are no icons on the files, check-ins/getlatest work, and the right click menu of the solution is missing the Online/Offline options. Attached is a screenshot of how this looks... We are using the 2005 client with CVS-st...

Thanks!

Cool, thanks

I don;t actually know if this is specific to 4.0.5, but it seems that it is hard to update the icons when the status of a file changes... For example, if I have a file whose status is "needs merge," I can see the icon there... If I do a merge and resolve it, it seems that it takes a very l...

Yes, VSIP in CVS mode

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!

Here's one that threw us way off (and still does sometimes): When one is working in offline mode, the Vault/Fortress icons disappear. The problem is that it looks exactly as if the solution was not bound to source control. This might send people off in a panic thinking that somehow the solution is n...

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...

ADDENDUM / CORRECTION: This only happens on the file currently being edited. Any other open files are not affected.

This happens with 4.0.5 beta as well. If you do a checkin from VS2005, any C# files that are open will have all their #region s expanded. you then have to manually collapse any #regions you wanted to collapse. Any files that are closed at the time of checkin are not affected. I don't program in VB, ...

Just a note: These outstanding bugs affect some of us greatly... And we are not in a position to give our clients the standard SourceGear "we don't have a date for the next release yet" response. Right now I have gotten bit by this "Add solution to Fortress" bug with an important...

Thanks... Is there a suggested workaround? For example adding the files by hand (through the client) then re-binding within VS2005 (VS2005 client, in case it matters), or some other "clever" way of going around it right now?

Thanks,

gabriel

Grrr... this is the second time I've tried to add the solution to Fortress, and the process goes on for about three hours and then tells me operation timed out, check your network settings (or something to that effect)... The bad thing is that the files are half-added to version control, not all fil...