Hi,

I am wondering if anyones else is having a similar problem as me. It seems at certain times when I do various actions (getting latest code, checking in something) the action completes and then Visual Studio locks up to the point where I have to kill the devenv.exe from the task list.

It has happened to me quite a few times now. I am running the VPC image for the server and have installed the TFC from the en_vs_2005_tfs_trial.iso file. I really like the product and have convinced my manager we should move to it but I can't really do that in good faith if the team is going to lock up frequently.

Cheers,

Clint

Clint,

Can you provide some more details on how things are locking up?

Is VS still using a lot CPU? Network bandwidth?

Is the Server using CPU still?

When things appear locked up do you actually have progress dialogs displayed still?

Do you have any virus checkers or other background apps running?

- Tim

Hi,

First of all I have so far only seen this problem related to source control activities. I consiently get it when checking in a file but have also seen it when getting latest and automerging a file that was changed on my local machine.

In the context of the checkin lockup, I will see the dialog which says it is doing work then it goes away as if everything was fine. Clicking on VS2005 produces no reaction from the software. None of the CPU's on the server nor on my local machine are doing anything. I am also only able to close the appliation via the task manager because clicks on the 'x' are not acknowledge at all.

I have tried disconnecting my network to see if there is a connection that can be broken but that did nothing.

At one time I did attach another instance of VS2005 to the hung instance and took a minidump if that will help at all.

Cheers,

Clint

PS. I am not running any kind of virus checking or background apps other than windows services.

• save a copy of your modified file somewhere
• undo the change
• get latest
• checkout the file
  
• manually merge in your changes from the copy you saved
• checkin

Hi,

I think it is something else because I have recently experienced the same issue while trying to check out a file. I then killed VS2005 and made a change then checked in the file with it being the only change to the file from the most recent version of the server. I am the only one working on files at this time so I am guaranteed to be checking in over the last latest file.

I general it seems that whenever I do any Source Control related activities there is a very high chance that that action will lock up VS.

Cheers,

Clint

Hey all

I am having the same problem. I am not however running TFS in a VPC. I am running it on a dedicated server. I am consistently having the problem when I try and create a new project in the source control. Does anyone know how to fix this yet?

Thanks

MacKenzie

I am debugging an issue that sounds very similar to this that happens with a particular add-in installed. Are you running any VisualStudio add-ins?

Another data point that would be helpful to me would be to know what the Win32 window state flags (WS_XXX) are for the main VS window when the problem occurs. The simplest way to get the state flags would be to run Spy++ and display the properites for the main window and click on the Styles tab.

Okay I am using CodeSMART 2005 G2 by AxTools

Here is the state flag information

WS_CAPTION
WS_VISIBLE
WS_DISABLED
WS_CLIPSIBLINGS
WS_CLIPCHILDREN
WS_MAXIMIZE
WS_SYSMENU
WS_THICKFRAME
WS_OVERLAPPED
WS_MINIMIZEBOX
WS_MAXIMIZEBOX

Let me know if you need anything else

Thanks

Kenzie

OK, this appears to be the same issue I am debugging.  I should have an answer soon.  And hopefully a solution too!

Thanks for getting that info so quick!

Hi,

I am having the same problem of visual studio locking up after completing various source control tasks.

The foundation server and team explorer clients were installed from the en_vs_2005_tfs_trial.iso. I also have the Innovasys Document! X 5 trial add-in installed. After removing the document X add-in the problems seem to go away.

I would like to know if there will be a fix or workaround for this issue.

Thanks,

Jeremy

I've figured out the problem and have a fix - at least for one of set of add-ins. I will see if I can get a copy of the Innovasys and AxTools add-ins to verify the fix works for them too.

Unfortunately there is not much you can do for this problem until a patch is released (and sorry I don't have a timeframe on that yet).

There are a few possible workarounds: don't have a solution open when you perform version control operations, run a second copy of VS (with no solution opened) or the command line to do version control operations, uninstall the add-ins that are causing the problematic interaction. I wish there were some better options available to you.

If you are curious about the technical details, this is not actually a hang per se. What is happening is that due to a call ordering problem the VS window gets disabled after the progress dialog is called. That is the result of a deferred modal state change request that does not get processed until our dialog is dismissed because the main VS message pump is what dispatches the modal state change.

Well I would like to thank you for your time and effort on this problem, though I must say that I am disappointed with the solution.

Kenzie

For anyone that is experiencing this problem, please call CSS at 800-936-5700 and report the issue. This will help us a great deal. Thanks!