VB.NET VERY Slow

[Guest]

Hi,
I'm new to VB.Net but have noticed a few things about the dev interface that
is really starting to get annoying. First of all, while trying to work with a
form and the code module for the form I notice switching back and forth
between the form and code window is very slow, specially if I select the
form. Im in the process of trying to add control names into my code and
wanted to copy and paste each control into the function, but each time I
switch from/to the form it take about 15 to 30 secs before I have control of
the form again. It could be that the enviroment is trying to check the code.
Is there a way to turn off some of these features (Like auto check functions,
ect...). Has anyone noticed things like that. Thanks for any suggestions.
Michael

 

[Ken Tucker [MVP]]

Hi,

Make sure you have at least have the recommended requirements
for vb.net 2003.

http://msdn.microsoft.com/vbasic/productinfo/sysreqs/default.aspx

Check you computer for spy ware and viruses. Below are some
links to some free programs I find to work well.

Microsoft Antispyware beta
http://www.microsoft.com/athome/security/spyware/software/default.mspx

AVG Antivirus has a free edition for home users.
http://www.grisoft.com/doc/40/lng/us/tpl/tpl01

Ken
----------------
Hi,
I'm new to VB.Net but have noticed a few things about the dev interface that
is really starting to get annoying. First of all, while trying to work with
a
form and the code module for the form I notice switching back and forth
between the form and code window is very slow, specially if I select the
form. Im in the process of trying to add control names into my code and
wanted to copy and paste each control into the function, but each time I
switch from/to the form it take about 15 to 30 secs before I have control of
the form again. It could be that the enviroment is trying to check the code.
Is there a way to turn off some of these features (Like auto check
functions,
ect...). Has anyone noticed things like that. Thanks for any suggestions.
Michael

 

[rawCoder]

First , This cant be a problem of VB.NET by itself.
Whatever is the issue, its related to the Visual Studio .NET

Second, I dont have a fast PC but I can switch between design/code view in
less than a second.
Do you really think microsoft will ship a product which has 15-20 second
delay in switching from one view to another.

One can guess that there must be some problem with your hardware/software
configuration.

and yes VB.NET is VERY SLOW.

THANK YOU
rawCoder

 

[Guest]

Thanks for the reply guys,
Could it be that there are about 100 controls on the form? I'm sure that
could affect it, but the same form (same layout and controls) in VB6 I have
no trouble switching between code/form windows. I also notice that VS.net
will jump to the top of the form when I switch back to the form, if I have
scrolled down the form. I don't want that to happen either. I notice that in
the code window sometimes also. Thanks again for the info.
Michael

 

[Guest]

Michael, I've noticed in my experience that if you have the reformatting
option selected and you have very large classes with many lines of code that
there is a brief pause while the IDEchecks the format of the class, I don't
think it's 15 seconds maybe 5 on my machine (PIII 1.1g .5g ram) this happens
when you have changes and the changes are saved...
Look in Tools>Options>Text Editor>Basic>VB Specific in the VS.NET IDE
uncheck Pretty listing of code, see if that solves. I like the "pretty"
formatting myself, so I'm willing to wait the few seconds for large classes...

Dan

 

[Cor Ligthert]

Michael,

Which version because 2002 was in some cases very slow.

Cor

 

[Herfried K. Wagner [MVP]]

Could it be that there are about 100 controls on the form? I'm sure that
could affect it, but the same form (same layout and controls) in VB6 I
have
no trouble switching between code/form windows.

Windows are not cheap objects
<URL:http://blogs.msdn.com/oldnewthing/archive/2005/03/15/395866.aspx>

In VB6, labels and image controls were windowless and for this reason
required few resources, in .NET all controls are windows.