VS 2010 Beta - What a horrible piece of software! [modified]
-
I just uninstalled it off a computer and it has successfully and completely screwed up VS 2008 installation on it. Firing up VS 2008 will give me some 12 errors with Yes or No option with the close button disabled. I'll have to click no 12 times. Restarted VS, restarted the machine. Same results. OK, I was willing to take it up on me. To my shock, I cannot view anything in project->settings because of some .NET component error (12 times for each click). EFF THIS RIGHT OFF! I was in the middle of an interesting debugging session, and now I'm in the middle of absolutely nowhere. I can't connect to the remote machine now (seems to be down), and I essentially can do nothing about it (11.14 PM here). I'll either have to take out VS 2008 DVD and try reinstalling it (with the hope that it would bring everything back to normal). But the thought process is gone, the flow of ideas is GONE! I cannot continue from where I was. How hard is it for them to get something as simple as an uninstallation procedure right?! Do they know of a thing called "testing"?! DO THEY?! I know it's a beta, but for the sake of love it shouldn't screwup something else on my computer. I think I'm executing plan B (go to sleep). There's nothing right about it. Not even the uninstallation. Zero marks. SCREW VS 2010. :thumbsdown: [Update] I cannot even switch between debug and release versions. This is it. Plan B executed. G'nite guys. [/Update]
“Follow your bliss.” – Joseph Campbell
modified on Monday, December 28, 2009 1:01 PM
-
Rajesh R Subramanian wrote:
Do they know of a thing called "testing"?
Of course they do, they get it free from kind people like you!
Richard MacCutchan wrote:
Of course they do, they get it free from kind people like you!
Not anymore if they don't ship at least beta quality software. Which is why I removed it, but even removing it is causing trouble! WTF!
“Follow your bliss.” – Joseph Campbell
-
I just uninstalled it off a computer and it has successfully and completely screwed up VS 2008 installation on it. Firing up VS 2008 will give me some 12 errors with Yes or No option with the close button disabled. I'll have to click no 12 times. Restarted VS, restarted the machine. Same results. OK, I was willing to take it up on me. To my shock, I cannot view anything in project->settings because of some .NET component error (12 times for each click). EFF THIS RIGHT OFF! I was in the middle of an interesting debugging session, and now I'm in the middle of absolutely nowhere. I can't connect to the remote machine now (seems to be down), and I essentially can do nothing about it (11.14 PM here). I'll either have to take out VS 2008 DVD and try reinstalling it (with the hope that it would bring everything back to normal). But the thought process is gone, the flow of ideas is GONE! I cannot continue from where I was. How hard is it for them to get something as simple as an uninstallation procedure right?! Do they know of a thing called "testing"?! DO THEY?! I know it's a beta, but for the sake of love it shouldn't screwup something else on my computer. I think I'm executing plan B (go to sleep). There's nothing right about it. Not even the uninstallation. Zero marks. SCREW VS 2010. :thumbsdown: [Update] I cannot even switch between debug and release versions. This is it. Plan B executed. G'nite guys. [/Update]
“Follow your bliss.” – Joseph Campbell
modified on Monday, December 28, 2009 1:01 PM
-
I just uninstalled it off a computer and it has successfully and completely screwed up VS 2008 installation on it. Firing up VS 2008 will give me some 12 errors with Yes or No option with the close button disabled. I'll have to click no 12 times. Restarted VS, restarted the machine. Same results. OK, I was willing to take it up on me. To my shock, I cannot view anything in project->settings because of some .NET component error (12 times for each click). EFF THIS RIGHT OFF! I was in the middle of an interesting debugging session, and now I'm in the middle of absolutely nowhere. I can't connect to the remote machine now (seems to be down), and I essentially can do nothing about it (11.14 PM here). I'll either have to take out VS 2008 DVD and try reinstalling it (with the hope that it would bring everything back to normal). But the thought process is gone, the flow of ideas is GONE! I cannot continue from where I was. How hard is it for them to get something as simple as an uninstallation procedure right?! Do they know of a thing called "testing"?! DO THEY?! I know it's a beta, but for the sake of love it shouldn't screwup something else on my computer. I think I'm executing plan B (go to sleep). There's nothing right about it. Not even the uninstallation. Zero marks. SCREW VS 2010. :thumbsdown: [Update] I cannot even switch between debug and release versions. This is it. Plan B executed. G'nite guys. [/Update]
“Follow your bliss.” – Joseph Campbell
modified on Monday, December 28, 2009 1:01 PM
You put beta software on a production system? And admitted it? Even worse, you did it with Visual Studio, which won't even uninstall the release version correctly. Correction: When I was testing it seemed that VS 2010 Beta uninstalled everything it might have installed. Turns out this is only partially true. It actually leaves .NET 4.0 behind, but uninstalls all of its runtime dependencies. The solution, it seems, is to uninstall .NET 4.0 after the VS 2010 Beta uninstall is done. On the other hand, I've long learned to never uninstall Visual Studio, beta or not.
modified on Monday, December 28, 2009 2:15 PM
-
You put beta software on a production system? And admitted it? Even worse, you did it with Visual Studio, which won't even uninstall the release version correctly. Correction: When I was testing it seemed that VS 2010 Beta uninstalled everything it might have installed. Turns out this is only partially true. It actually leaves .NET 4.0 behind, but uninstalls all of its runtime dependencies. The solution, it seems, is to uninstall .NET 4.0 after the VS 2010 Beta uninstall is done. On the other hand, I've long learned to never uninstall Visual Studio, beta or not.
modified on Monday, December 28, 2009 2:15 PM
Joe Woodbury wrote:
(Visual Studio 2010 beta uninstalls EVERYTHING it MIGHT have installed, whether it did or not. This includes .NET.)
Oh crap... I was gonna uninstall it this week from my Windows 7 box... You would *think* that it would only uninstall .Net 4.0...
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
Joe Woodbury wrote:
(Visual Studio 2010 beta uninstalls EVERYTHING it MIGHT have installed, whether it did or not. This includes .NET.)
Oh crap... I was gonna uninstall it this week from my Windows 7 box... You would *think* that it would only uninstall .Net 4.0...
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001Correction: When I was testing it seemed that VS 2010 Beta uninstalled everything it might have installed. Turns out this is only partially true. It actually leaves .NET 4.0 behind, but uninstalls all of its runtime dependencies. The solution, it seems, is to uninstall .NET 4.0 after the VS 2010 Beta uninstall is done. On the other hand, I've long learned to never uninstall Visual Studio, beta or not.
-
I just uninstalled it off a computer and it has successfully and completely screwed up VS 2008 installation on it. Firing up VS 2008 will give me some 12 errors with Yes or No option with the close button disabled. I'll have to click no 12 times. Restarted VS, restarted the machine. Same results. OK, I was willing to take it up on me. To my shock, I cannot view anything in project->settings because of some .NET component error (12 times for each click). EFF THIS RIGHT OFF! I was in the middle of an interesting debugging session, and now I'm in the middle of absolutely nowhere. I can't connect to the remote machine now (seems to be down), and I essentially can do nothing about it (11.14 PM here). I'll either have to take out VS 2008 DVD and try reinstalling it (with the hope that it would bring everything back to normal). But the thought process is gone, the flow of ideas is GONE! I cannot continue from where I was. How hard is it for them to get something as simple as an uninstallation procedure right?! Do they know of a thing called "testing"?! DO THEY?! I know it's a beta, but for the sake of love it shouldn't screwup something else on my computer. I think I'm executing plan B (go to sleep). There's nothing right about it. Not even the uninstallation. Zero marks. SCREW VS 2010. :thumbsdown: [Update] I cannot even switch between debug and release versions. This is it. Plan B executed. G'nite guys. [/Update]
“Follow your bliss.” – Joseph Campbell
modified on Monday, December 28, 2009 1:01 PM
Try uninstalling .NET 4.0.
-
Not even in my dream! The remote machine I'm talking about (read my post again) is my production machine. This one is a laptop on which I got the source copied to try fixing a few bugs at home, which actually was going smooth (and that's when I uninstalled VS 2010), which barfed on 2008. I wanted to try whatever I did here by connecting to the production machine, but it seemed down (which pissed me off even more). I can't sleep well and I'm hungry now. Going to the kitchen...
“Follow your bliss.” – Joseph Campbell
-
You put beta software on a production system? And admitted it? Even worse, you did it with Visual Studio, which won't even uninstall the release version correctly. Correction: When I was testing it seemed that VS 2010 Beta uninstalled everything it might have installed. Turns out this is only partially true. It actually leaves .NET 4.0 behind, but uninstalls all of its runtime dependencies. The solution, it seems, is to uninstall .NET 4.0 after the VS 2010 Beta uninstall is done. On the other hand, I've long learned to never uninstall Visual Studio, beta or not.
modified on Monday, December 28, 2009 2:15 PM
-
I just uninstalled it off a computer and it has successfully and completely screwed up VS 2008 installation on it. Firing up VS 2008 will give me some 12 errors with Yes or No option with the close button disabled. I'll have to click no 12 times. Restarted VS, restarted the machine. Same results. OK, I was willing to take it up on me. To my shock, I cannot view anything in project->settings because of some .NET component error (12 times for each click). EFF THIS RIGHT OFF! I was in the middle of an interesting debugging session, and now I'm in the middle of absolutely nowhere. I can't connect to the remote machine now (seems to be down), and I essentially can do nothing about it (11.14 PM here). I'll either have to take out VS 2008 DVD and try reinstalling it (with the hope that it would bring everything back to normal). But the thought process is gone, the flow of ideas is GONE! I cannot continue from where I was. How hard is it for them to get something as simple as an uninstallation procedure right?! Do they know of a thing called "testing"?! DO THEY?! I know it's a beta, but for the sake of love it shouldn't screwup something else on my computer. I think I'm executing plan B (go to sleep). There's nothing right about it. Not even the uninstallation. Zero marks. SCREW VS 2010. :thumbsdown: [Update] I cannot even switch between debug and release versions. This is it. Plan B executed. G'nite guys. [/Update]
“Follow your bliss.” – Joseph Campbell
modified on Monday, December 28, 2009 1:01 PM
Two words: Restore. System. Not necessarily in that order.
I wanna be a eunuchs developer! Pass me a bread knife!
-
I just uninstalled it off a computer and it has successfully and completely screwed up VS 2008 installation on it. Firing up VS 2008 will give me some 12 errors with Yes or No option with the close button disabled. I'll have to click no 12 times. Restarted VS, restarted the machine. Same results. OK, I was willing to take it up on me. To my shock, I cannot view anything in project->settings because of some .NET component error (12 times for each click). EFF THIS RIGHT OFF! I was in the middle of an interesting debugging session, and now I'm in the middle of absolutely nowhere. I can't connect to the remote machine now (seems to be down), and I essentially can do nothing about it (11.14 PM here). I'll either have to take out VS 2008 DVD and try reinstalling it (with the hope that it would bring everything back to normal). But the thought process is gone, the flow of ideas is GONE! I cannot continue from where I was. How hard is it for them to get something as simple as an uninstallation procedure right?! Do they know of a thing called "testing"?! DO THEY?! I know it's a beta, but for the sake of love it shouldn't screwup something else on my computer. I think I'm executing plan B (go to sleep). There's nothing right about it. Not even the uninstallation. Zero marks. SCREW VS 2010. :thumbsdown: [Update] I cannot even switch between debug and release versions. This is it. Plan B executed. G'nite guys. [/Update]
“Follow your bliss.” – Joseph Campbell
modified on Monday, December 28, 2009 1:01 PM
Been there. Done that. It messes up with some dll in System32 folder whose name I cannot recall right now. Your best bet would be to get rid of VS2008 as well and reinstall it.
50-50-90 rule: Anytime I have a 50-50 chance of getting something right, there's a 90% probability I'll get it wrong...!!
-
Two words: Restore. System. Not necessarily in that order.
I wanna be a eunuchs developer! Pass me a bread knife!
No need of anything now, the production machine was up after a support call and I connected to it, and I've completed whatever I had to.
“Follow your bliss.” – Joseph Campbell
-
I just uninstalled it off a computer and it has successfully and completely screwed up VS 2008 installation on it. Firing up VS 2008 will give me some 12 errors with Yes or No option with the close button disabled. I'll have to click no 12 times. Restarted VS, restarted the machine. Same results. OK, I was willing to take it up on me. To my shock, I cannot view anything in project->settings because of some .NET component error (12 times for each click). EFF THIS RIGHT OFF! I was in the middle of an interesting debugging session, and now I'm in the middle of absolutely nowhere. I can't connect to the remote machine now (seems to be down), and I essentially can do nothing about it (11.14 PM here). I'll either have to take out VS 2008 DVD and try reinstalling it (with the hope that it would bring everything back to normal). But the thought process is gone, the flow of ideas is GONE! I cannot continue from where I was. How hard is it for them to get something as simple as an uninstallation procedure right?! Do they know of a thing called "testing"?! DO THEY?! I know it's a beta, but for the sake of love it shouldn't screwup something else on my computer. I think I'm executing plan B (go to sleep). There's nothing right about it. Not even the uninstallation. Zero marks. SCREW VS 2010. :thumbsdown: [Update] I cannot even switch between debug and release versions. This is it. Plan B executed. G'nite guys. [/Update]
“Follow your bliss.” – Joseph Campbell
modified on Monday, December 28, 2009 1:01 PM
-
When it comes to uninstalling visual studio...It's more along the lines of re-install windows.
Those who are too smart to engage in politics are punished by being governed by those who are dumber. - Aristotle
Very correctly said. :)
“Follow your bliss.” – Joseph Campbell
