IDE VB.Net Slowsdown

  • Thread starter Thread starter Alexander
  • Start date Start date
A

Alexander

Hello I was just asking why my VB.Net Editor is working
so slow on bit projects.
I have 3 projects 1 DLL (with 15 Datasets), 1 Application
(with like 20 screens) and 1 Database project...
and every time I have to write something on the code
editor Visual Studio .Net 2003 needs to think and takes
long time to work beacuse it is hard to move from one
line to the other.
Why is the checker so slow? any tips to speed up that?
 
Alexander,

try to close the dynamic help, and see if things speed up then.

Klaus
 
* "Alexander said:
Hello I was just asking why my VB.Net Editor is working
so slow on bit projects.
I have 3 projects 1 DLL (with 15 Datasets), 1 Application
(with like 20 screens) and 1 Database project...
and every time I have to write something on the code
editor Visual Studio .Net 2003 needs to think and takes
long time to work beacuse it is hard to move from one
line to the other.
Why is the checker so slow? any tips to speed up that?
Click to expand...

Does your machine have a lot of RAM? At least 512 MB?
 
It can also be alot slower if you are using project references rather
than dll references.

Are the projects dependant on one another? To speed things up you can
reference the dll of your dependancies rather than their projects. It
means you have to rebuild each project yourself for the changes to be
made available in your main app rather than VS.net doing it
automatically but it does speed things up through reduced project
chaining.

hth

Richard
 
Ok, I am going to try the references idea and the Dynamic Help.
One question?
Is the Dynamic Help the one that highlights the lines or the one that
apears with a lot of links that on top says "Dynamic Help"? or both are
the same?

Because I really like the highlights, It helps me out some times.
 
Hi Alexander,

I posted earlier but the server spat at me...so if this is a double
post thats the reason. I cant remember what i said earlier but
something along the lines of dyanamic help is just the documentation.

As Cor i think suggested, its pretty big and it does chew up processor
cycles because it watches what your doing and then dynamically changes
its suggestions according to that.

The sqiggly lines that we all love so much is the background
compilier. This is where another common place a lag occurs. Its
basically compiling your project in the background as you write your
code.

If your project chaining however its got to compile all the projects
and so you *can* experience this pain-in-the-ass lag with every new
line you type, especially if as Herfreid suggested, you've got a low
spec'd machine.

I thin you can disable the BC in project properties, but i dont know
anyone that flies without it.

hth
Richard
 
Back
Top