Indeed, ViEmu/VS slowly blends into Visual Studio, and one day it seems like vi/vim editing in VS was there from the beginning. I'm really happy, as that means the tool is doing its job sweetly: the more it disappears in the background, the better it means it is.

Thanks again and best regards,

  -- Jon

If I remove the default Visual Studio mapping for Esc in the text editor, normally  Edit.SelectionCancel (Esc (Text Editor)) according to the options dialog, then everything seems to work great.  The one exception is that "Esc" now always takes me completely out of insert mode, even if novaxesc is set and there is a Visual Assist listbox up.  Since that's my preferred behavior as far as I'm concerned this is perfect

Given that I am using ViEmu's visual selections instead of Visual Studio's, I don't even notice that this mapping is missing.  On a side note, the joy I feel at discovering this workaround is pretty good evidence of how dependent I've become on ViEmu

I have tried it and found that if you uninstall VS.NET 2003, unfortunately, the buggy behavior comes back. I will keep experimenting to see whether I can find exactly *what* fixes the behavior (although it's a daunting task). I hope that I can find the exact file or registry entry that fixes the problem.

Meanwhile, the only known solution is to have VS.NET 2003 properly installed.

Regards,

  -- Jon

I have VC6, VC2005, VC2008 already on my pc.
Because of the limited number of licenses allowed for me,
it's not possible to have  .NET installed on my pc.

I like to know, if the problem still remains fixed
even after uninstalling .NET.

I'll post back if I find any new info.

Regards,

  - Jon

Good luck tracking down the issue!

Regards,

  -- Jon

I think I can test this at home, given that a) I just reproduced the issue by installing Visual Assist in my home dev environment (Vista Ultimate 32 bit, VS2008; ViEmu by itself was working perfectly fine,) and b) I should have a VS2003 install set lying around somewhere.  One difference is that at home I am using VS2008, not VS2005, and the same issue shows up.

However, I don't think it's possible for me to test this at work given that installing VS2003 breaks the latest "approved" versions of a certain hardware SDK that I need.  Maybe if I get some downtime after our next deadline to rebuild everything, but that's a few weeks away.

I did verify that the issue goes away when I uninstall Visual Assist.  I don't think that adds any new information to the pile, though, apart from verifying that the issue is for certain related to VA + Vista + VS200[5, 8].

I'll try to find my 2003 install at home at least and verify that that fixes me there.

I was able to reproduce the problem in a fresh Vista x86 VM, with VS2005, the latest ViEmu (2.2.6) and the latest Visual Assist (1647). After reproducing the problem, I tried setting up a full ViEmu dev environment, which involves installing VS.NET 2003 and a few additional tools, and the problem went away!

I did this again, and found that, indeed, installing VS.NET 2003 on the same machine seems to fix the issue. It makes it impossible for me to debug the issue, which would be a hard task in any case, but at least it solves it.

So I suggest that you install VS.NET 2003 on the same machine (I only installed Visual C++ support, not any of the other languages), and see whether that fixes the problem. Please let me know whether that works.

This is a tough issue. Event notification seems to work differently sometimes for no good reason, there is no documented dependency that would cause this. And the cause seems to be somewhere deepn in the bowels of Visual Studio, .NET or Windows itself. The fact that installing VS.NET 2003 fixes it leads me to believe there is some kind of dependency on system DLLs or .NET assemblies -- given Windows' fragile design, something in the VS.NET 2003 installation makes VS2005 behave differently, maybe loading another version of some DLL or .NET assembly. You can guess that trying to track the issue with such a subtle dependency is all but impossible. Hopefully the VS.NET 2003 is a viable solution to have it quickly corrected.

By the way, I also tested whether only installing VS.NET 2003's "prerequisites" fixes it, and it turns out it doesn't. You need to actually install VS.NET to fix it (and it's not necessary to even run it once for the magical effect to happen).

Regards,

  - Jon

Regards,

  -- Jon

Actually I have thought hitting esc key twice is normal, even though it's quite annoying,
and didn't know there is an option "vaxesc",
before i read this posting.

Jon

I'll get back to you here or by email about it to try to run some instrumented tests.

  - Jon

I'm going to try reinstalling VA and ViEmu from scratch one more time.