.NET Expectations
Mike
Recently getting into the .NET programming, its great to be able to
leverage a tremendously rich core library framework. The improvements
to the VB language now as VB.NET with commonality with C# and C++/CLR
is very exciting (I still think VB is a great RAD tool). Exploring
the compiled disassembly of test code compiled in all three languages,
tells me, its longer (or much less) an issue to consider what language
to use for performance or optimization - its all basically compiled to
use the same core framework. I still have lots to learn about .NET,
but I think that is very very nice!
I have a few questions that maybe experienced .NET developers can help
provide insights.
We have a mixed language product RPC client/server framework. The
server, of course, is written in C/C++ for high performance and most
of the RPC user hosting clients are written in C/C++ as well. Many
utilities are written in VB6 even the old Delphi v3.0.
It is these utilities that we are originally planning to use .NET with
, along with creating .NET SDK client library for our RPC server.
But about using .NET for high performance multi-threaded hosting
applications?
Are there optimization issues? thread-safety issues? Overhead issues?
Thunking? or marshalling issues? How about hidden COM related (STA vs
MTA) issues? I am sure there is always little of each, but are some
of these too significant that prohibit high confidence multi-thread
designs? I ask because when you use other people "libraries" with
lots of unknowns or not yet fully understanding what the "blackbox" is
doing, these kind of quality issues crop up - well, for me, its a
front consideration.
But overall, I'm am considering to explore using VB.NET to developer
some internet hosting server.
Am I expecting too much out of VB.NET and should use C++/CLR or even C#?
Thanks for any feedback you might have.
==
Ben Voigt [C++ MVP]
"Mike" <unk...@unknown.tv> wrote in message
news:u5MYKFw1...@TK2MSFTNGP06.phx.gbl...
You can get good performance from .NET. But it isn't free, you'll still
have to do some serious design. Or pay for a .NET-based scalable server
framework, I've seen a couple but never needed to use one since I'm not into
n-tier client/server work.
One of the best things about .NET is how easy it is to mix languages. If
you need to call native stuff, you can do that efficiently from C++/CLI with
great control. Then you can seamlessly reuse that functionality from C# or
VB.NET.