Long live C++

re: Long live C++

Kris — Fri, 22 Jul 2005 09:22:35 GMT

Good to see this. Just wondering how MS is using the new Managed C++ in their own products. Can you reveal some info just so people like me can be convinced that pursuing Managed C++ once again would be worthwhile. I remember that when VC++ initially started suporting Managed framework I see there was lot of focus on it, but this new release of C++ doesnt seem to have the same fan following inspite of the fact that it has a much cleaner syntax. Any thoughts?

re: Long live C++

wOOdy — Fri, 22 Jul 2005 10:57:12 GMT

I wonder, when (or if) we finally see a similar statement regarding Visual FoxPro from you... This development tool is the perfect fit for the Small and Midrange shops, for which DotNet is just an overkill and who are fading away to other OS platforms and development tools.

re: Long live C++

Wil — Fri, 22 Jul 2005 18:18:15 GMT

> It is absolutely our strong belief in a multi-language ecosystem that led us to provide the same, state of the art of tools for all languages in Visual Studio.

Will Class Designer be available for VC++ in VS2005? If not, when?

> I doubt you’ll find many people creating web apps in C++

None will be, unless Web Forms allows them to do so. Will it?

> C#, Visual Basic.Net, C++ and Java will each occupy a unique place in the programming languages world

Indeed, VS Tools for Office will not support VC++, for that reason. However, that seems contrary to the whole CLI concept. You **ought** to be able to use MSIL without regard for which language's compiler generated it, if the multi-lingual claims for .Net were to be really meaningful. IMHO...

More Interesting Finds

Jason Haley — Sun, 24 Jul 2005 15:42:47 GMT

re: Long live C++

stevetei — Tue, 26 Jul 2005 04:40:57 GMT

>>Just wondering how MS is using the new Managed C++ in their own products. Can you reveal some info just so people like me can be convinced that pursuing Managed C++ once again would be worthwhile.<<

The new version of managed C++ is what we call C++/CLI, and the "worthwhileness" of the language will be pretty self evident when you give it a try. There simply is no better way to do interop between native C++ and managed code, and the language extensions are very elegant. On the VC++ team, we're seeing just about every product group with a large C++ code base that they wish to leverage into .NET seriously considering managed C++ (in 2003) or C++/CLI (in 2005). A shipping product that I know of off the top of my head that uses managed C++ is DirectX, who built their .NET interface in managed C++, but there are several other products in development that use managed C++ or C++/CLI.

>>I remember that when VC++ initially started suporting Managed framework I see there was lot of focus on it, but this new release of C++ doesnt seem to have the same fan following inspite of the fact that it has a much cleaner syntax. Any thoughts? <<

Actually, we're getting overwhelmingly positive feedback on C++/CLI from early adopters. Perhaps it's not getting ink because the fact that VC++ can talk to .NET is not new, but the excitement level is definitely there among those that have tried it.

>>Will Class Designer be available for VC++ in VS2005? If not, when? <<

No, unfortunately this was a feature we were forced to (rather painfully) cut a couple of months ago when it became clear that we wouldn't be able to pull it off in combination with the team's other priorities. I can't say for sure when it will be in, but we'll certainly include it in the planning process for Orcas (the next version of VS after 2005).

>>Indeed, VS Tools for Office will not support VC++, for that reason. However, that seems contrary to the whole CLI concept. You **ought** to be able to use MSIL without regard for which language's compiler generated it, if the multi-lingual claims for .Net were to be really meaningful.<<

The lack of C++ support for VSTO has little to do with the language-neutrality of the .NET platform itself. The issue is that there is language-specific GUI work involved, so the team targeted the C# and VB.NET language for this release because those languages are in higher demand among VSTO developers. We appreciate your feedback on this, as customer demand will dictate whether C++ support is included in a future release of VSTO.

Somasegar s WebLog Long live C | Hair Growth Products

Somasegar s WebLog Long live C | Hair Growth Products — Tue, 09 Jun 2009 11:45:21 GMT

PingBack from http://hairgrowthproducts.info/story.php?id=5962