VS 2010 driving me insane
-
I read - a lot. Knowledge is power.
.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, 2001John Simmons / outlaw programmer wrote:
I read - a lot.
Of poetry?
I wanna be a eunuchs developer! Pass me a bread knife!
-
Sounds like the processor is off doing other interesting things instead working conscientiously for you!
------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave
Dalek Dave wrote:
Sounds like the processor is off doing other interesting things instead working conscientiously for you!
It's usually the disk. Guess things will be a lot better once SSDs get faster at performing writes and become more commonplace.
-
The core feature of Visual Studio is the ability to edit source code. That's #1. For me, though, Visual Studio 2010 is continually getting into a state where it no longer allows me to type. Usually I can just switch to another tab, then back again, or I close the file and reopen, and then I can edit again. There's no warning - just suddenly I can no longer type in that window. Sometimes if I switch away, then back, I see all the typing (and banging) that I did appear, meaning lots of Ctrl-Z-ing. However, I've just had a new one: I can no longer edit the second line in my current file. Everything else is fine, but I can't drag and drop, delete, type on it - nothing. Line 1 is great, line3, it welcomes my edits. But not line 2. Today is "Thou Shalt Not Touch Line 2 Day". I have to say that for all this talk of focus on quality in Microsoft products, they were using the wrong glasses. VS 2010 is becoming painful.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Does my head in as well, though I haven't tried VS 2010 yet. But in earlier versions it drives me nuts when I'm typing and then have to wait while the HD is hammered for a while before it catches up. It's even worse with resharper installed.
-
But power corrupts, so obviously reading is corrupting.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
I must be a veritable peat bog then :sigh:.
Software Zen:
delete this; -
The core feature of Visual Studio is the ability to edit source code. That's #1. For me, though, Visual Studio 2010 is continually getting into a state where it no longer allows me to type. Usually I can just switch to another tab, then back again, or I close the file and reopen, and then I can edit again. There's no warning - just suddenly I can no longer type in that window. Sometimes if I switch away, then back, I see all the typing (and banging) that I did appear, meaning lots of Ctrl-Z-ing. However, I've just had a new one: I can no longer edit the second line in my current file. Everything else is fine, but I can't drag and drop, delete, type on it - nothing. Line 1 is great, line3, it welcomes my edits. But not line 2. Today is "Thou Shalt Not Touch Line 2 Day". I have to say that for all this talk of focus on quality in Microsoft products, they were using the wrong glasses. VS 2010 is becoming painful.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Ah. They've actually moved the VS2003/VS2005/VS2008 bug down a line, and updated it in the process. You know the one: Open a new document, and the cursor doesn't display until you've typed a whole line and placed an end-of-line marker in the text. Sounds like progress to me. I bet for VS2012, line 3 will spontaneously combust.
Software Zen:
delete this; -
VS has decided that line 2 is the best line of code you've ever written and is making sure you don't throw it all away.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Well, I will admit it was a rather good line. Don't want to toot my own horn and all that, though. :-\
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
Well, I will admit it was a rather good line. Don't want to toot my own horn and all that, though. :-\
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Chris Maunder wrote:
Well, I will admit it was a rather good line. Don't want to toot my own horn and all that, though.
using Microsoft.VisualBasic;
That one? :rolleyes:
Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
-
Chris Maunder wrote:
Well, I will admit it was a rather good line. Don't want to toot my own horn and all that, though.
using Microsoft.VisualBasic;
That one? :rolleyes:
Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
From simplicity comes beauty. In this case, really, really simple.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
Have you switched from the default theme? If so switch back and try and replicate the bug.
Two heads are better than one.
It's happened with and without a different theme. Good point, though.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
It's happened with and without a different theme. Good point, though.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
The core feature of Visual Studio is the ability to edit source code. That's #1. For me, though, Visual Studio 2010 is continually getting into a state where it no longer allows me to type. Usually I can just switch to another tab, then back again, or I close the file and reopen, and then I can edit again. There's no warning - just suddenly I can no longer type in that window. Sometimes if I switch away, then back, I see all the typing (and banging) that I did appear, meaning lots of Ctrl-Z-ing. However, I've just had a new one: I can no longer edit the second line in my current file. Everything else is fine, but I can't drag and drop, delete, type on it - nothing. Line 1 is great, line3, it welcomes my edits. But not line 2. Today is "Thou Shalt Not Touch Line 2 Day". I have to say that for all this talk of focus on quality in Microsoft products, they were using the wrong glasses. VS 2010 is becoming painful.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Chris Maunder wrote:
For me, though, Visual Studio 2010 is continually getting into a state where it no longer allows me to type.Usually I can just switch to another tab, then back again, or I close the file and reopen, and then I can edit again. There's no warning - just suddenly I can no longer type in that window. Sometimes if I switch away, then back, I see all the typing (and banging) that I did appear, meaning lots of Ctrl-Z-ing.
That happened to me a lot in VS2008. I have just switched to VS2010 about 2 days ago but have yet to use it. I was hoping that annoying bug feature of VS was resolved. :mad:
Simply Elegant Designs JimmyRopes Designs
Think inside the box! ProActive Secure Systems
I'm on-line therefore I am. JimmyRopes -
Vikram A Punathambekar wrote:
there's no U in Superior
Paradox Of The Day? :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
For once, I hang my head in shame. :sigh: Obviously, I meant no second U.
Cheers, Vikram. (Got my troika of CCCs!)
-
Vikram A Punathambekar wrote:
there's no U in Superior
What about the one after the S? :laugh: :laugh: :rolleyes:
I don't have ADHD, I have ADOS... Attention Deficit oooh SHINY!! If you like cars, check out the Booger Mobile blog | If you feel generous - make a donation to Camp Quality!!
Hoisted by my own petard. :-O Clearly, I should have said "There's no second U in Superior".
Cheers, Vikram. (Got my troika of CCCs!)