N
news.microsoft.com
Hi all,
First post here. I'm porting an application I wrote in VB6, over to VB.NET
2005.
It could be said I'm really struggling with some (most!) of the syntax of
VB.NET 2005, but I'm getting there. I'm relying a lot, at this point, on
sample code from Microsoft, and other forums about the Internet.
One thing I've painfully noticed (hence the title of this post) is .NET
seems to be GOD AWEFULLY slow!
My VB6 version of my app interacts HEAVILY with Active Directory. My VB6
program starts in approximately 10 seconds, loading all 1300-odd Active
Directory user accounts in a listview.
VB.NET (doing the same thing and based on an example from MSDN) takes almost
60 seconds!
WMI is also painfully slow. A "DiskQuota" DLL call to the server to get
volume useage info under VB6 is instant. A WMI call to get the same
information takes 30 or more seconds.
Why is this? My workstation/VB.NET 2005 platform is Windows XP 64-bit, fully
updated, running on a P4-3.2GHz, 1Gb RAM. My server is Server 2003 SP2 (two
dual core 3.2GHz Xeons). My network is fine.
I'm attempting to port my program to VB.NET to get cross-platform
compatibility. 32-bit/64-bit/workstation and server. My program needs to run
on them all. A 32-bit program using 32-bit DLLs simply won't work on a
64-bit platform - hence the port.
Is .NET inherently slower than VB6 where VB6 is using whatever 32-bit DLL is
needed to get the job done?
Mark
First post here. I'm porting an application I wrote in VB6, over to VB.NET
2005.
It could be said I'm really struggling with some (most!) of the syntax of
VB.NET 2005, but I'm getting there. I'm relying a lot, at this point, on
sample code from Microsoft, and other forums about the Internet.
One thing I've painfully noticed (hence the title of this post) is .NET
seems to be GOD AWEFULLY slow!
My VB6 version of my app interacts HEAVILY with Active Directory. My VB6
program starts in approximately 10 seconds, loading all 1300-odd Active
Directory user accounts in a listview.
VB.NET (doing the same thing and based on an example from MSDN) takes almost
60 seconds!
WMI is also painfully slow. A "DiskQuota" DLL call to the server to get
volume useage info under VB6 is instant. A WMI call to get the same
information takes 30 or more seconds.
Why is this? My workstation/VB.NET 2005 platform is Windows XP 64-bit, fully
updated, running on a P4-3.2GHz, 1Gb RAM. My server is Server 2003 SP2 (two
dual core 3.2GHz Xeons). My network is fine.
I'm attempting to port my program to VB.NET to get cross-platform
compatibility. 32-bit/64-bit/workstation and server. My program needs to run
on them all. A 32-bit program using 32-bit DLLs simply won't work on a
64-bit platform - hence the port.
Is .NET inherently slower than VB6 where VB6 is using whatever 32-bit DLL is
needed to get the job done?
Mark