[Connect bug] VC++ 2010 : C++/CLI does not support variant delegates/interfaces
-
Rajesh R Subramanian wrote:
I've voted there
It's kinda sad how few people here did the same. It's only at 9 votes now and was 4 before I cast mine. The entire point of posting connect bug reports here is the I'll Scratch Your Back If You Scratch Mine Principle. It all falls apart if we don't vote each other's bugs to the TEOTWAWKI level necessary to have MS patch them in the next major release.
3x12=36 2x12=24 1x12=12 0x12=18
Some of us aren't under the delusion that Microsoft actually fixes anything on Connect based on any meaningful criteria. (Heck, there's a bug in Visual Studio 2010 that has something like 60 votes and Microsoft still pretends it doesn't happen.)
-
Deyan Georgiev wrote:
For not using it? Why, is it the CLI in low supply these days?
Yeah big joke, funny guy! :rolleyes:
Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
Don’t play sarcastic on me or I’ll stop hammering at my boss that we need a copy of your “Extending MFC applications with C#”. :-D
The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word. Advertise here – minimum three posts per day are guaranteed.
-
Don’t play sarcastic on me or I’ll stop hammering at my boss that we need a copy of your “Extending MFC applications with C#”. :-D
The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word. Advertise here – minimum three posts per day are guaranteed.
Deyan Georgiev wrote:
Don’t play sarcastic on me or I’ll stop hammering at my boss that we need a copy of your “Extending MFC applications with C#”.
:laugh: Alright, but you've gotta get your boss to buy a copy for each developer there!
Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
-
Rajesh R Subramanian wrote:
I've voted there
It's kinda sad how few people here did the same. It's only at 9 votes now and was 4 before I cast mine. The entire point of posting connect bug reports here is the I'll Scratch Your Back If You Scratch Mine Principle. It all falls apart if we don't vote each other's bugs to the TEOTWAWKI level necessary to have MS patch them in the next major release.
3x12=36 2x12=24 1x12=12 0x12=18
Dan Neely wrote:
It's kinda sad how few people here did the same. It's only at 9 votes now and was 4 before I cast mine. The entire point of posting connect bug reports here is the I'll Scratch Your Back If You Scratch Mine Principle. It all falls apart if we don't vote each other's bugs to the TEOTWAWKI level necessary to have MS patch them in the next major release.
Yeah I was kinda hoping for a few more votes than this really. I think it's the need to sign in using a .NET Passport that makes people think it's too much hassle :sigh:
Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
-
Some of us aren't under the delusion that Microsoft actually fixes anything on Connect based on any meaningful criteria. (Heck, there's a bug in Visual Studio 2010 that has something like 60 votes and Microsoft still pretends it doesn't happen.)
In my experience, the VC++ team has been quite responsive to compiler issues. If they've given anything a pass, it's usually been due to time constraints.
Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
-
Phil Martin... wrote:
Typing with a baby in one hand is slow.
Typing while holding a toddler who thinks keyboards are great fun is ever slower.
Tell me about it. My 3 year old is fascinated by computers (and rightly so) and just loves me opening up a work processor and letting her type out the alphabet and some numbers and words and things. I'm sure she'll be using Twitter and FriendFace well before me too.
-
I've found it very useful for interop between Managed (C#,etc.) and legacy unmanaged C++ code. It's much more efficient than COM interop, and more flexible than pInvoke for scenarios where COM interop is not a choice). I would not use it for anything more significant than a thin interop layer, however.
I've used it to interop with "legacy" static libraries (.lib). Legacy meaning vendors who think people still use VC 6.0, and provide C++ libraries as their only interop.
-
Other than Nish, here on CP, and myself, I don't know a soul who has written any C++/CLI code, even to try it out. I've written some C++/CLI code, just to see what it could do. Wasn't impressed and found the lack of interest by Microsoft to document and help you along to be a major show stopper. (If you've written C++/CLI, that makes three.)