By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,285 Members | 1,647 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,285 IT Pros & Developers. It's quick & easy.

DotNet inherently more processor intensive or just inefficent?

P: n/a
Bob
I had occasion to unearth one of my old VB6 projects today and had forgotten
how blazingly fast it runs compared to VB.Net. Naturally non-UI code is
faster in DotNet, but everything else, all the GUI stuff is just plain slow
as molasses compared to VB6. I strongly suspect GDI+ is mostly to blame;
regardless, is speed acknowledged as a problem? Is it expected to get fixed
or get slower in the next release?

Bob

Nov 20 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
* "Bob" <no****@nowhere.com> scripsit:
I had occasion to unearth one of my old VB6 projects today and had forgotten
how blazingly fast it runs compared to VB.Net. Naturally non-UI code is
faster in DotNet, but everything else, all the GUI stuff is just plain slow
as molasses compared to VB6. I strongly suspect GDI+ is mostly to blame;
regardless, is speed acknowledged as a problem? Is it expected to get fixed
or get slower in the next release?


I agree, Windows Forms are slightly slower than VB6's forms. And I
think that GDI+ is to blame in some situations, but sometimes the
slowness is caused by wrong usage of .NET's layouting features (docking,
anchoring). I have played around with .NET 2.0 Windows Forms and it
seems to be faster, but I didn't test it with a form containing lots of
controls ;-).

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>
<URL:http://dotnet.mvps.org/dotnet/faqs/>
Nov 20 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.