Is Visual c++.NET 2005 a compromise compared to C# or VB.NET ? advice needed

[s33k3r]

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'd be
lugging legacy baggage if I'm using VC++.NET. Can some one clarify ?

cheers

 

[Michael D. Ober]

If you are comfortable in C/C++, do the entire app in C#. If your comfort
level is with VB 6, do it in VB. If you go the VB route, configure the IDE
to default all VB projects to Option Explicit ON and Option Strict ON.
These two settings will save you tons of headaches down the road. Also, you
may discover that some components work better in one language and others in
a different language. VS 2005 supports this by creating multiple DLL
projects in a single solution. Each project can be in a different language.

Mike Ober.