present. For the future one needs the Oracle.
"Salim Af?ar" <salim@novationnetwork.com> ha scritto nel messaggio
news:7B28907C-8B77-4135-8D94-ED3BAD50B3A7@microsoft.com...
I didn't see any developer using .Net Framework CLR with C++.
CLR with C++ is easy and can be developed in any platform which runs CLR.
MFC only works in Windows.
What do you prefer MFC,CLR or another???
Which one is most used?
Which one will be using more in the future?
I don't have a crystall-ball so I can't predict the future :)
IMHO, if you have existing code base written in MFC, there is no reason to
port to CLR and .NET: just continue with MFC.
(However, there could be elements that may cause a different decision;
there are several factors to consider, and there is no one "unique" rule).
For new projects, I must confess that I like WPF technology a lot. WPF is
a .NET technology, and my personal preference is that I like C# (and also
VB.NET) for managed .NET development.
I know that it is possible to also use C++/CLI for managed code, but
frankly speaking, for managed development I like using C# (or VB.NET).
(I would consider C++/CLI only as a "bridge" between existing C++
code-base and .NET world.)
If you are interested in cross platform, I would suggest C++. C++
compilers are available also on Linux/Unix and I think Mac, too. So, if
you use standard C++ (with standard C++ libraries like STL), and some GUI
toolkit/framework like wxWidgets or QT, you can achieve portability using
C++.
IIRC, Microsoft is going to port Silverlight to Linux and Mac, so also
this managed platform will get you the portability feature.
Just my 2 cents.
Giovanni