C++ intellisense for Visual Studio 2010
-
Saturday, April 24, 2010 4:36 PM
I just updated my VS2008 to VS2010. I was aware that there was no support for intellisense for C++/CLI.
My software uses limited C++/CLI functionality with most functionality in native C++. However, I use the WPF to access both the Managed/Unmanaged classes.
However, it seems that any code under WPF -- even the native Classes accessed from the WPF classes cannot access Intellisense.
Is this correct? Under what type of project do I get the Intellisense for my unmanaged classes?
--- Jim
Answers
-
Thursday, April 29, 2010 4:46 PM
Hi Jim,
Unfortunately that is the by design behavior by current VS 2010. Basically "IntelliSense does not work for ANY C++ file (regardless of /clr setting) IF there is a /clr file used in the project".
We have got lots of complains about this issue, see VC blog: http://blogs.msdn.com/vcblog/archive/2010/04/13/visual-studio-2010-is-now-available.aspx#9995285 and we are working on a fix for it for next VS release\update.
Currently, you can try the following workaround: Don’t add /clr:nostdlib as an additional option for files that are to be compiled as native.
Thanks,
Jianhua
- Marked As Answer by Yi Feng LiMicrosoft Contingent Staff, Moderator Friday, April 30, 2010 4:46 AM
All Replies
-
Sunday, April 25, 2010 4:18 AM
jim,
pls refer this link for further on intellisense
http://msdn.microsoft.com/en-us/library/ms165392.aspx
also check visual c++ intellisense on http://msdn.microsoft.com/en-us/library/dd547188.aspx
sree
THEY SAID I WAS LAZY, THEY DIDNT KNOW I DREAMT OF CODE!
www.crawller.com
PLS MARK AS ANSWER IF UR DOUBT IS SOLVED OR REVERT QUERY -
Thursday, April 29, 2010 4:46 PM
Hi Jim,
Unfortunately that is the by design behavior by current VS 2010. Basically "IntelliSense does not work for ANY C++ file (regardless of /clr setting) IF there is a /clr file used in the project".
We have got lots of complains about this issue, see VC blog: http://blogs.msdn.com/vcblog/archive/2010/04/13/visual-studio-2010-is-now-available.aspx#9995285 and we are working on a fix for it for next VS release\update.
Currently, you can try the following workaround: Don’t add /clr:nostdlib as an additional option for files that are to be compiled as native.
Thanks,
Jianhua
- Marked As Answer by Yi Feng LiMicrosoft Contingent Staff, Moderator Friday, April 30, 2010 4:46 AM