| Author |
 Topic  |
|
|
hhcc
New Member
3 Posts |
 Posted - May 10 2010 : 4:17:58 PM
|
I get the strange error in the picture below:
The project compiles (and runs) just fine, but VAX does not recognize the #using statement. Parsing has problems from there ...
My sys info:
VA_X.dll file version 10.6.1822.0 built 2010.04.22
Licensed to:
VA X: XXXX (Non-renewable license) Support ends 2010.11.05
DevEnv.exe version 10.0.30319.1
msenv.dll version 10.0.30319.1
Comctl32.dll version 6.10.7600.16385
Windows 7 6.1 Build 7600
2 processors (x86-64;
WOW64)
Platform: Project defined
Stable Includes:
C:\\Storage\\Boost;
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\include;
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\atlmfc\\include;
C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v7.0A\\include;
Other Includes:
Stable Source Directories:
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\atlmfc\\src\\mfc;
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\atlmfc\\src\\mfcm;
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\atlmfc\\src\\atl;
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\crt\\src;
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - May 10 2010 : 4:39:29 PM
|
The underlines and error message are produced by the default intellisense engine (even without VA installed).
That said, VA does not currently support #using directives to load clr references in c++. case=39988. Until that is fixed, a workaround is to add the clr reference to the project (rather than, or in addition to, the directive in the source file). |
 |
|
|
hhcc
New Member
3 Posts |
Posted - May 10 2010 : 6:11:36 PM
|
Thank you for the incredibly quick response ...
I tried adding "C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\System.Dynamic.dll" using the /FU option (as described here) ... but it did not help.
Then, I tried adding the location of my boost library (in the picture of my original post the #include was also underlined) as described here. It broke intellisense! Now, I do not have squiggles at all. I already checked in Options->Text Editor->C/C++->Advanced->Disable Squiggles to no avail.
How can I enable squiggles again?
|
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - May 10 2010 : 8:54:17 PM
|
I added System.Dynamic.dll using the /FU option and it seemed to work for me. OTOH, it isn't clear what is actually broken for you.
I'm confused about the squiggle problem. Are you saying that you have errors that should be underlined that are no longer underlined because you added boost to the directory list? |
Edited by - sean on May 10 2010 9:41:12 PM |
|
|
|
hhcc
New Member
3 Posts |
Posted - May 11 2010 : 12:21:18 AM
|
quote:
Are you saying that you have errors that should be underlined that are no longer underlined because you added boost to the directory list?
Yes! ... that was the step that killed the squiggles. The image below is from the same file as the initial posting.
As far as I can tell, I returned to the initial settings everywhere (removing the /FU file, removing the boost directory, etc.) but the squiggles are gone. Note how "aNonDefinedSymbol" has no squiggles yet the label is colored 
I understand that this is not a VAX error (and it never was). At this point I am happy that I have no squiggles all over and that VAX does a good job recovering from AverageSense mistakes. |
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - May 11 2010 : 01:08:34 AM
|
Did you disable the CLR compilation option? The squiggles won't appear in C++ when the CLR option is set. The screenshot in the first post looks like the CLR option wasn't enabled at that point. See the Common Language Runtime support setting at Project Properties | Configuration Properties | General.
|
|
|
| |
Topic |
|
Error: "#using" requires C++\\CLI
