Typing in Visual Studio 2005 Text Editor is extremely slow

Question

Has anyone else noticed that typing in Visual Studio 2005 is extremely slow?  Whey I type it seems that the screen is always 2 words behind where my hands are.  It makes it extremely frustrating to get anything done.

I'm mainly referring to C# code.  It seems like Intellisense is going nuts trying to guess every word I'm going to type and never actually prints the characters to the screen.

Has anyone else experienced this?  Is there an option I can turn off to get my text editor back?!

By the way, I have a very fast computer with Dual 3.0 GHz Zeons with 3GB memory and everything else that should make "typing" very fast.

Answer 1

We’ve recently discovered an issue where the Navigation Bar can cause this sort of slow-down.  Can you try going to Tools->Options->Text Editor->C#->General and unchecking the “Navigation bar” option, and see if that makes a difference?

Thanks,
--
Kevin
[e-mail]

Answer 2

Wow!  Turning that option off made all of the difference in the world.  Typing and intellisense is in "real-time" now.  :) Thanks for getting back to me on this.

Answer 3

Just an FYI that I found this post via Google and tried the suggestion.  It immediately did the trick.  My machine is a dual processor with a gig of RAM, but it is 4+ years old.  I thought VS 2005 was making me realize I needed a new machine.  But unchecking this open has things flying again.

Thanks!
-joe

Answer 4

I had the same problem, but in Visual Basic! - However the Navigation Bar option in the Basic menu is grayed out,  BUT,  if you goto Tools->Options->Text Editor->All Languages->General and unchecking the “Navigation bar” option there it solves the problem in VB as well!!

Answer 5

I've been trying to find a way to write a macro to toggle the Navigation Bar - so I can turn it on for the times I need it. Of course, I'd like to leave it on all the time, but it's just too sloooooooow.

Anyone come across any macros for toggling it?

Answer 6

    Sub ToggleCSharpNavigationBar()

        Dim properties As EnvDTE.Properties = DTE.Properties("TextEditor", "CSharp")

        Dim shown As Boolean = properties.Item("ShowNavigationBar").Value

        properties.Item("ShowNavigationBar").Value = Not shown

    End Sub

Answer 7

Excellent - that works perfectly! Just what I wanted!

Many thanks! :)

Answer 8

I tried this solution, but made no difference for me. Typing is still dreadfully slow for large .cs files  with lots of references. Any other suggestions?

Answer 9

I had the same problem - very slow typing -   after I turned on wordwrap.

I have now  turned it off and everything works fine.

Disabe wordwrap at: Tools>Options>TextEditor >C#>General>

Answer 10

Wow, word wrap causing this!!!  Is there a hot fix to fix both of these issues yet?

Cause man, I need my word wrap but this is nuts!

Answer 11

What I've notice is that if u have form opened in Design Time it's slowing down the typing. It seems like is trying to update the designer on every keystroke. Anyway once u close the designer in most of the time it will speed up the typing.

Answer 12

I have both Navigation Bar and WordWrap turned off, but my CPU still stays pegged at 100%.  What's going on?!?

Rob

Answer 13

I did everything here and it's still horriable.  If I change the name of a textbox and click off it takes way to long to change. I'm using a p4 2.6 512 ram 7200hd and I just can't make heads or tails anymore. Anyone with any other ideas please help...

I'm programming windows forms in vb.net

Answer 14

Basically, as far as I can tell by this entire discussion and my own experiences is that the code editor is essentially unusable (or at least incredibly slow) for any form that has > 2000 lines of code in it. You can make that worse by putting on word-wrap, using the Navigation bar, having the form in design mode while you're editing your code behind etc. etc. etc. (All bugs other than the slowness of the editor with even moderately large code files)

The end result of this is that MS needs to release a public patch right away for the code editor to fix all of these things. Everyone is running into it unless they're doing "Hello World" and it looks bad on MS. 


Please, please please MS, fix this stuff quickly and get us a patch before SP1... this can't wait.

Answer 15

More than 2,000 lines in a form class? Crikey, that's a lot. I usually refactor and encapsulate/delegate long before then!

