weird delays when editing code for CF project with VS 2003

[news.austin.rr.com]

Hi,



I'm developing a CF app with VS 2003. When I first started developing the
application months ago VS worked fine. Now as the app has grown larger it
takes a very long time for VS to move to another line after I edit and move
off the current line. What happens is the cursor disappears when I click off
the edited line and takes a long time 10-15 seconds for it to appear on the
new line. VS seams to get hung up when editing.



Has anyone seen this? Is there some kind of fix or something I can turn off
to allow smooth editing? It is so bad that I can edit the code faster in
notepad!



Thanks

 

[Daniel Moth]

I bet (but not much) that you are using VB, right? Exactly how big is the
solution and what is the spec of the machine you are using?

If it contains multiple projects consider working on a single project at a
time...

Cheers
Daniel

 

[news.austin.rr.com]

It is C# with over 10 projects

I bet (but not much) that you are using VB, right? Exactly how big is the
solution and what is the spec of the machine you are using?

If it contains multiple projects consider working on a single project at a
time...

Cheers
Daniel

 

[Daniel Moth]

Sounds like I lost that bet (my money was on the background compiler)... Not
sure what the problem is in your case (you could still try breaking the
solution down in smaller projects...).... Maybe turn off or tweak your
antivirus... If you don't get other replies here try one of the VS groups as
the issue is probably on the tools/compiler side rather than the
framework...

Cheers
Daniel

 

[Sergey Bogdanov]

I also have the enough large solution and have never encountered with
such behaviour. Maybe the problem is not in the concrete solution but in
VS.NET itself. Try to create new solution and see what will happen. If
the worst comes to the worst try to reinstall VS.NET...

Best regards,
Sergey Bogdanov
http://www.sergeybogdanov.com

 

[Jim Popowski]

We had a similar problem that appears to be tied to the usage and/or
network location of our assembly key file. Our solution was to only include
the keyfile when running a release build.
Now Visual Studio performs normally, without the annoying delays.

In assemblyInfo.vb of each of our modules, we include the following:
#If CONFIG = "Release" Then

<Assembly: AssemblyKeyFile("\\<NetworkLocation\MyKeyfile.snk")>

#End If

Hope that helps....

Jim