visual studio 2005 is running slowly

visual studio 2005 is running slowly

• Atul Palkhe

  Another easy way to check for bugus controls is to use the combo dropwdown in the properties grid. First check that the number of items in the combo matches the number of controls on your form or is at least in the right ball park.

  Then if you think you have extra controls try selecting some from the combo box. That should cause the relevant control to be selected on the designer. If it's not getting selected it's probably a bogus control in a non visible part of the form or a non visible portion of a container control.

  Another thought is to do a Find on the name of the control (check the option to search hidden code). If the results you get for the control exist only in the designer.vb file and there are no event handlers for the control then it's probably a bogus control since you have no user code associated with it. (This may not be true for labels and other static controls however).

  If you need any more help in tracking this down please contact vbperf@microsoft.com and we'll be happy to help.

  Cameron McColl

  
  

• Brian Kramer

  That doesnt sound very right..

  As i recall, there were almost no delay when changing a name of a control in vb 6.

  Of course im no expert developer, but the studio must be doing something in those 10 seconds, and there shouldn't be that much writning fore one name..

  But here is something interesting i discovered right now:

  When placing a control on the form it takes one second. In that second it sets the name of that control easy Now if i right away changes the name of this control it takes less than a second. And i can change it severall times and it is very fast. Now here is the strange stuff: When the studio then saves my program for autorecovery, or i myself choose save all in the file menu, it actually takes 5 seconds to change the controls name after this. If a place a new control on the form, i can change the name of this control in a second, right until i save the file again. All the "old" controls are slow at chagning names.

  Could you try this on you project im curious to see if this is just something on my machine.. (o=

  PS: pardon my english spelling, im danish

  
  

• ZopoStyle

  In addition to installing the performance fix, check your forms to see that you don't have unnecessary controls in there. We have seen instances where the forms start accumulating unused controls and that slowing down designer operations.

  To check for unused controls, open the form.designer.vb file and make sure that the only variables declared are the ones that you are using in your controls.

  Hope this helps,

  
  
  

• DavideB

  I tried the hotfix. no luck. still having the same problem

  1)changing the name of the controls takes >10-20seconds

  2)same symptoms when i save the changes in my project

  3)auto hide feature of property window is slower(after i edit some thing in the poperty window and click on the form it takes 10 seconds to hide the property window some times

  4) when i change the tabpages order, the background color of all the tabpages change from control to transperant

  
  

• MRDPrince

  did the hotfix work And how well
  

• Sugan

  Thats doesnt sound right.
  

  See Posting
  http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=382602&SiteID=1
  
  
  

  
  MS have have released 2 fixes that address different problems:

  KB 915038 - EnC Fix
  KB 917452 - Performance Fix, which includes the fix to the memory leak problem with XML Doc comments.

  
  From looking at the description in some of your posts, it looks like you need to get the fix for KB 917452.

  To get the HotFix, please contact Microsoft Support (http://support.microsoft.com/contactus/ ws=support), ask to contact the Visual Basic 2005 Support Team, and request the hotfix described in KB Article 917452.

  
  

  
  

• Jenny777

  thanks for the info. not all the forms have 15 tabpages. 5-6 forms have 8-15 tabpages. The developer left the company. I am the new deveoper and converting vba forms to windows forms manually. The current vba has so many bugs (no technical doc)we tried third party tools like access vb.net converter, and convertovb(vba-->vb6-->vb.net). the results was bad. I was able to open most of the form in vs 2003. but in 2005 i get red XXX's with 50--100 errors per form. so I started to create forms manually. I am using .net controls not vb6 controls.

  Note:i will be redesigning the forms(reduce the number controls) .waiting for the user feed back.

  
  

• Stephanie Chen

  thanks for the info. I am in the process of converting vba forms to windows forms. I used two third part tools. no sucsess. I was unable to open most of the forms(total forms=277). then started to do manualy by creating a new project.some of these forms have 5--10 tabcontrols and within tabcontrol another 3-5 tabcontrols. each main tabcontrol has at least 25--75 controls like labels,radiobuttons,textbox,listbox,combobox. some of the forms look a like. so i simply copied and pasted the controls and renamed them and deleted unnecessary ones. counting the controls or checking the positions of the controls manuly is time consuming. let me give it a try(vba forms are designed by some body else

  i have 5 forms like this:

  Tabcontrols-15

  Labels->100

  Buttons->100

  Combobox-25

  subTabcontrols-10

  radiobutton>40

  1)what is the maximum number of controls that a form can have

  
  

• jrboddie

  That's a huge number of controls.

  It does'nt suprise me that it takes so long when renaming controls - VS goes through everything and updates references (which is real handy). With that many controls there's a lot of code to go through. Additionally, all those old 'vb6' labels are much more heavyweight controls.

  To be honest, trying not to be too critical, but the whole application sounds like a users nightmare (15 tabs on one form out of 277!! ouch!) Since you are upgrading it (the question would by why Presumably it is working - if it isn't, then it should be redesigned anyway) perhaps you need to extract the forms into satellite assemblies, grouped by user function.

  I think you are going to continue to wrestle with the problem, unless you break it down into smaller projects.

  
  
  

• CruzPedro

  you are right dan.this is what i did

  1)my form already has 950 controls. so i added a new textbox and changed the name a few times. it was fast. then the auto recovery feature ran. then i started to get the same problem.

  2)i put a new textbox and chnaged the name 3 times before the auto recovery ran. then i changed the name of an existing control.it took about 12 seconds.then came back to textbox to change the name.i got the same problem.

  Note: as per ms advice: I change value of refractory from true to false(tool-->windows form designer-->general-->refactory-->false). no luck

  
  

• SnowJim

  i spoke to ms and got a hotfix. let me install it and see.

  thanks for the info

  
  

• MarcoSartore

  yesterday i spent 2 hours with ms vs2005 support. acccording him the dealy of 10-15 seconds is normal as i am having so many controls on my form.

  I have one tabcontols with 15 pages. each page has :

  15 ,110,12,97,40,107,90,5,14,56,2,3,84,266,56 controls(combination of labels,textboxes,comboboxes,radio buttons,datagridview,check boxes,listboxes)

  also he mentioned that i ahve so many programs installed on my machine such as sql server 2000,citrix,vs2003 which i don't agree. may b e i have to redesign the form. any advice would be appreciated

  
  

• rajesh_batchu

  i was informed by a ms staff today that this is a known issue and no hotfixes right now, may not be in near future. I can use a text editor to rename the controls The person called me like to close the case
  

• RARiedel

  Hehe, that was Weird...

  Kind of strange that they contacted you when they already tried to say that its a normal thing this delay. If they knew this program that they have made (visual studio2005) then they should be able to find out what is going on in these 15 seconds delay..

  I myself think that this is a pretty important issue and it should be fixed rather fast. In these delays you could easy write a few lines of code, and its anoying to sit and wait..

  But how are you able to change the names in a texteditor, and why should you

  The only thing to do then is probably to make sure that you name the control right away when its created. But i am courious to know what exactly the studio is doing in these delays after the autosave have done its thing.

  But we can only wait and see if they come up with a hotfix..

  
  
  
• visual studio 2005 is running slowly