| T O P I C R E V I E W |
| jschroedl |
Posted - Jun 17 2009 : 11:08:55 AM
Hi,
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.
Now delete those lines and type this:
System::Windows::Window^ w2 = gcnew System::Windows::Window();
w2->
Press Ctrl+Space and a completion list will usually show. This is the list I need to see in the first usage since have using namespace in our code.
Here's the full VAXTest.cpp I end up with:
-------------------------------------------
// VAXTest.cpp : main project file.
#include "stdafx.h"
using namespace System;
using namespace System::Windows;
int main(array<System::String ^> ^args)
{
// FAILS
Window^ w = gcnew Window();
w->
// WORKS (Sometimes)
System::Windows::Window^ w2 = gcnew System::Windows::Window();
w2->
Console::WriteLine(L"Hello World");
return 0;
}
---------------------------------------------
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)
Platform: Win32
Stable Includes:
C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\include;
C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\include;
C:\\Program Files\\Microsoft SDKs\\Windows\\v6.1\\include;
C:\\Program Files\\Microsoft SDKs\\Windows\\v6.1\\include;
C:\\Program Files\\Microsoft SDK\\Include;
Other Includes:
Stable Source Directories:
C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\src\\mfc;
C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\src\\mfcm;
C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\src\\atl;
C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\crt\\src;
John
|
| 4 L A T E S T R E P L I E S (Newest First) |
| support |
Posted - Aug 22 2009 : 7:21:13 PM
case=28209 is fixed in build 1731 |
| sean |
Posted - Jun 17 2009 : 2:54:28 PM
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. |
| jschroedl |
Posted - Jun 17 2009 : 2:43:32 PM
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.
John |
| sean |
Posted - Jun 17 2009 : 12:05:24 PM
Do you have any change in behavior if you close the solution and then re-open it? |
