Why VS 2010 sucks today
-
So I finally update my windows installation to get the Windows Automation API 3.0, as VS would nag about it every time it got opened. And now it crashes when you hover over something when debugging. So if you wanted to see the value of some variable by hovering over it you instead get a crash and have to restart visual studio. The crash is actually a null reference exception in the drawing code for the fancy new UI elements. I should have just kept ignoring the pop-up.
My current favourite word: Harsh!
-SK Genius
-
So I finally update my windows installation to get the Windows Automation API 3.0, as VS would nag about it every time it got opened. And now it crashes when you hover over something when debugging. So if you wanted to see the value of some variable by hovering over it you instead get a crash and have to restart visual studio. The crash is actually a null reference exception in the drawing code for the fancy new UI elements. I should have just kept ignoring the pop-up.
My current favourite word: Harsh!
-SK Genius
On my machine, the Windows Automation API 3.0 refused to install for quite a while. I would get the popup, goto the download site, click the correct download link (I tried them all eventually so I know I got the right one) and then it would tell me the update doesn't apply to my system...
-
On my machine, the Windows Automation API 3.0 refused to install for quite a while. I would get the popup, goto the download site, click the correct download link (I tried them all eventually so I know I got the right one) and then it would tell me the update doesn't apply to my system...
Yeah I got that a lot, it turns out that you may need to install the latest service pack first (which I did).
My current favourite word: Harsh!
-SK Genius
-
So I finally update my windows installation to get the Windows Automation API 3.0, as VS would nag about it every time it got opened. And now it crashes when you hover over something when debugging. So if you wanted to see the value of some variable by hovering over it you instead get a crash and have to restart visual studio. The crash is actually a null reference exception in the drawing code for the fancy new UI elements. I should have just kept ignoring the pop-up.
My current favourite word: Harsh!
-SK Genius
I'm not a fan of VS2010 since last week when I installed it. Messed up my VS2008 C++ builds. Messy way of setting up includes. Can't customize it. Tried to drag a toolbar anywhere yet?? Uninstalled last night. I'm betting it's messed up my entire system and I'm going to have to piece together all my previous work now. C#4 might really introduce some slick stuff but VS2010 just sucks today..
ed ~"Watch your thoughts; they become your words. Watch your words they become your actions. Watch your actions; they become your habits. Watch your habits; they become your character. Watch your character; it becomes your destiny." -Frank Outlaw.
-
I'm not a fan of VS2010 since last week when I installed it. Messed up my VS2008 C++ builds. Messy way of setting up includes. Can't customize it. Tried to drag a toolbar anywhere yet?? Uninstalled last night. I'm betting it's messed up my entire system and I'm going to have to piece together all my previous work now. C#4 might really introduce some slick stuff but VS2010 just sucks today..
ed ~"Watch your thoughts; they become your words. Watch your words they become your actions. Watch your actions; they become your habits. Watch your habits; they become your character. Watch your character; it becomes your destiny." -Frank Outlaw.
-
I'm using it for one project at present; and my recommendation for future efforts will be to stay with 2k8 until 2k12(?) is released.
3x12=36 2x12=24 1x12=12 0x12=18
Should have asked a few weeks back!!! :mad: **kicks self**
ed ~"Watch your thoughts; they become your words. Watch your words they become your actions. Watch your actions; they become your habits. Watch your habits; they become your character. Watch your character; it becomes your destiny." -Frank Outlaw.
-
So I finally update my windows installation to get the Windows Automation API 3.0, as VS would nag about it every time it got opened. And now it crashes when you hover over something when debugging. So if you wanted to see the value of some variable by hovering over it you instead get a crash and have to restart visual studio. The crash is actually a null reference exception in the drawing code for the fancy new UI elements. I should have just kept ignoring the pop-up.
My current favourite word: Harsh!
-SK Genius
Thanks for the heads-up. I clicked the link one of the first times it popped up and after reading the page, I decided I wasn't using the stuff this is supposed to speed up, so I've been ignoring it since. It is irritating tho.
Pete
-
So I finally update my windows installation to get the Windows Automation API 3.0, as VS would nag about it every time it got opened. And now it crashes when you hover over something when debugging. So if you wanted to see the value of some variable by hovering over it you instead get a crash and have to restart visual studio. The crash is actually a null reference exception in the drawing code for the fancy new UI elements. I should have just kept ignoring the pop-up.
My current favourite word: Harsh!
-SK Genius
Have you checked the list of available hotfixes[^]? Also, update your graphics driver - that helped a lot since many drivers are still causing problems with WPF. Those two things helped make VS2010 very useable for me (I use it daily on 5 different projects including Web Apps, C++ and C# desktop apps). Cheers, Drew.
-
Have you checked the list of available hotfixes[^]? Also, update your graphics driver - that helped a lot since many drivers are still causing problems with WPF. Those two things helped make VS2010 very useable for me (I use it daily on 5 different projects including Web Apps, C++ and C# desktop apps). Cheers, Drew.
sadly a driver update didn't stop it from behaving like a yoyo for me on winforms dev, although dumping the crap driver dell blighted the quadro with did at least allow my laptop to correctly detect the resolution of a monitor plugged in after boot.
3x12=36 2x12=24 1x12=12 0x12=18
-
sadly a driver update didn't stop it from behaving like a yoyo for me on winforms dev, although dumping the crap driver dell blighted the quadro with did at least allow my laptop to correctly detect the resolution of a monitor plugged in after boot.
3x12=36 2x12=24 1x12=12 0x12=18
Dan Neely wrote:
sadly a driver update didn't stop it from behaving like a yoyo for me on winforms dev, although dumping the crap driver dell blighted the quadro with did at least allow my laptop to correctly detect the resolution of a monitor plugged in after boot.
I'm still praying for NVidia to release a driver that fixes all the WPF problems. I still periodically get problems where the client drawing area of WPF apps gets mangled and I have to restart (although I've narrowed it down to one app. in particular now - if I don't run it I don't have problems). Cheers, Drew.