s33k3r wrote:
hi all
I've been assigned the task of designing a distributed application
from scratch. I have no legacy applications to integrate or support.
But I'm faced with the question : Is visual c++.net a compromise when
compared to C# or VB.NET.
Considering the fact that even COM+ enterprise services is going to be
rewritten in managed code in vista, I'd like to understand if I'm
lugging legacy baggage if I'm using VC++.NET. Can some one clarify ?
By the way, in addition to Bruno's comments (which I agree with 100%), I'll
add that even in Vista there are tons of new, native-only bits of
functionality. In fact, within the OS itself (kernel, shell, user32, gdi32,
etc), none of the new features are implemented in managed code, and many of
them are inaccessible except from native code. If you plan to target Vista
and make use of Vitsa features (other than WPF, which is really just an
add-on and also runs on XP), then C++ still has lots to offer over C#.
There's no architectural change to COM+ ES in Vista - it's the same, native
code that it's always been (and always will be). There's good support for
interoping with COM+ in .NET 2.0 and 3.0, so it's accessible from C#, C++
can use the .NET wrappers from managed code, or use the native
interfaces/functions directly from native code.
-cd