Visual Studio 2005 glitch

[rrounkles]

I'm experiencing a glitch under Windows XP, using Visual Studio 2005. When working on code, for example implementing an interface in a class, the refactoring menu does not render. I have tried both the keyboard shortcut (alt-shift-F10) and clicking on the popup icon, both have the same result; the menu appears to render briefly, then flashes away and I'm left with the just refactoring icon. This is negatively affecting my development time, as a lot of the automation features in Visual Studio are available only through that context menu (as in this case, the "Implement interface xyz" feature). Has anyone else experienced this problem, or found a solution?

 

[vioccc]

I'm experiencing a glitch under Windows XP, using Visual Studio 2005. When working on code, for example implementing an interface in a class, the refactoring menu does not render. I have tried both the keyboard shortcut (alt-shift-F10) and clicking on the popup icon, both have the same result; the menu appears to render briefly, then flashes away and I'm left with the just refactoring icon. This is negatively affecting my development time, as a lot of the automation features in Visual Studio are available only through that context menu (as in this case, the "Implement interface xyz" feature). Has anyone else experienced this problem, or found a solution?

I had don't any problems with this menu on my machine. If I type this code in a new .cs file:

using System;

namespace Hi
{
interface Test
{
void SomeFunction();
}

class Class1: Test
{
}
}

clicking on the Refactor thingie under "Test" or using Alt-Shift-F10 displays the context menu properly with "Implement Interface Test" and "Explicitely Implement InterfaceTest". Selecting either option works. If I change the namespace name, the Refactor thingie works as well offering me to rename Hi.

My config:
- MacBook C2D / 768MB allocated to Windows / MacOS X 10.4.9 up-to-date
- Windows XP SP2 up-to-date running off a VM file (not bootcamp)
- Coherence mode with Windows Taskbar hidden
- Windows performance settings set to "Optimize for best performance" (i.e. all the Fisher Price colors and effects are disabled, Win 98 look).
- Visual Studio 2005 Team Suite edition with SP1

 

[rrounkles]

My config

Thanks for the info. To clarify, my config:

MBP 15", CD, 1.83Ghz, 304MB RAM allocated to windows, 24MB video
Windows XP Pro SP2, running off VM (not bootcamp)
Tried coherence, fullscreen, and windowed
Windows Performance set to "Best performance", win98 look
Visual Studio 2005 Pro SP1

The only difference I can see between my machine and yours is the C2D (which I believe has a different video card), and Team Edition, which really shouldn't make a difference. If I bootcamp it, same machine, same version of visual studio, the menu works.

 

[vioccc]

Thanks for the info. To clarify, my config:

MBP 15", CD, 1.83Ghz, 304MB RAM allocated to windows, 24MB video
Windows XP Pro SP2, running off VM (not bootcamp)
Tried coherence, fullscreen, and windowed
Windows Performance set to "Best performance", win98 look
Visual Studio 2005 Pro SP1

The only difference I can see between my machine and yours is the C2D (which I believe has a different video card), and Team Edition, which really shouldn't make a difference. If I bootcamp it, same machine, same version of visual studio, the menu works.

I can see another difference unless it's a typo (did you mean that your MBP has 64MB of VRAM?): you've allocated 24MB of VRAM to your VM. IIRC the default is 16MB and i've left it there. Might be worth trying to set it back to the default.

 

[mmischke]

Thanks for the info. To clarify, my config:

MBP 15", CD, 1.83Ghz, 304MB RAM allocated to windows, 24MB video
Windows XP Pro SP2, running off VM (not bootcamp)
Tried coherence, fullscreen, and windowed
Windows Performance set to "Best performance", win98 look
Visual Studio 2005 Pro SP1

The only difference I can see between my machine and yours is the C2D (which I believe has a different video card), and Team Edition, which really shouldn't make a difference. If I bootcamp it, same machine, same version of visual studio, the menu works.

You didn't mention how much physical RAM your iMac has. You'll want 2 GB for this type of scenario. With only 304 MB allocated to XP, it's probably thrashing itself to death with VS 2005 running. The transient menu behavior may be the result of timing issues because of this. I run this same scenario on my Mac mini, day in and day out. I give XP 1 GB and everything's nice & crisp - even VS 2005 while debugging.

I'll bet the problem will go away if you give XP 768 KB - 1 GB.

FYI - this isn't a Parallels thing. It's XP & any heavy app (like VS). It wants plenty of RAM, even on a physical machine.