VS 8 Performance makes it unuseable

VS 8 Performance makes it unuseable

• CheeseBob

  Stephan -
  What IDE features are you seeing that are particularly slow   The project opening   IntelliSense   Colorization
  
  Would you be willing to send us your code so we could repro the issue on our side
  
  Please log a bug at the Product Feedback Center as well. http://lab.msdn.microsoft.com/productfeedback/
  
  Thanks!
  Karen Liu
  Visual C#

  
  
  

• Joe Duffy

  I converted a large VB.NET project from VS7 to VS8. After converting the project, the development environment runs so slow, that I cannot even get any work done.

  On a form if I try to change a control name it can take up to 2 minutes for the change to take place. I have tried everything. I have increased my memory to 2gb and I'm running on an AMD 64 Bit processor.

  The perfomance issue is much more than just annoying it makes the environment impossible to work with. If I could, I would convert the project back to VS7 but I dread this thought.

  I read somewhere that I might be best off creating a new project and adding in all the forms and classes to the new project, but I don't want to invest the time in doing this if it is not going to help.

  Microsoft has got to do something about this problem.

  
  

• advent.children

  Hi,
  
  Yes, the IDE definitely is quite slow. But I've used the VS2002 on its beta days and the GUI was really slow. But upon release the GUI just got a little faster. I think this is also the case in VS2005. Lets just wait on the RTM and see if it becomes faster.
  
  
  
  
  cheers,
  
  Paul June A. Domag
  
  
  

• cRz

  I put this very simple, VS2005 is the worst IDE i have ever used, even JBuilder was better. Performance is one thing (i have no option but to leave most GUI library in VS2003) but sudden crashes during design makes effective work imposible. For example: have deep inheritance hierarchy for user controls, renaming control type or name on base form, not only disrupt child user controls but in most cases crash IDE itself . Another very 'RAD' feauture : any change in base library referenced by toolbox equals inability to design any form which contains any controls declared in that library. Solution reopen VS2005, how long does it take with solution with 20 projects you can only imagine :]. In VS2003 this scenerio worked flawless. I also encounter random crashes during attaching proces to debug (which ofcourse never was a case in VS2003). In terms of real work usability VS2005 is as effective as Vs2002 beta1 was. Really, Vs2002 was huge step forward, and vs2003 was briliant, i have never encountered any crash, and now we have Team System, 7 miliones of code and another marketing *** but no usable IDE. Great work M$, is there any chance to release any service pack, or we should wait for vs 2007 which be only suitable to build hello world type application I know it is very harsh, but .Net 2.0 is great advencment over 1.1, but horryfing slow, crashable IDE is real obstacle in effective development.

  And onother 'great' feature of IDE concerning toolbox : sometimes randomly when i put my control from toolbox , i have exception : cannot add reference ...., reference already exist in project (reference is user control library from toolbox).

  
  

• Richard G.H.Lin

  Hi Paul,
  
  Thanks for the suggestion but we had already tried this. One of the most annoying features was that the toolbox insisted on trawling through all the application Dll's and adding any controls it found to itself. As there were so many, the UI just appeared to hang (10 minutes), the only indication of life was a flickering scroll bar in the toolbox. Luckily this feature can be disabled via setting Tools-Options-Windows Forms Designer-AutoToolBoxPopulate to False.
  
  Another particularily annoying feature is that when you run code in debug mode it runs really slowly, ie. you can see textboxes render themselves on forms. Run the code in release or run without debugging and all is fine. This is most odd because if you run without debugging and then attach the debugger using "Attach Process..." it runs ok.
  
  Its starting to bring a whole new meaning to the word RAD :)
  
  Steve Crabb
  

• Rob MacFadyen

  You are not alone, we just finished porting a project from VS.NET 2003 to VS.NET 2005, the project is large, and performance went down immediately (debug time), some files just cannot open in the editor, and they are very small :-)

  
  

• MarieG

  I cannot believe that microsoft cannot reproduce this with all of their resources! I mean my gosh man. I am experiencing this and it seems as if everyone with more than the simplest project is. It is so bad that it is making the product unusable. Why dont you fly someone out and get it fixed. It's truly incredible.

  gary.goodwin@gmail.com

  
  

• JR-MDX

  GeorgeT, Stephan -
  Would either of you mind sharing your project so that we can repro this on our side   (I realize that this may be quite large and may not be possible though).
  
  Please email me at karenliu@microsoft.com.
  
  Thanks!
  Karen Liu
  Visual C#
  
  

