Have Geek Brain

VS2008 devenv won't close without creating files?

Hey guys, do you guys encounter this behavior and if so how did you get around it?

Basically what happens is: I will have a VS2008 instance, pop into another VS project in a new instance, and then close the new instance. After that, from time to time VS will complain that "The file is open in another window, would you like to close it?". Clicking yes does nothing; I cannot open the file in the editor.

What's infinitely worse, any files that would display this behavior (which are perhaps the ones I am not aware of) do not seem to be built. The assembly does not immediately include the classes that represent the problem.

I noticed that when I close VS, there are still examples of devenv.exe running; when I kill them in Process Explorer, the problems seem to go away, so it seems to me that they keep open file descriptors.

I wish I could trust my environment a little more than I can now ...

Any suggestions?

PS - I have VimEmu installed and a single plugin.

0


a source to share


2 answers


The obvious question is, have you tried uninstalling / disabling a third party plugin to see if it changes something?



+1


a source


One thing you can try to work around this issue (so you don't need to close) is to trigger the unlock on the affected files.

http://www.emptyloop.com/unlocker/

It is a free tool that allows you to see which files are locked and then can force you to unlock.

Don't fix the problem, but it could be the problem.



As a side note, when I modify the file in the second instance of Visual Studio, I get this message:

This file has been modified outside of the original editor.

Do you want to restart it?

+1


a source






More articles:


All Articles