Why I hate Visual Studio today
-
So I'm anticipating being done with my work for the evening. I have just a few more things to change on my UI in Visual Studio. The new item requires a new reference. The easiest way to get the correct reference for this particular Telerik component is to drag it from the toolbox onto the design surface. Guess what happens? The stupid modal dialog in Visual Studio happens. It says, "Removing toolbox content from unregistered assemblies." And at this point it's adding ones that are missing. All in likelihood from upgrading the Telerik components a couple of days ago. Why in a day in age that Microsoft is pushing asynchronous does something like this stop your work and lock up VS? I would gladly have did it the long way if this had to finish in the background. But, I cannot do anything. It's been chugging away for more than 10 minutes and still going. Hey Microsoft, is this the way to teach by example, or are you telling us to do what you say and not what you do? tl;dr VS displays modal dialog at the worst times, it cannot be canceled, and you're stuck waiting.
-
So I'm anticipating being done with my work for the evening. I have just a few more things to change on my UI in Visual Studio. The new item requires a new reference. The easiest way to get the correct reference for this particular Telerik component is to drag it from the toolbox onto the design surface. Guess what happens? The stupid modal dialog in Visual Studio happens. It says, "Removing toolbox content from unregistered assemblies." And at this point it's adding ones that are missing. All in likelihood from upgrading the Telerik components a couple of days ago. Why in a day in age that Microsoft is pushing asynchronous does something like this stop your work and lock up VS? I would gladly have did it the long way if this had to finish in the background. But, I cannot do anything. It's been chugging away for more than 10 minutes and still going. Hey Microsoft, is this the way to teach by example, or are you telling us to do what you say and not what you do? tl;dr VS displays modal dialog at the worst times, it cannot be canceled, and you're stuck waiting.
Visual Studio usually does that on startup (for me at least). What VS version do you have? I remember seeing this happen in VS2008/2010. VS2012/2013 don't seem to do it as often.
<voice type="Ebeneezer Scrooge"> Bah. dumb bugs </voice>
-
Visual Studio usually does that on startup (for me at least). What VS version do you have? I remember seeing this happen in VS2008/2010. VS2012/2013 don't seem to do it as often.
<voice type="Ebeneezer Scrooge"> Bah. dumb bugs </voice>
-
So I'm anticipating being done with my work for the evening. I have just a few more things to change on my UI in Visual Studio. The new item requires a new reference. The easiest way to get the correct reference for this particular Telerik component is to drag it from the toolbox onto the design surface. Guess what happens? The stupid modal dialog in Visual Studio happens. It says, "Removing toolbox content from unregistered assemblies." And at this point it's adding ones that are missing. All in likelihood from upgrading the Telerik components a couple of days ago. Why in a day in age that Microsoft is pushing asynchronous does something like this stop your work and lock up VS? I would gladly have did it the long way if this had to finish in the background. But, I cannot do anything. It's been chugging away for more than 10 minutes and still going. Hey Microsoft, is this the way to teach by example, or are you telling us to do what you say and not what you do? tl;dr VS displays modal dialog at the worst times, it cannot be canceled, and you're stuck waiting.
tgrt wrote:
The easiest way
... is probably by editing the project file in Notepad.
This space intentionally left blank.
-
Odd. I almost never see that 'Removing toolbox content...' dialog. I think that DevExpress control setups run devenv /setup to rebuild the toolbox content before the IDE is run. Not sure about Telerik controls, though. I do see the 'Waiting for a required operation to complete.' dialog sometimes, usually when I try to do something before VS is fully loaded.
<voice type="Ebeneezer Scrooge"> Bah. dumb bugs </voice>
-
Odd. I almost never see that 'Removing toolbox content...' dialog. I think that DevExpress control setups run devenv /setup to rebuild the toolbox content before the IDE is run. Not sure about Telerik controls, though. I do see the 'Waiting for a required operation to complete.' dialog sometimes, usually when I try to do something before VS is fully loaded.
<voice type="Ebeneezer Scrooge"> Bah. dumb bugs </voice>
-
So I'm anticipating being done with my work for the evening. I have just a few more things to change on my UI in Visual Studio. The new item requires a new reference. The easiest way to get the correct reference for this particular Telerik component is to drag it from the toolbox onto the design surface. Guess what happens? The stupid modal dialog in Visual Studio happens. It says, "Removing toolbox content from unregistered assemblies." And at this point it's adding ones that are missing. All in likelihood from upgrading the Telerik components a couple of days ago. Why in a day in age that Microsoft is pushing asynchronous does something like this stop your work and lock up VS? I would gladly have did it the long way if this had to finish in the background. But, I cannot do anything. It's been chugging away for more than 10 minutes and still going. Hey Microsoft, is this the way to teach by example, or are you telling us to do what you say and not what you do? tl;dr VS displays modal dialog at the worst times, it cannot be canceled, and you're stuck waiting.
Because legacy code.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
So I'm anticipating being done with my work for the evening. I have just a few more things to change on my UI in Visual Studio. The new item requires a new reference. The easiest way to get the correct reference for this particular Telerik component is to drag it from the toolbox onto the design surface. Guess what happens? The stupid modal dialog in Visual Studio happens. It says, "Removing toolbox content from unregistered assemblies." And at this point it's adding ones that are missing. All in likelihood from upgrading the Telerik components a couple of days ago. Why in a day in age that Microsoft is pushing asynchronous does something like this stop your work and lock up VS? I would gladly have did it the long way if this had to finish in the background. But, I cannot do anything. It's been chugging away for more than 10 minutes and still going. Hey Microsoft, is this the way to teach by example, or are you telling us to do what you say and not what you do? tl;dr VS displays modal dialog at the worst times, it cannot be canceled, and you're stuck waiting.
The best is a modal dialog stating "performing background task". WTF???!!! If it's a background task, then why the hell do I care?
If your actions inspire others to dream more, learn more, do more and become more, you are a leader.-John Q. Adams
You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering.-Wernher von Braun
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-Albert Einstein -
So I'm anticipating being done with my work for the evening. I have just a few more things to change on my UI in Visual Studio. The new item requires a new reference. The easiest way to get the correct reference for this particular Telerik component is to drag it from the toolbox onto the design surface. Guess what happens? The stupid modal dialog in Visual Studio happens. It says, "Removing toolbox content from unregistered assemblies." And at this point it's adding ones that are missing. All in likelihood from upgrading the Telerik components a couple of days ago. Why in a day in age that Microsoft is pushing asynchronous does something like this stop your work and lock up VS? I would gladly have did it the long way if this had to finish in the background. But, I cannot do anything. It's been chugging away for more than 10 minutes and still going. Hey Microsoft, is this the way to teach by example, or are you telling us to do what you say and not what you do? tl;dr VS displays modal dialog at the worst times, it cannot be canceled, and you're stuck waiting.
I hate that it decides, on my behalf, to remove unregistered controls. We have a library of controls that the IT group uses that we do not register. They are placed into a central remote directory for inclusion to Visual Studio. Does anyone know how to disable this 'feature' of removing unregistered components from the toolbox. there should be a menu option to run this removal of unregistered controls. do not do it for me. We have over 100+ unregistered controls in the centralized repository.