Help fix performance problems in VS
-
Yeah, but Joe just mentioned that some bugs *did* get fixed because he reported them to MS. Why didn't we hear about those? Instead, all we heard was more whining about the ones that didn't get fixed. You're complaining that they didn't fix a syntax color bug. You're complaining they don't have MDI windows. You're implying they lied about taking a survey on the MDI thing. So what? They took away MDI? Boo freaking hoo. Get over it. You're not a 5 year old. Software is imperfect. Move on. If it really matters that much to you, keep talking to Microsoft, stop bitching to CP about how terrible your life is because of it. When every CP thread is met with cynicism, it's gone too far. Oh, if VS has an MDI, I'm going to start bitching.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoJudah Himango wrote:
Yeah, but Joe just mentioned that some bugs *did* get fixed because he reported them to MS
Read what I wrote. The bugs got fixed because I publicly complained about them; they ignored them when I simply reported them (and even closed most of them.) There is a HUGE difference. You are ignoring the simple fact that we talked to Microsoft over and over and until the were publicly embarassed, they did NOTHING.
Judah Himango wrote:
Software is imperfect.Move on.
This is such a bullshit attitude. We aren't talking about free or $50 software here, but $800+ software. I know you're just being a damn hypocrite because I'm sure you take back the $30 toaster that doesn't work right. I'm sure if you have a car with the same repair problem, you'd complain to both the company and governmental agencies. But somehow, you're all magnaniumous about software. Sure. (A dozen years ago there was a doozy of a bug in Adobe Premiere. I reported it and was told there was no bug. Others reported it and were told the same. We all started complaining publicly. Lo and behold, a patch [that wasn't in the works] suddenly came out and that bug was fixed [though weirdly, Adobe kept denying its existance.] I could got on and on about products that didn't get fixed until there was a public outcry.)
-
John Simmons / outlaw programmer wrote:
I don't want new features
Yeah you do. You just complained 2010 doesn't have MDI. But I'm not talking about features. I'm talking about improvement. Examples: fewer memory leaks in 2010. The Add Reference dialog doesn't freeze the UI thread for 10 seconds. :-p
John Simmons / outlaw programmer wrote:
Actually, I think the exact statement will be "It's about f*ckin' time they got it right...", and I'm sure a number of others will agree with the sentiment.
I may be mistaken about this, John, but I think the plugin system works like that already. I didn't have to reinstall my plugins when VS 2010 SP1 was released last month. Guess I'll be waiting for a CP lounge thread saying, "It's about f*ckin' time they got it right..." ;)
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Judah Himango wrote:
Yeah, but Joe just mentioned that some bugs *did* get fixed because he reported them to MS
Read what I wrote. The bugs got fixed because I publicly complained about them; they ignored them when I simply reported them (and even closed most of them.) There is a HUGE difference. You are ignoring the simple fact that we talked to Microsoft over and over and until the were publicly embarassed, they did NOTHING.
Judah Himango wrote:
Software is imperfect.Move on.
This is such a bullshit attitude. We aren't talking about free or $50 software here, but $800+ software. I know you're just being a damn hypocrite because I'm sure you take back the $30 toaster that doesn't work right. I'm sure if you have a car with the same repair problem, you'd complain to both the company and governmental agencies. But somehow, you're all magnaniumous about software. Sure. (A dozen years ago there was a doozy of a bug in Adobe Premiere. I reported it and was told there was no bug. Others reported it and were told the same. We all started complaining publicly. Lo and behold, a patch [that wasn't in the works] suddenly came out and that bug was fixed [though weirdly, Adobe kept denying its existance.] I could got on and on about products that didn't get fixed until there was a public outcry.)
Reporting bugs to Microsoft is good. Bitching about problems without end, and not being willing to do anything to improve the situation, is the ugly thing. You sound like you've tried to do things about it in the past, with mixed results (some fixed, many not fixed). Ok, fine. I posted this thread about a tool that can improve the situation. It was met with cynical, sarcastic responses. How is that improving the situation? It's not. If people really are serious about improving things, this thread would have gone differently. All this community does is bitch about things. I *never* see stuff like, "oh, sweet, they fixed this", or "Oh, nice, they actually fixed one of my bugs." Seeing some of that would make all the bitching tolerable. But when it's 99% negative, I don't buy the BS that it's all MS's fault. I think people here really are negative, whiny old cynics who don't appreciate a damn thing; the only thing they know how to do is complain. I'm so sick of the negative, cynical personalities here on CP. It didn't used to be this way.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Joe Woodbury wrote:
Microsoft claimed VS 2010 would be the next 6
Kinda remiscient of when they said they "re-wrote" SourceSafe so that it "didn't suck". And now we have that bloated over-priced mess called Team Foundation Suite.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"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, 1997Hey, I'm no TFS fan (guess I'm still fond of good ol' SVN), but TFS was an improvement over VSS. Come on now, who remembers how bad that thing actually was? It made CVS look good.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Judah Himango wrote:
John Simmons / outlaw programmer wrote:
I don't want new features
Yeah you do. You just complained 2010 doesn't have MDI.
That's not a new feature; that's removing a regression.
3x12=36 2x12=24 1x12=12 0x12=18
;P
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
This plugin will help solve things then. Give it a shot, let us know how it works for you.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoNope, only works in Vista/7... Running XP at the office, unfortunately.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels) -
Nope, only works in Vista/7... Running XP at the office, unfortunately.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)Luddite...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"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 -
Luddite...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"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, 1997Hey, not by choice! Got Win7 x64 at home, and I love it... Much better than XP.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels) -
John Simmons / outlaw programmer wrote:
I don't want new features
Yeah you do. You just complained 2010 doesn't have MDI. But I'm not talking about features. I'm talking about improvement. Examples: fewer memory leaks in 2010. The Add Reference dialog doesn't freeze the UI thread for 10 seconds. :-p
John Simmons / outlaw programmer wrote:
Actually, I think the exact statement will be "It's about f*ckin' time they got it right...", and I'm sure a number of others will agree with the sentiment.
I may be mistaken about this, John, but I think the plugin system works like that already. I didn't have to reinstall my plugins when VS 2010 SP1 was released last month. Guess I'll be waiting for a CP lounge thread saying, "It's about f*ckin' time they got it right..." ;)
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoJudah Himango wrote:
. I didn't have to reinstall my plugins when VS 2010 SP1 was released last month.
I still can't get Iron Ruby to work :((. It's funny to see one joke reply transcend into this monster. But you are right on many points, CP has become a place of whining about technology.
-
This sounds like an interesting VS plugin: VS PerfWatson[^]. The plugin detects when Visual Studio hangs. When it hangs, it sends the hung stack trace to MS. MS spends less time investigating VS performance problems and more time fixing them[^]. :cool:
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoOops - 1-voted instead of clicking for page 1 - off to Q&A to find out how to retract. [EDIT] Couldn't work out how to retract, so 5 voted it as well. Apologies, Stewart
modified on Tuesday, May 10, 2011 4:16 AM
-
Oops - 1-voted instead of clicking for page 1 - off to Q&A to find out how to retract. [EDIT] Couldn't work out how to retract, so 5 voted it as well. Apologies, Stewart
modified on Tuesday, May 10, 2011 4:16 AM
-
From the link: If VS goes unresponsive for more than 2 seconds, Perf Watson grabs a stack frame. That's the problem. When I use it, VS 2010 rarely goes unresponsive for 2 seconds, it just feels sluggish. Usability tests have proven over and over that if something takes more than 100 ms, users notice it's not instantaneous. By 300 ms, it becomes obvious. By 1 second it becomes measurably disruptive. Microsoft has an excellent usability department, so why do so many divisions and teams at Microsoft ignore them? (Rhetorical question--solving customer problems takes a back seat to using the latest "in" technology.)
RE: sluggish - If you watch any of the MS instructional videos, say for Silverlight, you'll see very snappy VS2010 performance. Oh, and I'll bet all those videos are being recorded on virtual PCs, which I have found to be slightly slower than the non-virtual kind. I'm running a 3 year old WinXP system at work and I'd chalk up the sluggishness to the PC's age and OS, if it weren't for the fact that I've got a 'decent' Win7 64 desktop at home (only 4GB though) which is still no where near as snappy as what I see in the videos. Maybe their usability department is all using boxes with beastly CPUs and lots of memory and, therefore, don't see nearly as much sluggishness.
-
This sounds like an interesting VS plugin: VS PerfWatson[^]. The plugin detects when Visual Studio hangs. When it hangs, it sends the hung stack trace to MS. MS spends less time investigating VS performance problems and more time fixing them[^]. :cool:
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoMy VS2010 Pro has just decide to crash with: An error occurred creating the form. See Exception.InnerException for details. The error is: Object reference not set to an instance of an object. for ANY project, even if it only has a form with 1 text box in it and simple code such as: Public Class Form1 Dim AIFName As String = TextBox1.Text & ".AIF" End Class I uninstalled the whole VS2010 & installed it again - exactly the same problem. What a PITA this is - screwing up my schedule. Tried to install VS2010 on an older machine but it is so slow it is unusable.
-
My VS2010 Pro has just decide to crash with: An error occurred creating the form. See Exception.InnerException for details. The error is: Object reference not set to an instance of an object. for ANY project, even if it only has a form with 1 text box in it and simple code such as: Public Class Form1 Dim AIFName As String = TextBox1.Text & ".AIF" End Class I uninstalled the whole VS2010 & installed it again - exactly the same problem. What a PITA this is - screwing up my schedule. Tried to install VS2010 on an older machine but it is so slow it is unusable.
I've found the cause of your problem: you're using Visual Basic.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
I've found the cause of your problem: you're using Visual Basic.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Maybe, because when I try the same thing in C# using VS2010, I don't get any error! :-) But I don't plan to convert all my apps because of a MS error, so I guess I will have to find the cause of the problem.
You using Visual Studio 2010 Service Pack 1?
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
You using Visual Studio 2010 Service Pack 1?
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Joe Woodbury wrote:
That's the problem. When I use it, VS 2010 rarely goes unresponsive for 2 seconds
Really? Mine freezes all the time... I could be in the middle of typing, and it'll just suddenly lock up for a good minute or two. It's gotten to the point that when it happens, I just browse a few websites and check back now and then to see if it's woken up yet.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)I had the same thing happening - infuriating and highly stressful when you are trying to get something done. The solution I was working on had 3 projects that all were vs2008, so had been upgraded to vs2010. Long story short, I think (I know I did, but think these were the causes of improvements) I saw improvements by creating a new vs2010 solution and then adding in the projects to it. Also, I read that you shouldn't store any of the projects on a network drive as the i/o is heavy with vs2010 and I think that helped some. Do a search (it dawned on me to that day) on vs2010 slowness to find pointers but yeah, we shouldn't have to live like this. I did install the plugin as it seemed like an efficient way for us and MS to work on some of these problems!!!
-
It's a colloquialism. If I'm going to go through the trouble/hassle of installing a plug-in, they're gonna have to take it to heart and start telling me something besides, "it's not worth fixing". In case you haven't picked up on it yet, that really pissed me off.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"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, 1997To be fair, not all problems are Microsofts fault. Take for example: vs2010-rtm-crashes-when-unlocking-xp[^] - from the memory dump wesaw the video driver was the culprit, not a Microsoft problem. I too have had my fair share of Connect issues rejected, marked as designed, or wont fix. Half the time I think its due to all the hoops and quality checks to get releases out the door at Microsoft, eg: DebugDiag - The Saga to RTM[^]
-
Hmm, I thought I was, but after the re-installation I am not sure whether the update process did install it... I can't see it mentioned anywhere in the About. Thanks - I will look into this in the morning.