• hasdkljakldjs

  Hi Paul,
  
  As far as I know this is the release version we are using !!. It would make me at least a little hopeful if someone were to tell me it isnt.
  
  Microsoft Visual Studio 2005
  Version 8.0.50727.42  (RTM.050727-4200)
  Microsoft .NET Framework
  Version 2.0.50727
  
  regards

  Steve Crabb

  
  

• ChapiNaples

  Hi,

  Thanks for raising this issue with performance in the VS IDE. We are currently working on a hotfix to address many of the perf degradations in the VB IDE, and we hope to release it soon.

  To help us evaluate whether our fix will address the issues you're experiencing, can you please answer the questions below You can email me directly at pdarragh*at*microsoft.com.

  1. I've listed the specific IDE scenarios that you have mentioned have bad perf. Are there any others that are also impacting your productivity
  
  -Renaming controls on the forms designer
  -Opening files in the editer (Q: Are these code files or forms )
  -Running when hosted by the debugger
  -Toolbox auto-detection of usercontrols
  
  2. What is your machine configuration (CPU, RAM, disk space, OS version)
  3. How many projects are in your solution What type of projects are they (eg, VB only Control Libraries )
  4. Are you using project to project references
  5. Are you using 3rd party controls
  6. Is the project in compiling state If not many errors,warnings are in the task list
  7. Are you using the My feature in VB
  8. Do you use the Edit and Continue feature
  9. Do you run other programs at the same time as VS If so, what are they typically

  Thanks,
  -Patrick Darragh
  VB PM

  
  

• PETRU ROTARIU

  Hi,
  
  Ok, I just checked the site. And I think you downloaded it on the MSDN subscriber site. The launching of the product is due to November 7 in San Francisco. And sad to say, but yes that's the final release. I suggest you file a complaint in the Product Feedback.
  
  
  
  
  cheers,
  
  Paul June A. Domag
  
  
  

• FHJJr

  Hi Gary.

  I'm not sure we have to fly someone out yet. :0) But we are absolutely committed to helping you solve your performance problems, especially if you feel that they make the product unusable. I'll email you and connect you with someone who can really dig through this problem.

  If anyone else is running into performance problems or other bugs, feel free to email me through my blog (http://blogs.msdn.com/scottno). I'll work with you to get the issue resolved.

  Thanks,
  Scott Nonnenberg
  Visual C# Team

  
  
  

• Martin McNally

  I complained about VS.NET 2005 on day 2 after its release, when impressed by the Microsoft presentations we started migrating our C# code, and after a week, I just learned how not to use any of the new features :)

  I wanted immediately to use all the new features, like the refactoring, edit and continue, and all the new improvements to the C# language.

  Unfortunately, the edit and continue is not supported on the ASPX web sites (with wonderful misleading error messages, we call them MS Scams.NET, they just give you false hope), there is something else called edit and refresh (without the debugging support), I guess someone just invented this as a feature :-) but anyway, not that useful when debugging,

  Team server is not ready, the refactoring is supported on ASPX but super slow, 30 minutes and up, and the aps.net compiler, slow as hell.

  A very large .net project, compiled immediately, a small web site attached, verified in ……..

  Here is an idea, all what I want from 2.0 is the generics, implement them in VS.NET 2003 Service Pack 1 as .net 1.11, and I will be just fine :-), I will simply uninstall VS.NET 2005 with no problems.

  Having such a poor product stopped us from implementing SQL Server 2005 in our project, for a project that just loads and saved data, 2000 is doing just fine, although 2005 is faster, I think a second processor will give you the same performance, and it is safer, after all what I’ve seen in 2.0 this year, and BizTalk 2004 2 years ago, who knows how much problems are in SQL 2005

  Good luck with fixing.

  
  

• Jaylach

  Hi,
  
  Yes, this has been an issue with the VS2005 Beta 2. Its been said that this has been fixed in the Final Release (or maybe as early as RC ). There's a workaround on this:
  

  Delete:
  windows.prf and windowsidx.prf

  found in the following folder:
  C:\Documents and Settings\[username]\Application Data\Microsoft\VisualStudio\8.0

  Here's the bug report submitted to microsoft: http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx feedbackid=f10bec3b-a66c-49f3-af2d-05b07af8772c
  
  
  cheers,
  
  Paul June A. Domag
  
  
  
• VS 8 Performance makes it unuseable