I think there must me more than one issue at work here. I had the slowdown in modules with only a few hundred lines, and that was fixed by turning off the navigation bar.

I don't have any modules with more than 2,000 lines of code, so I've never encountered the problem due to that.

Answer 16

Hi,

I am Suma Sushilendra from C# IDE team. We have identified and fixed several perf issues that our users reported at "MSDN feedback center" on the RTM version of VS2005, in our recent builds.

One thing that really helps us in identifying an issue that is reported in newsgroups/feedback center etc, as being a new issue or a known issue is a callstack of the problem. To get this, try closing the IDE when the slowness/sluggishness/unresponsiveness happens. When you try to close a non-responding application watson report gets generated and you should then choose to "Send the error information" on this dialog. Then you can go to "Event Viewer" (http://support.microsoft.com/default.aspx?scid=kb;en-us;308427) and get the Watson bucket ID ( a big number) for the watson report that got submitted. Mentioning this bucket ID in the bug that you submit or issue that you report in the forums, we will be able to immediately link the issue to either an already known issue or to fix that after determining that it is a new one.

Sorry for the inconviniences caused because of these perf issues. Please help us identify and nail these issues down by providing more info such as the one explained above.

Thanks again for all of your time on reporting these issues,

 

Suma

Answer 17

JohnGalt wrote:

Basically, as far as I can tell by this entire discussion and my own experiences is that the code editor is essentially unusable (or at least incredibly slow) for any form that has > 2000 lines of code in it. You can make that worse by putting on word-wrap, using the Navigation bar, having the form in design mode while you're editing your code behind etc. etc. etc. (All bugs other than the slowness of the editor with even moderately large code files) The end result of this is that MS needs to release a public patch right away for the code editor to fix all of these things. Everyone is running into it unless they're doing "Hello World" and it looks bad on MS.  Please, please please MS, fix this stuff quickly and get us a patch before SP1... this can't wait.

I agree, this is ridiculous.

Answer 18

I turned off Navigation problem and word wrap. Text faster is no faster

So what is the solution to this problem other than turning off navigation bar and word wrap?

 

 

Answer 19

Hi Mani,

As I said in my earlier post, it would be very helpful for us to have a callstack (or a repro case) of the code when the issue happens that would help us in either determining that the issue is same as the one we have seen before or the new issue that we then fix.

As for the navigation bar issue, it has been fixed in our internal builds and is marked to be included in SP1 for VS2005 whose schedule information can be got at http://msdn.microsoft.com/vstudio/support/servicing/sp1_vs05/default.aspx

Again, I am really sorry for the inconvinience this performance issue has caused and I really want to get to the bottom of this issue that you are seeing.

Also, there are others on this thread that have said that disabling the navigation bar didn't help. I would really appreciate if I could get a callstack or the repro case for this issue.

Feel free to email me at [e-mail] 

Thanks

Suma

Answer 20

thanks for these information

Answer 21

I am using VB 2005 and I have this problem and it is a show stopper. Its crazy for this to be happening. WE CANNOT WAIT FOR A SERVICE PACK in the Q3 of 2006. By the time MS is late as usual with service packs, we are looking at 2007.

WE may as well dump VS 2005 and return to VS 2003.

My CPU going to 100% every couple of minutes in between typing into the IDE.

Its truly amazing to see MS talking about all the glorious things that VS 2005 will do, including "increase productivity". Thats a big laugh, I will never understand how with all the beta testing and high powered programmers at MS, a common problem that kills the IDE gets through to early adopters.

None of the suggestions about navigation bar or word wrap helps.

I was excited but now AM HURT.

Clif

 

Answer 22

Clif,

If you haven't done so already, I suggest posting about the problems you're having with the VB editor in the Visual Basic IDE forum. Performance issues while editing VB may have nothing to do with performance issues while editing C#, and the VB team will want the feedback.

Thanks,
Tom Meschter
Software Dev, Visual C# IDE

Answer 23

Hi Clif,

I'm the VB Dev trying to track down our perf issues. It's possible the slow down you are seeing is related a known issue with Code Snippets.

Try going to Tools -> Code Snippet Manager and remove any snippet directories that you added manually. Basicaly the issue here is if you add a directory that is underneath a "busy" directory you will experience this kind of delay. An example would be to add a directory "c:\snippets" or to add a directory located under your "My DOcuments" folder.

If this doesn't address your issue please contact me directly at [e-mail] and I will help figure out the problem.

Once we establish the problem I will post a resolution to this thread.

 

Thanks

Cameron McColl

VB.NET Development Team

Answer 24

Just wanted to thank both Tom and Cameron for their info.

Cameron, I have not created any new snippets.

Whilst the environment is genarally slow and annoying, I have found that turning off the Refactoring (DevExpress add-in ) helps to reduce that awful long wait between keystrokes that occurs.

I also think that the # of lines of code also affect the editor so i have gone about splitting up code whereever i can to  reduce the wait.

As suggested, I will post my concerns in the VB .NET forum.

Thanks again.

Clif

Answer 25

I'd like to add my company's experience to the mix.  We had a large VS2003 ASP.NET 1.1 project consisting of 8 projects having a mix of C# and VB.NET plus one Web project in VB.NET.  We just finished our conversion to VS2005.  We used the new Web Application feature to convert our existing project as-is because there were too many breaking changes in the new web project format.

The editor is an absolute dog.  Quite unusable.  It goes out to lunch every 5 seconds just as the other posters have indicated.  As another reader did, I ran Sysinternals filemon.exe to monitor what files devenv.exe was accessing.  Unbelievably, it touches every single file in the solution (and we have hundreds) almost every 5 seconds!  When this happens the CPU spikes to 100% and the IDE becomes completely nonresponsive, unusable.

We've tried every suggestion mentioned in this thread to no avail.  As a last ditch effort I spent 2 hours completely rebuilding the project from scratch, manually adding back in all the references and namespace imports (for the VB.NET projects).  No improvement at all.

I'm absolutely shocked and dismayed.  I paid how much for this?  It's truly unusable and Microsoft should be ashamed of itself!  How is my team supposed to get any work done like this?

I'm beside myself, and very frustrated.  I can't believe this didn't come out in beta testing.  At first I thought maybe this was because we're using this new Web Application project format, but I see from other posters that it's happening in all manner and style of projects.

Question: I'm not sure if this has anything to do with anything, but on my dev machine, I have the TEMP directory mapped to a separate partition on a separate drive from my VS project.  I've noticed a temporary lag/freeze in my browser when downloading files from the internet due to the browser having to shift a completed file from one partition to another.  Could something similar be happening here?  I am going to change my TEMP dir and see.

Answer 26

Sadly, TEMP location changes have had little effect on the performance.  Still slow. :(

Answer 27

This is a (very) long shot, but you might try turning off AutoRecover. This option can be found by going to the Tools\Options... menu item and then navigating to the Environment\AutoRecover group. I don't really expect that it will help, but it's worth a shot.

Since you're developing an ASP.NET solution, you should also try posting about this in the ASP.NET forums.

-Tom Meschter
Software Dev, Visual C# IDE

Answer 28

I'm wondering if there's any update to this issue.  There's lots of suggested fixes but its mostly ancedotal.

 

Microsoft: is there anything out there listing the recommended ways to fix this problem since I presume there's no code fix yet.

 

Answer 29

Hi,

Just so I wrap this thread up, people who reported their issues also emailed me and I worked with them offline and could get help for them. Just to summarize,

1) One of the customers on this thread had a C# and VB mixed web app. But the slowness happened only in VB web pages and not in C#. So, it is very important to try to isolate the problem and report it in the exact location/situation that it is seen to help us get to the root of it quickly. As Tom mentions in one of the posts on this thread, if the IDE is slow in VB apps, the right forum to report it on is "Visual Basic IDE" forum.

2) Another customer had an addin that was outdated because of which the VS IDE was either hanging or crashing on typing. Isolating this and getting the updated addin fixed the problem.

