Message for MS (Re: VS2010)
-
file:///C:/Documents%20and%20Settings/Smiller/Local%20Settings/Temporary%20Internet%20Files/Content.IE5/YHRATLVN/VS2010RCReadme%5B1%5D.htm#Supported%20Operating%20Systems Contains the following: 2.4.2.3 IntelliSense does not work for C++/CLI IntelliSense is not available for C++/CLI in this release of Visual Studio. However, all browsing features (ClassView, GotoDef, Find All References, Navigate To, etc) are still available for C++/CLI. To resolve this issue: There is no workaround. IntelliSense for C++/CLI is not supported in this release of Visual Studio. To which I say to the VS team at Microsoft, with deep and heartfelt sincerity: F*ck Yo* So, I'm to be further manipulated by the social engineering of ease-of-use? Instead, maybe I'll be even inspired to drop the MSDN subscription and shop elsewhere for a compiler/IDE. (apologies to any in the community the above word-choice may offend)
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"It's a sad state of affairs, indeed, when you start reading my tag lines for some sort of enlightenment. Sadder still, if that's where you need to find it." - Balboos HaGadol
Well, the good news is the
C++compiler comes still with Visual Studio 2010... :rolleyes:If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
Seriously? After all the complaining about the poor support for C++ in VS2008, they still haven't addressed this issue? Is it intellisense for everything in C++, like MFC, or just C++/CLI? Marc
I tested VS 2008 for a MFC project and the list of functions showed itself.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"It's a sad state of affairs, indeed, when you start reading my tag lines for some sort of enlightenment. Sadder still, if that's where you need to find it." - Balboos HaGadol
-
Rama Krishna Vavilala wrote:
I do not prefer to write too much code in C++/CLI, as even with good Intellisense support it was messy with all caps and hats.
That, my friend, is a choice you made for yourself . . . which is my point. I don't like being told what to do - unless the teller is willing to pay me for the privilege.*
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"It's a sad state of affairs, indeed, when you start reading my tag lines for some sort of enlightenment. Sadder still, if that's where you need to find it." - Balboos HaGadol
As somebody else has pointed out already when it comes to C++/CLI there is no other compiler which supports it. So you have to stick with VS2010 or continue using VS2008.
-
Visual Assist[^] will support it I believe (or so I recall reading somewhere). But still...
Balboos wrote:
shop elsewhere for a compiler/IDE
But then how would you do C++/CLI?
Kevin
Kevin McFarlane wrote:
But then how would you do C++/CLI?
That's my question too :).
-
Seriously? After all the complaining about the poor support for C++ in VS2008, they still haven't addressed this issue? Is it intellisense for everything in C++, like MFC, or just C++/CLI? Marc
It is just for C++/CLI. The Intellisense is based on another framework and that framework does not support C++/CLI, so Intellisense is not available for C++/CLI.
-
Visual Assist[^] will support it I believe (or so I recall reading somewhere). But still...
Balboos wrote:
shop elsewhere for a compiler/IDE
But then how would you do C++/CLI?
Kevin
Kevin McFarlane wrote:
Visual Assist[^] will support it I believe (or so I recall reading somewhere). But still...
That's like telling WPF programmers they have to use Expression Blend to get the functionality the IDE should already have.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
Kevin McFarlane wrote:
Visual Assist[^] will support it I believe (or so I recall reading somewhere). But still...
That's like telling WPF programmers they have to use Expression Blend to get the functionality the IDE should already have.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001That's why I appended "But still..." :laugh: Nevertheless, there's no harm in pointing the OP to a solution should he choose to investigate it. Re: Blend, yes I always thought that was crazy. MS just wanting to make more dosh. Does VS 2010 provide a superset of Blend or will there still be features in Blend it doesn't have?
Kevin
-
That's why I appended "But still..." :laugh: Nevertheless, there's no harm in pointing the OP to a solution should he choose to investigate it. Re: Blend, yes I always thought that was crazy. MS just wanting to make more dosh. Does VS 2010 provide a superset of Blend or will there still be features in Blend it doesn't have?
Kevin
Kevin McFarlane wrote:
Blend, yes I always thought that was crazy. MS just wanting to make more dosh. Does VS 2010 provide a superset of Blend or will there still be features in Blend it doesn't have?
The situation has not changed. VS2010 still doesn't have the Blend features that it really should have, and Blend is still a half-assed excused for a development environment.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
file:///C:/Documents%20and%20Settings/Smiller/Local%20Settings/Temporary%20Internet%20Files/Content.IE5/YHRATLVN/VS2010RCReadme%5B1%5D.htm#Supported%20Operating%20Systems Contains the following: 2.4.2.3 IntelliSense does not work for C++/CLI IntelliSense is not available for C++/CLI in this release of Visual Studio. However, all browsing features (ClassView, GotoDef, Find All References, Navigate To, etc) are still available for C++/CLI. To resolve this issue: There is no workaround. IntelliSense for C++/CLI is not supported in this release of Visual Studio. To which I say to the VS team at Microsoft, with deep and heartfelt sincerity: F*ck Yo* So, I'm to be further manipulated by the social engineering of ease-of-use? Instead, maybe I'll be even inspired to drop the MSDN subscription and shop elsewhere for a compiler/IDE. (apologies to any in the community the above word-choice may offend)
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"It's a sad state of affairs, indeed, when you start reading my tag lines for some sort of enlightenment. Sadder still, if that's where you need to find it." - Balboos HaGadol
Trying to force people to use mananged languages, very bad idea.
-
file:///C:/Documents%20and%20Settings/Smiller/Local%20Settings/Temporary%20Internet%20Files/Content.IE5/YHRATLVN/VS2010RCReadme%5B1%5D.htm#Supported%20Operating%20Systems Contains the following: 2.4.2.3 IntelliSense does not work for C++/CLI IntelliSense is not available for C++/CLI in this release of Visual Studio. However, all browsing features (ClassView, GotoDef, Find All References, Navigate To, etc) are still available for C++/CLI. To resolve this issue: There is no workaround. IntelliSense for C++/CLI is not supported in this release of Visual Studio. To which I say to the VS team at Microsoft, with deep and heartfelt sincerity: F*ck Yo* So, I'm to be further manipulated by the social engineering of ease-of-use? Instead, maybe I'll be even inspired to drop the MSDN subscription and shop elsewhere for a compiler/IDE. (apologies to any in the community the above word-choice may offend)
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"It's a sad state of affairs, indeed, when you start reading my tag lines for some sort of enlightenment. Sadder still, if that's where you need to find it." - Balboos HaGadol
Just so that Microsoft realise how much of a pain this is, please register your interest on Microsoft connect bug id 501921.
