Future of C++ and Windows Programming :: C++

[kuphryn]

Hi.

I posted a topic a few days ago about the future of COM. Overall, most responses implied that COM in general has and will become .NET legacy. The bottomline is Microsoft is dropping COM for .NET.

Microsoft will release Longhorn and I am sure they are working on other versions of their line of OS. According to several articles on the future of Windows development, .NET is taking over Windows.

http://www.codeproject.com/interview..._msdn_0103.asp
http://msdn.microsoft.com/chats/vstu...dio_121802.asp
http://www.eweek.com/article2/0,3959,642737,00.asp

What is the future of C++ programming in Windows? Microsoft can make C++ obsolete under Windows as they push .NET. I have no problem with .NET. I am just curious about C++ programming in Windows because, well, it is fun!

Thanks,
Kuphryn

[Krishnaa]

Man , C/C++ are native windows languages , and not gonna die in coming 100 years at least.

You can see VC++.net hasnt become that much famous as VC++6.0 is ... and will never become.

[souldog]

Who cares about what Microsoft is doing. Do not forget about Unix.

[Wfranc]

Oh... When that time comes, we all move to .NET, or maybe I will create an absolutely new language called Wfranc++ for everyone

[Andreas Masur]

[Moved thread]

[Clearcode]

So long as MS maintains application backward compatibility (i.e can I run MS Word 6 on Longhorn) then the APIs will be the same and so "unmanaged" C++ will still be possible (and indeed desireable).

However it is likely that wholy new MS technologies will be released as framework extensions rather than standard DLLs so unmanaged C++ will not be able to use these.

[Manish Malik]

Originally posted by kuphryn
What is the future of C++ programming in Windows? Microsoft can make C++ obsolete under Windows as they push .NET.

Well, they seem to have forgotten to include C++ examples in .NET documentation, it seems.

[galathaea]

I wouldn't say c++ is related to .NET. They are almost orthogonal, as c++.NET illustrates. The idea is more: which language will our source code be compiled into in the future to run under Windows, and this has consequences for compiler support. Right now, the majority of applications are compiled into the processor's instruction set. .NET applications compile into Microsoft's proprietary intermediate language. Currently, this rules most of Microsoft's major compiler competitors as production applications for .NET. And if Microsoft decides to begin adding OS functionality which is only available through .NET, they will likely face more antitrust suits, as that would illegally tie in two different department domains, as prohibited by the courts.