3) Another customer who mailed me also sent me the watson bucket ID that he got while he tried to close an unresponsive IDE and I figured that it is a known issue and we have fixed in the internal builds.

We are very much interested in getting to the bottom of each and every issue you bump into and it is very important for us to be able to get a repro or callstack/dump/watson bucket id of the issue to be able to really help you.

That said, thanks to one and all who have taken time to report the issues they have seen with VS. Thanks for helping us make the product better. I appreciate your effort and time spent on all these.

Thanks

Suma Sushilendra

 

Answer 30

Suma: Thanks for your response.  I didn't appreciate there were so many specific causes to the problem. I can see why general solution is not possible.

If this problem recurrs for me with frequency can I contact you with my specifics?

At the moment things are ok.

 

Thanks

Vince

Answer 31

Yes, you can contact me at [e-mail] with details of the issue and I will be able to help you or get help for you.

 

Thanks

Suma Sushilendra

Answer 32

FYI, MS has provided me with a fix for the Navigation Bar issue and will be releasing a hotfix shortly.

I'm working with them on the word-wrap issue at the same time so hopefully that gets fixed in the same hotfix.

Now if I could only get the other two show stoppers that waste my day fixed, I'd be really happy :)

Answer 33

Disable "Tools\Options\Text Editor\General\Track changes".

