Vault VS2005 Client - Problem with Get Latest

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

BradleyUffner
Posts: 49
Joined: Mon Jun 11, 2007 3:37 pm

Vault VS2005 Client - Problem with Get Latest

Post by BradleyUffner » Tue Jun 19, 2007 11:21 am

When I use the "Get Latest" command off of the right-click menu in the solution explorer the "Recursive" checkbox is unchecked and disabled. Also, using the get latest off of the solution it's self, instead of one of the projects under it seems to try to get the latest version of the last actual project selected, not the entire solution and all it's sub projects.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Tue Jun 19, 2007 12:41 pm

What version of Vault are you using?
Do you have service pack 1 installed for Visual Studio?

BradleyUffner
Posts: 49
Joined: Mon Jun 11, 2007 3:37 pm

Post by BradleyUffner » Tue Jun 19, 2007 12:59 pm

4.0.0.1 for both client and server.
It's visual studio 2005, with SP1, and the Vista patch for SP1.
This is 64bit Vista also.

The behavior is also happening with our other developer with same software.

ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

Post by ian_sg » Tue Jun 19, 2007 1:06 pm

Am I correct in assuming you're using the 2003 compatible plug-in?
Ian Olsen
SourceGear

BradleyUffner
Posts: 49
Joined: Mon Jun 11, 2007 3:37 pm

Post by BradleyUffner » Tue Jun 19, 2007 1:13 pm

No, I converted the solution to using the VS2005 client after the update from 4.0.0.0 to 4.0.0.1

We also seem to be having some issues checking in ASPX pages. It seems like the connection to the server is timing out in some cases, and it can take up to 10 minutes for the checkin comments window to show up. After this initial long pause files can be checked in without a delay as normal. After working for about an hour or so the delay happens again. We don NOT get the "your session has times out" dialog that normally pops up if the server is restarted, but it seems to be acting the same way.

ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

Post by ian_sg » Tue Jun 19, 2007 1:23 pm

The issue with the recursive checkbox is a display bug. A get latest from the solution node is always recursive. We should also probably enable the checkbox so you can alter that behavior. I've logged both of these.

Regarding the slow check-ins, a log would help me determine what's going on. Could you turn on logging for Visual Studio 2005 and send me the snippet during one of these delays?
Ian Olsen
SourceGear

BradleyUffner
Posts: 49
Joined: Mon Jun 11, 2007 3:37 pm

Post by BradleyUffner » Tue Jun 19, 2007 1:26 pm

I will turn on logging and copy the log to you. However the recursive issue isn't just a display problem. MY associate added a new aspx page to the project. When I did a get latest on the project the new project knew about teh new file, but the the file it's self was missing. I had to right click on the file and do Get Latest on it to actually get the file.

BradleyUffner
Posts: 49
Joined: Mon Jun 11, 2007 3:37 pm

Post by BradleyUffner » Tue Jun 19, 2007 1:35 pm

I can't find the option to enable logging. How do I turn that on, and where will the log file be generated?

Also. Get Latest on the solution has this in the Update folder
"C:\Users\Bradley\Documents\Visual Studio 2005\CGAManager\ScheduleEngine" Which is the path of one of the PROJECTS in the solution, not the actual solution.

ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

Post by ian_sg » Tue Jun 19, 2007 1:37 pm

The instructions for turning on logging are here: url=http://support.sourcegear.com/viewtopic.php?t=1534
Ian Olsen
SourceGear

BradleyUffner
Posts: 49
Joined: Mon Jun 11, 2007 3:37 pm

Post by BradleyUffner » Tue Jun 19, 2007 2:06 pm

Here is the log file.
Attachments
VaultVsipClient.txt
log file
(297.5 KiB) Downloaded 269 times

BradleyUffner
Posts: 49
Joined: Mon Jun 11, 2007 3:37 pm

Post by BradleyUffner » Tue Jun 19, 2007 2:12 pm

You can see the delay at the end of the log file. The checkin started at 3:49, and was still going on at 4:00 when I finally killed visual studio process so I could send the log file.

BradleyUffner
Posts: 49
Joined: Mon Jun 11, 2007 3:37 pm

Post by BradleyUffner » Tue Jun 19, 2007 3:30 pm

I should add that checking items in from the stand alone GUI client works without problem.

The vault server is on the local network also.

ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

Post by ian_sg » Wed Jun 20, 2007 8:29 am

Thanks Bradley, the log is helpful.

With regards to having to manually get the recently added file: believe it or not that's a separate issue. The first time a new file appears in a project file, we're not automatically getting it. Aside from this scenario that we're handling poorly, get Latest from a solution, project, or folder node is still always recursive.
Ian Olsen
SourceGear

BradleyUffner
Posts: 49
Joined: Mon Jun 11, 2007 3:37 pm

Post by BradleyUffner » Wed Jun 20, 2007 6:38 pm

Is there any update on this? It's getting really annoying to have to do an end task on visual studio about 50% of the time we try to check in a file. Using the stand alone gui client works, but after doing a check in we have to manually click "reload" in VS for every file that was modified durring the checkin.

That brings up another questions. Why is the vault client making changes to the file durring checkin that cause visual studio to have to reload them? Shouldn't it just be marking the file as readonly?

ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

Post by ian_sg » Wed Jun 20, 2007 7:22 pm

Unfortunately I can't provide a time frame because we haven't positively identified the problem here.

I'll provide more info as soon as I have it, but a fix is probably weeks off, not days. If this is happening frequently, you're probably better off using the 2003-compatible client in the mean time.
Ian Olsen
SourceGear

Post Reply