I'm running into problems with VAX using C++/CLI assemblies and suggestion lists.
Try this in Visual Studio:
File > New Project. Select Visual C++, CLR, CLR Console Application. Name = "VAXTest"
Build Project for fun -- Success.
In Soltion Exploer, bring up the Project Properties. Select Common Properties, Add New Reference... Add references WPF assemblies: PresentationCore, PresentationFramework and WindowsBase. (Ignore that I'm referencing WPF in a Console app - this is just a demonstration and does not matter).
In VAXTest.cpp use a WPF namspace:
using namespace System::Windows;
For fun: Build Project -- Success.
In main() type
Window^ w = gcnew Window(); w->
Press Ctrl+Space -- No completion list shows. ugh.
Even this "working" w2 case can stop working and offer no suggestion list. For example, I reworked the code a bit to add those // WORKS and // FAILS commands and Ctrl+Space stopped working for w2. Even if I delete the fails case so that it's legit code it can still stop working.
My Info:
- Beta build 10.5.1727.0 But it's nothing new to this build..been happening for a many versions. - Get content from default intellisense is OFF. No change if I turn it ON. - Reparse Current file doesn't help. - I have all the coloring I can turned on. It's interesting that "w" shows in light gray italics but is not bolded. Even though I have "Local symbols in Bold" and "Stable symbols in Italic" ON. Turning them OFF doesn't affect the suggestion list any.
VA_X.dll file version 10.5.1727.0 built 2009.06.12 Licensed to: VA X: XXXXXXXXXXXXXXXXXX DevEnv.exe version 9.0.30729.1 msenv.dll version 9.0.30729.1 Font: Consolas 12(Pixels) Comctl32.dll version 6.10.6001.18000 Windows Vista 6.0 Build 6001 S 4 processors (x86)
Indeed, the suggeston lists start working again after I re-open the project.
Our product solution is so large that I rarely reload during the day so I seem to hit this frequently.
Is there anything I can do to trigger the same update somehow without needing the project re-load? Is it adding the reference that causes the problem or using the namespace? Our set of references hasn't changed in a long time so I think it must be adding the 'using namespace' which is the trouble.
I recently came across a bug that seems related to the problem you are seeing. It will be fixed in the next release cycle. The problem is that references added to a project are not handled properly until you re-load the solution. case=28209
I'm not sure why you are seeing intermittent success/failure before the reload though.