Answer 34

This did not work for me. I went to "All Languages" as well as separately into each language and unchecked the "Navigation bar", but when I open one of the bigger *.asp files it takes on average 6 sec for a single character I type to appear on the screen. The machine has 4G of memory  and an Intel Xeo processor and there no delay in say Interdev.

Answer 35

Nope, that does not help either.

Answer 36

Clif,
I am having the same problem using C++.
Did you ever get a solution for the problem besides getting your money back?

Rich

Answer 37

Hi,

This did it for us!! Our WinForms needed ages to open, turning Track Changes off works perfectly!

Thank you!!

Berndt

 

Answer 38

Tried all tricks but still slow. Any SP out already?

Also I have installed Ramdisk, is there anyway that I can speed up VS by move some temporary directories to the ramdisk?

Answer 39

Hello,

You can found the service pack 1 beta here http://www.microsoft.com/downloads/details.aspx?FamilyID=8D702463-674B-4978-9E22-C989130F6553&displaylang=en

Here is my recommendation to resolve slowness :

 - remove navigation bar

 - remove word wrapping

 - remove remote projects in "HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\ProjectMRUList"

 - add dword OptimizePDB in "HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\VB Editor" at 1 (solution need  to be regenerate)

 - apply service pack beta 1 (not recommanded in production environement

 - disable add-ins like Refactor, CodeRush, Ankh ... try to enable one by one

 - close all applications and clear the %TMP% directory (not recommended to beginners)

 - move your solutions in another disk than visual studio 2005 if possible

 - disable html validation, enable it sometimes or when publishing.

 - build your own tool bar, grouping your commun tasks like build, open file, undo, left ajust, top ajust ... and disable all other tool bars

Best regards,

Answer 40

BTW, SP1 beta DOES NOT fix this.

It's still dog slow, especially with word wrap on and especially with 64 bit OSes.

Answer 41

The performance of Visual Studio 2005 has driven me mad. When I work on my webform, the PC will slow down within half an hour. My .net project is very simple already, it contains only a few pages, everytime I only open two to three pages to edit. the most complicated page only has only two FormViews and one Gridview, when I switch between design mode and source mode, or among different templates, or switch between webform and coding, the usage of RAM is increased sharply, though CPU usage is still low, the PC becomes extremely slow. The only way is to restart the PC and release the RAM. The PC has a 2.9GH CPU and 1.0G physical RAM.

I have turned off Text Wrap and navigation bar in the options, but the problem persists. Since there is not positive feedback on the SP1 beta yet, I will not consider to apply the service patch, who knows whether it is another nightmare.

Answer 42

This is my experience with the slow editor i c#:

I have several winform projects where this is a problem and the problem is proportional with the numbers of controls on the forms.

Today I did some tests to find out when the slowness occurs.

In my project I have a Mainform.cs and I open this in the designer, no other files are open. Then I open the code behind file by pressing F7. I try to type something into the code behind file and the speed is allright. Now I run the program in debug mode by pressing F5. The program runs and I close it again. In VS2005 the code behind file is still in the foreground, and I type something into the editor. Now there is a problem, every character typed takes 1 second to show up and my CPU uses 100%

Now comes the strange part. I click on the tab for the designer of my form, don't change anything here but only click on the code behind file tab again to get it into the foreground again. Typing something in the code behing file editor is now normal speed again !

I can do this sequence with debugging and switching tabs again and every time the same result. I have no add-ins loaded into VS2005

Can anyone reproduce the same behavior in VS2005, or is it just a strange thing on my computer ?

 

Answer 43

This is my experience with the slow editor i c#:

I have several winform projects where this is a problem and the problem is proportional with the numbers of controls on the forms.

Today I did some tests to find out when the slowness occurs.

In my project I have a Mainform.cs and I open this in the designer, no other files are open. Then I open the code behind file by pressing F7. I try to type something into the code behind file and the speed is allright. Now I run the program in debug mode by pressing F5. The program runs and I close it again. In VS2005 the code behind file is still in the foreground, and I type something into the editor. Now there is a problem, every character typed takes 1 second to show up and my CPU uses 100%

Now comes the strange part. I click on the tab for the designer of my form, don't change anything here but only click on the code behind file tab again to get it into the foreground again. Typing something in the code behing file editor is now normal speed again !

I can do this sequence with debugging and switching tabs again and every time the same result. I have no add-ins loaded into VS2005

Can anyone reproduce the same behavior in VS2005, or is it just a strange thing on my computer ?

Answer 44

pilchieMS wrote:

We’ve recently discovered an issue where the Navigation Bar can cause this sort of slow-down. Can you try going to Tools->Options->Text Editor->C#->General and unchecking the “Navigation bar” option, and see if that makes a difference?

FWIW, this also solved my problem in VS2003. It was blazing fast at first start-up, but the response of the editor slowed down with each build and each source/designer switch. Restarting VS would bring it back to normal. Simply turning off the Navigation Bar has kept me cruising and is withstanding build after build now. (I am uncertain if I am running SP1 for VS2003.)

Answer 45

hi,

http://support.microsoft.com/kb/922449/en-us

For my problem in the previous post, it is due to another bug with Visual Studio 2005. Though microsoft states that hotfix is available, and it is also included in the sp1 beta, I can't download it. Can anyone advise how to download it quickly? Thanks.

Answer 46

Hi,

http://support.microsoft.com/contactus/?ws=support has the details on how you can get the hotfix.

Basically you need to call up PSS at the following number and cite the KB number 922449 to get the hotfix from them.

Telephone
(800) MICROSOFT (642-7676)

Hope this helps,

Suma Sushilendra [MSFT]

Answer 47

I didn't have any issues of slowness in the IDE until I upgraded my browser to IE7.  After the upgrade, I began to experience extreme slowness when typing on source view for asp.net apps.  It got to the point where it would take over 10 seconds to see a character after hitting the key.  I tried some of the suggestions here to no avail.

I removed IE7, and the problem went away.

Answer 48

Lexter wrote:

I didn't have any issues of slowness in the IDE until I upgraded my browser to IE7.  After the upgrade, I began to experience extreme slowness when typing on source view for asp.net apps.  It got to the point where it would take over 10 seconds to see a character after hitting the key.  I tried some of the suggestions here to no avail. I removed IE7, and the problem went away.

Interesting, I was doing some web preformance tests with Team Stuite and noticed they decreased in speed dramatically after intalling the last beta of IE7.  It was shrugged off as non-reproducable.

Have you logged a bug on connect.microsoft.com for this?

Answer 49

A lot of problems occurs with Internet Explorer 7 - no doubt about this.
I have reported several bugs on connect.microsoft.com, but I was ignored by the Microsoft IE team.

I especially found this to be critical, as I represented myself as a Software Development Engineer, and I reported several features/bugs with IE7 working "together" with Visual Studio 2005.

Even more, I am frustrated how they could ignore this, as we have MSDN Team Suite licenses all around.

Anyway, sorry for this outbreak, I just needed to get rid of my frustrations!

Regarding VS2005, i experience severe response time, especially when working with remote web projects - which is essential for an Enterprise developer like myself.

Do we get totally ignored by MS here, or will they provide us with a fix?
And whats with all the "you need to contact support in order to get the patch"?!

When we have production issues, we release hotfix' as they come available - we do not burden our customers with all the beurucratic bull****.

Let me state out as a last comment that I am a huge supporter of Microsoft.
I normally consider there products to bee good, but with IE7, VS2005 and SQL2005 something went terrible wrong.

I mean, they added a lot of new nice and good stuff - no doubt about that, but a lot of the features I personally (and lure me, if not other developers has the same preferences) come to like (and working features as well), vanished with the products mention before.

This is unacceptable, and at the very least, MS should listen to the users of the BETA program - otherwise, what the point in BETA testing and provide valualbe feedback?! I dont get my time back for providing valuable feedback to Microsoft, and there released products surely indicates to me, that they give a *** about my reports (which, for the record, was very diplomatic and straight forward).

I have so much more i want to write, but I can see i get of topic here .. please Microsoft - do support your professional users; it is the very least you can do, especially considering how expensive the MSDN Universal / MSDN Team Suite licenses are.

Give us value for the money :)

