VS.NET 2003 long delay when undoing a file checkout

cmccarrick · Post by **cmccarrick** » Tue Mar 23, 2004 7:47 pm

Whenever I undo a single file checkout in vs.net 2003, the IDE goes a little crazy and seems to loop through every file in my project taking about four minutes before I can access the ide again. This also happens after I choose the option to overwrite a local version of the file.

Any suggestions?

Thanks,

Christian

Post by **jclausius** » Tue Mar 23, 2004 11:02 pm

what version of vault are you using? if vault 2.0.0 (build 2120), do you have folder security enabled on the repository?

cmccarrick · Post by **cmccarrick** » Tue Mar 23, 2004 11:05 pm

version 2.0.1 build (2137)

cmccarrick · Post by **cmccarrick** » Tue Mar 23, 2004 11:07 pm

I did not enable folder level security when I installed the product. I am assuming that it is still not enabled.

Thank you,

Christian

Post by **jclausius** » Tue Mar 23, 2004 11:22 pm

christian:

can i ask you for a favor?

checkout a file from ide client. how long does this take?
shutdown vs.net 2003
start vault gui client
undo the checkout from vault gui client- how long does this take?

can you describe your solution - number of projects, type of projects, number of files, etc? i'll see if i can recreate your environment to see what is up.

its a little late for me now (GMT -6:00). i'll be able to take a closer look at recreating things, from the info gathered by your response, sometime tomorrow.

cmccarrick · Post by **cmccarrick** » Tue Mar 23, 2004 11:57 pm

thanks for your help.

Checking out a file that has been changed by me or not been changed takes seconds. Undoing the checking through the vault client takes seconds.

I have 1 solution with 2 projects. The main project has about 3,000 files in it. The other one has about 50.

It seems to be more related to the vs.net / vault integration then the vault server itself I think.

When I re-open vs.net it also wants me to instantly check out any file that I had changed but already checked in during my previous session. weird.

Thank you for your help.

Christian

Post by **jclausius** » Wed Mar 24, 2004 9:41 am

christian:

sorry to keep going back and forth on this.

is the amount of time you wait for an undo checkout the same if you are undoing a checkout from the main project vs. undoing a checkout from the 50-file project from within vs.net 2003?

cmccarrick · Post by **cmccarrick** » Wed Mar 24, 2004 11:32 am

The real issue seems to be why vs.net needs to cycle through every file in the project after every undo, or overwrite, or merge action. Since there are so many files in the project it takes a long time to loop through them. It is similiar to what happens when I first load the project (with or without vault installed).
The project with 50 files still loops through, but there are much less files, so it takes less time.

Again, this might be an issue with vs.net, but I would like to have some facts before I open a ticket with MS.

Thanks,

Christian

Post by **jclausius** » Wed Mar 24, 2004 1:00 pm

christian:

can you verify that the checkout on the 50 file'd project works within a normal time period?

cmccarrick · Post by **cmccarrick** » Wed Mar 24, 2004 1:31 pm

In either case, large project or small project, the checkout action itself performs in seconds. The problem only appears right after the checkout happens if the checkout requires a merge, then it loops through every file and takes four minutes.

The small project seems to work fine.

Christian

corey · Post by **corey** » Wed Mar 24, 2004 3:24 pm

When you perform an Undo Check Out on a file, do you select the file and then choose Undo, or do you select the parent project and then choose Undo?

If you're just selecting the specific file, then I don't think VS.NET loops through all files by default. In that case, it could be an inefficiency in Vault's implementation of Undo in the IDE Client.

cmccarrick · Post by **cmccarrick** » Wed Mar 24, 2004 5:05 pm

I usually just do one file.

corey · Post by **corey** » Thu Mar 25, 2004 11:25 am

When you say that VS.NET "loops through every file in the project", what do you see in VS.NET? How do you know its looping through every file?

cmccarrick · Post by **cmccarrick** » Thu Mar 25, 2004 11:28 am

The solution explorer window in the top right of vs.net seems to jump from one file to the next in a random order. Along with this, the file itself seems to open in the main designer window for a second or so before it moves on to the next file and so on, eventually opening every file in the project. (1,000+)

Christian

Post by **jclausius** » Thu Mar 25, 2004 3:00 pm

christian:

when you select the one file for undo, a dialog is displayed for undo checkout.

is it safe to assume only that one file is displayed in the dialog?
when you confirm the "undo", do you use your mouse to click the OK button or do you hit "enter" on the keyboard?

the file itself seems to open in the main designer window for a second or so before it moves on to the next file and so on, eventually opening every file in the project. (1,000+)

something is definitely strange with vs.net in this case. the msscci/vault ide has no code to force the loading of a file within a project. is there maybe some sort of setting in vs.net that would force a file to load? perhaps some sort of macro? just grasping at thin air here.

SourceGear Support