Future C++.NET support

[danutz_plusplus]

Someone I know said that Microsoft has stopped to provide C++/C++.NET support to new features in the .NET framework. He said that they'll continue to keep C++ support in the .NET framework at the current level, but not provide compatibility with new features. And that VB.NET and C#.NET on the other hand will support the new features.
This seems weird to me, so I wanted to check with you guys. Is this true?
Thanks in advance.

And no, my friend is not actually myself. In case you thought that.:D

[Zaccheus]

I find that very unlikely. One of the selling points of .net is that you can use several different languages all compiling to the same .net byte code.

Besides, with VC++2005 they've introduced a whole new programming language (C++/CLI) - why would they throw all that away?

On the other hand, MS have been pissing off more people than usual recently (for example, declaring they will not support VS2003 on Vista (http://blogs.msdn.com/somasegar/archive/2006/09/26/772250.aspx) !) so anything is possible.
:(

[cilu]

Someone I know said that Microsoft has stopped to provide C++/C++.NET support to new features in the .NET framework. He said that they'll continue to keep C++ support in the .NET framework at the current level, but not provide compatibility with new features. And that VB.NET and C#.NET on the other hand will support the new features.
This seems weird to me, so I wanted to check with you guys. Is this true?
Thanks in advance.

And no, my friend is not actually myself. In case you thought that.:D
Can you provide a link to such a statement from Microsoft? I find it unlikely for the moment. Definitelly, not for VS2007.

[danutz_plusplus]

Can you provide a link to such a statement from Microsoft? I find it unlikely for the moment. Definitelly, not for VS2007.

Well I wasn't saying that I have proof about something like this. I just said that someone I know told me that. And I wasn't sure. So I wanted to see your opinions. Which were pretty much as I thought. Thanks.

[kaixa]

http://msdn2.microsoft.com/en-us/library/ms379617(vs.80).aspx

Sounds appealing :o

[Zaccheus]

http://msdn2.microsoft.com/en-us/library/ms379617(vs.80).aspx

Sounds appealing :oI used C++/CLI for about a year for some of my hobby projects and I recently came to the conclusion (http://www.codeguru.com/forum/showthread.php?t=412701) that I'm actually better off using C# for developing pure managed assemblies.

I think the final straw was discovering that C++/CLI does not let you auto-dispose received references (C++/CLI stack semantics - receiving a C++/CLI handle (http://www.codeguru.com/forum/showthread.php?t=412448)), something you can do in C# via the using() statement.

Of course C++/CLI in non-safe mode does allow you to mix native and managed code but that seems very messy to me.