G
Gary
I would like to know if I use C# instead of Vb.Net for Server components,
will there a performance improvement ?
TIA,
Gary
will there a performance improvement ?
TIA,
Gary
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
G
gani
gary,
just use the language which you are comfortable with.
there's no difference if you use c# or vb.net.
regards,
gani
pls visit: http://thedeveloperscorner.com.ph
just use the language which you are comfortable with.
there's no difference if you use c# or vb.net.
regards,
gani
pls visit: http://thedeveloperscorner.com.ph
R
Rami Reddy
Gary,
Since all the compiled code ( MSIL ) will be conevrted
by the same ZIT, and moreover it uses the same CLR
facilities, I dont see any performance oriented issues
between these two languages.Howver, it will be nice if
Microsoft come up with certain statistics on this issue,
so that there will be a tested proof.
Best Regards
Rami
Since all the compiled code ( MSIL ) will be conevrted
by the same ZIT, and moreover it uses the same CLR
facilities, I dont see any performance oriented issues
between these two languages.Howver, it will be nice if
Microsoft come up with certain statistics on this issue,
so that there will be a tested proof.
Best Regards
Rami
G
Gary
Thanks a lot.
- Gary -
- Gary -
Rami Reddy said:Gary,
Since all the compiled code ( MSIL ) will be conevrted
by the same ZIT, and moreover it uses the same CLR
facilities, I dont see any performance oriented issues
between these two languages.Howver, it will be nice if
Microsoft come up with certain statistics on this issue,
so that there will be a tested proof.
Best Regards
Rami
W
William Ryan
Gary, there is no real difference betwen the two with one Caveat. They are
the same if you use Strong Typing. If you turn off Option Strict and opt
for late binding or ambiguous typing, there will be a huge difference. Just
b/c Option Strict is Off doesn't mean it will run slower if you code
correctly...but do yourself a favor, turn on Option Strict, leave it on,
never turn it off unless you are forced to at gunpoint. If you do that, you
won't notice any performance differences.
Cheers,
Bill
the same if you use Strong Typing. If you turn off Option Strict and opt
for late binding or ambiguous typing, there will be a huge difference. Just
b/c Option Strict is Off doesn't mean it will run slower if you code
correctly...but do yourself a favor, turn on Option Strict, leave it on,
never turn it off unless you are forced to at gunpoint. If you do that, you
won't notice any performance differences.
Cheers,
Bill
R
Richard A. Lowe
Gary, I would qualify a 'no' answer by saying, as long as
you don't make extensive use of the VB.NET runtime
libraries and don't use weak typing at all.
If you remove the Vb.NET runtime libraries and just use
core vb.net and the framework for everything you do, there
should be very little, if any, difference in performance.
Richard
you don't make extensive use of the VB.NET runtime
libraries and don't use weak typing at all.
If you remove the Vb.NET runtime libraries and just use
core vb.net and the framework for everything you do, there
should be very little, if any, difference in performance.
Richard
W
William Ryan
I'm with you brother. Death to Weak Typing!
Richard A. Lowe said:Gary, I would qualify a 'no' answer by saying, as long as
you don't make extensive use of the VB.NET runtime
libraries and don't use weak typing at all.
If you remove the Vb.NET runtime libraries and just use
core vb.net and the framework for everything you do, there
should be very little, if any, difference in performance.
Richard
H
Harsh Thakur
I mostly agree with whats said above.
But guys, isn't the c# compiler slightly better at
optimizing the code?
At least thats what I've read.
Regards
Harsh Thakur
But guys, isn't the c# compiler slightly better at
optimizing the code?
At least thats what I've read.
Regards
Harsh Thakur
J
Jon Skeet
Harsh Thakur said:I mostly agree with whats said above.
But guys, isn't the c# compiler slightly better at
optimizing the code?
Not that I've heard of. The VB.NET compiler generates a little bit more
code in exception handlers to get ONERROR behaviour (IIRC), and if you
use the VB built-in functions you may incur some cost there, but most
of the real optimisation is done by the JIT, which is the same in both
cases.
At least thats what I've read.
Where, out of interest?