Answer 50

I just tried the disable nagivation bar trick, seems to work for C++ IDE (native code). looks like it is not fixed in SP1 cuz I am running SP1 Beta 1 already.

Answer 51

Was there every a solution for this?

I'm using VB.net express. It has service pack 1 installed, the navigation bar is off, word wrapping is off, etc.. but the text editor is unusable. My machine completely locks up about every 5 to 10 seconds while trying to type.

Trying to use the edit and continue is simply the most frustrating experience (well actually not having it since VB6 was but that's another story)

Again, Service Pack 1 didn't solve the problem so I'm wondering if some other solution was presented.

Specifics of my system.

 

Microsoft Visual Studio 2005
Version 8.0.50727.762  (SP.050727-7600)
Microsoft .NET Framework
Version 2.0.50727

 

Installed Edition: VB Express

 

Microsoft Visual Basic 2005   76541-000-0000011-00124
Microsoft Visual Basic 2005

------------------
System Information
------------------
Time of this report: 2/1/2007, 17:53:04
Machine name: ORTHANC
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.  
System Model: 7VRX                           
BIOS: Version 1.00                   
Processor: AMD Athlon(tm) XP 1800+,  MMX,  3DNow, ~1.5GHz
Memory: 512MB RAM
Page File: 371MB used, 879MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: None
DxDiag Version: 5.03.2600.2180 32bit Unicode

Answer 52

Even with SP1, if you're editing and continuing or even just editing normally and you have the form open, periodically (not always) it will read any typing you make in the code behind as a change to the form. It will then reload the form every character you type.  If you close the designer then it will speed up again.

However, it's still slow as molasis on big forms editing code even if you turn everything off as above, and forget word wrap, it's just completely unusable on any good sized form.

Oh, and I was told that this wasn't going to be fixed until Orcas and thus that I was going to have to pay money for a bug fix.  Obviously I am not impressed!!!

This should be fixed yesterday and a public hotfix should be released immediately.

Answer 53

David,

You're best off bringing up issues about performance problems while typing in VB in the VB.Net Forums. While there are a few issues that affect multiple languages, such as the Nav Bar, there are others that are language specific. We won't be much help in diagnosing the particular problems you're facing here in the C# forums.

-Tom Meschter
Software Dev, Visual C# IDE

Answer 54

I've noticed that after installing SP1 the performance of the text editor is, if anything, worse than before.  Turning off particular features doesn't seem to help, and isn't really a preferred fix anyway (since I tend to use the Navigation bar).  The performance is especially bad on large files in both C++ and C# projects (greater than 1000 lines), with the CPU spiking to 100% on simple text edits.  The problem could be related to intellisense, since the CPU tends to get consumed whenever the intellisence dropdown would normally appear, when changing method signatures, etc. 

Is there any information that I can provide that would help solve this problem?  It's made visual studio very difficult to use, and I've had to resort to an external text editor for my larger code files. 

Answer 55

Me too!!! It's brutal!

Answer 56

I was able to get acceptable performance by deleting the task list.

In my case, every time I'd make a single edit (of any shape or form) in the text editor, the IDE would try to update the task list. Well, after upgrading a project from VB6 I had over 3700 tasks marked as 'UPGRADE WARNING'. 99.99% of them were simply "no default property for nnn found.' (who cares?). So it was going through all 3700 items looking for items it could update.

To solve this, I went to Tools->Options and from the tree list selected Environment->Task List. I unchecked both task list options shown in the first frame, and then selected and deleted all the Task List Tokens. (from the second frame).

This basically cleared out my task list (it was the only way I could find to clear it, as selecting an item and right-clicking wouldn't enable the 'delete' context menu option..is that a bug??)

Anyway, with the task list gone, I can now type reasonably quickly. It's not as responsive as VB6's IDE, but then I suppose, for some reason, we shouldn't expect it to be.

Another questions is how on earth did I get over 3700 task items? Variables, and classes created in VB6 do not have default properties, so why is the upgrade wizard expecting to find them, and then reporting it couldn't find the default property? It also clutters my code with the same comment line over and over and over and over and over again... Half my time now seems to be deleting the comments the upgrade wizard has inserted into my code...

Anyway.. at least I can delete those comments without a 15 second wait between them...

Answer 57

Yes, the task list was my problem too.

I use shortcuts in code for quick navigation in a big solution. And task list (with "Shortcuts" filter) to navigate from one shortcut to another.  I noticed a few days ago that some shortcuts had duplicate entries in tasklist but i ignored that. Today my IDE became real SLOOOW.

When i looked in TaskList i had over 9000 entries.

Every new line and every autocomplete in the code editor(C#), lasted about 15-20 seconds. After navigating to each shortcut in task-list and removing the shortcut (Ctrl+K,H) several houndreds of entries in TaskList were removed. so i continued until i removed all shortcuts (about 15 in total) and respectively, all entries in TaskList were removed(over 9000).

Now the IDE is responsive.

Something is wrong with the Task List.

Answer 58

I found that the devenv.exe grows to over 800MB during debugging sessions (at that point I am in the mud). The problem was resolved by turning off the Dynamic Help window while in debug mode (Not sure why I had it on in the first place BUT problem solved for me).

Hope this helps.

 

Ted

Answer 59

FWIW, I've gone through this thread, applied all recommended changes, installed the hot fixes, upgraded to SP1 and so forth.  I'm working in a solution with several projects including C++ and C#.  The editor works fine until I build.  Then, it goes into delaying after every edit mode.  The only solution for me is to restart VS2005 after each build.

Steve

Answer 60

 I am getting the same very poor performance in VB.NET 2005 in Vista.  However, in VB.NET 2003 in XP there were no such problems.   The response from my call to MS installation group for VS 2005 is posted at vbcity.com here-->http://vbcity.com/forums/topic.asp?tid=145345.

I think it is a fair assessment that MS has to look into this issue quickly.   To simulate the problem all you would need to do is generate a simple "Hello World" is statement like

Dim j as Int64

j = 1
If j = 1 then msgbox("Hello World")
If j = 1 then msgbox("Hello World")
If j = 1 then msgbox("Hello World")
If j = 1 then msgbox("Hello World")
If j = 1 then msgbox("Hello World")
If j = 1 then msgbox("Hello World")
If j = 1 then msgbox("Hello World")
If j = 1 then msgbox("Hello World")

and copy and paste the if statement above about >20,000 times.  Next, when editing (do not run this) try to add 10 lines, delete 10 lines, and the editor will likely hang for >30 seconds.

My guess is that a first approach to fix this is to maybe make the editor run intellisense and Vista do its "hypersecurity" on only the subroutine that's being edited.   Vista is a large part of the problem, and the pattern that is emerging is that Vista's heightened security is tantamount to being like a keylogger that actually is paranoid about every keystroke. 

The big problem is that coders are losing productivity.

lep

Answer 61

Lep

 

22,000 lines isn't really all that big so I don't know what MS is talking about. My VB solution is two projects combined to well over 150,000 lines.

 

The problem I discovered was the task tracking.

 

When I upgraded my project from VB6 to VB.net (I eventually had to go back to VB6 because VB.net isn't anything like real visual basic), I discovered that the upgrade process added a whole slew of 'tokens' to the code that it tracked in the task manager.

 

Everytime I'd make one small edit, the IDE's task manager would go through all tasks (about 3,000 of them) looking for things it could update.

 

Eventually I discovered that I could turn off the tokens by going to;

Tools->Options->Click 'Show All Settings'->Click Task List and deleting all tokens.

 

Once all the tokens from the task list are gone, there is nothing left for the IDE to try and update with each edit.

 

VB.Net 2005 is still no where near as good as VB6, the language changes are awful, and the tools we were presented with are poorly made. But if you have no choice other than to use VS2005, I think turning off the task list tokens should speed up the IDE to at least make it useable.

Answer 62

bragac2 wrote:

JohnGalt wrote: Basically, as far as I can tell by this entire discussion and my own experiences is that the code editor is essentially unusable (or at least incredibly slow) for any form that has > 2000 lines of code in it. You can make that worse by putting on word-wrap, using the Navigation bar, having the form in design mode while you're editing your code behind etc. etc. etc. (All bugs other than the slowness of the editor with even moderately large code files) The end result of this is that MS needs to release a public patch right away for the code editor to fix all of these things. Everyone is running into it unless they're doing "Hello World" and it looks bad on MS. Please, please please MS, fix this stuff quickly and get us a patch before SP1... this can't wait. I agree, this is ridiculous.

i also agree

Answer 63

Sontu, you saw this tasklist bug in VS 2005?  I know we had earlier reports of that issue, but I thought it was fixed prior to the release of VS 2005.  If you're still seeing it, we'll have to take another look.  Do you have any idea what caused the tasks to be duplicated?  In other words, does the duplication happen when you restart the IDE, or when you open and close a project, or...?

 

Thanks!

-Josh

 

Answer 64

- Josh.

 

 As I posted earlier in the thread, there is a serious problem with the VS2005 task list. Or, maybe to be more clear, I found the problem both in the VS2005 editor, as well as the "stand alone" VB.net Express editor, and the "stand alone" VC++.net Express editor. (Although I assume they're the same editors)

 

 Having the task list tokens turned on pretty much killed performance. This was exceedingly noticeable when I attempted to migrate a 150,000 line VB6 project to VB.Net. There were so many useless comments added to my code that were also task list tokens, (over 6,000) that the whole thing came to a screetching hault. Once I removed the tokens from the token list on the task list option, then the IDE improved dramatically. That's not to say it's as good as VB6 (or VS95) but at least you can use it.

 

David

Answer 65

Hi David, thanks for the feedback.  The perf issue is something we're well aware of, and we've made some major improvements in this area since the release of VS 2005.  I'm going to make this a priority for the next release as well.

 

-Josh

 

Answer 66

 

vb.net 2005 editor is painfully slow even after sp1. so far I am very disappointed in vs 2005.

Answer 67

 

yes, I don't think vs 2005 is design for "hello world" app. it should be OK for large file too.

 

UPDATE:

 

just found this out.  It's resharper 3.0. it doesn't work well with vb.net. disable it in the add-in manager will do the trick.

 

 

Answer 68

Locking the thread as most recent additions to it have been about typing performance in the VB editor, not C#. Please post questions about editor performance in the forums for the specific language in question; you're far more likely to get useful assistance this way.

 

-Tom Meschter
Software Dev, C# IDE