F
Fabiano
Please,
wich language the world is using? Performance, costs and on?
tks
Fabiano
wich language the world is using? Performance, costs and on?
tks
Fabiano
M
Mary Chipman
It depends on which language is more comfortable than any other single
factor. That being said, I'd not want to program Office automation
using C#, so in some cases you need to consider the application you
are building. It's always cheaper to program in a language you already
know or in one you can learn more quickly than another. However, even
if you choose VB.NET, you'll end up needing to learn at least a little
C#. Once you learn one, learning the other is pretty easy. What's more
important is getting comfortable with the base class library in the
Framework.
-- Mary
MCW Technologies
http://www.mcwtech.com
factor. That being said, I'd not want to program Office automation
using C#, so in some cases you need to consider the application you
are building. It's always cheaper to program in a language you already
know or in one you can learn more quickly than another. However, even
if you choose VB.NET, you'll end up needing to learn at least a little
C#. Once you learn one, learning the other is pretty easy. What's more
important is getting comfortable with the base class library in the
Framework.
-- Mary
MCW Technologies
http://www.mcwtech.com
M
Martin Carolan
Appartenly C#.NET is 5% better for performance, i use VB.NET though...
C
Chris Taylor
Hi,
First, Martin sorry to reply to your post but it is the only one visible in
my reader. My remarks are not directed at your post
.
I am a C# guy myself, but I do a tremedous amount of VB.NET and I feel that
they are both very good environments. If you use VB.NET and you are
concerned about performance, then make sure that you steer clear of the
functionality in Microsoft.VisualBasic namespace, rather use the
functionality from the System.* namespaces. And just the silly little things
like leaving it to the compiler to do implicit type conversion, those are
the things that really hurt performance. So rather than assigning a integer
to a string and letting the compiler sortout the conversion, do it
explicitly, the code will be much tighter.
Hope this helps
First, Martin sorry to reply to your post but it is the only one visible in
my reader. My remarks are not directed at your post
.I am a C# guy myself, but I do a tremedous amount of VB.NET and I feel that
they are both very good environments. If you use VB.NET and you are
concerned about performance, then make sure that you steer clear of the
functionality in Microsoft.VisualBasic namespace, rather use the
functionality from the System.* namespaces. And just the silly little things
like leaving it to the compiler to do implicit type conversion, those are
the things that really hurt performance. So rather than assigning a integer
to a string and letting the compiler sortout the conversion, do it
explicitly, the code will be much tighter.
Hope this helps