VS 2010 driving me insane
-
I suppose for those who are used to working completely in the IDE it would be weird to toggle back and forth between the compiler / debugger and an editor (though perhaps not as weird as being unable to edit line 2). I've been doing it so long it's natural to me and I simply can't imagine trusting my coding, i.e. what I spend most of my time doing when developing, to a subpar application. No matter what I'm doing, I like power tools. I wouldn't use a chainsaw to change sparkplugs, so why would I want to use a compiler / debugger to write source code? The right tool for the job, and all that.
Christopher Duncan
www.PracticalUSA.com
Author of The Career Programmer and Unite the Tribes
Copywriting ServicesChristopher Duncan wrote:
I've been doing it so long it's natural to me and I simply can't imagine trusting my coding, i.e. what I spend most of my time doing when developing, to a subpar application.
That's a powerful statement which I do not think is true either. Whatever, editor you are using does it understand code as code or does it simply consider it text? Does it have contextual Intellisense? Can it refactor your code? Modern IDE editors do that and even they have a few glitches, they do it better than any regular text editors. Text editors are meant to edit text, IDEs are meant to edit code. The right tool for editing text is a text editor and the right tool for editing code is an IDE. VS for C#/VB.NET and Eclipse for Java. I am all for right tool for right job but the job has to be defined correctly and be known first:)
-
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
unplug it, then plug it back in. or maybe detonate a hydrogen bomb near it ?
-
Christopher Duncan wrote:
I've been doing it so long it's natural to me and I simply can't imagine trusting my coding, i.e. what I spend most of my time doing when developing, to a subpar application.
That's a powerful statement which I do not think is true either. Whatever, editor you are using does it understand code as code or does it simply consider it text? Does it have contextual Intellisense? Can it refactor your code? Modern IDE editors do that and even they have a few glitches, they do it better than any regular text editors. Text editors are meant to edit text, IDEs are meant to edit code. The right tool for editing text is a text editor and the right tool for editing code is an IDE. VS for C#/VB.NET and Eclipse for Java. I am all for right tool for right job but the job has to be defined correctly and be known first:)
Rama Krishna Vavilala wrote:
Text editors are meant to edit text, IDEs are meant to edit code.
Text editors (notepad) are meant to edit text, IDEs are meant to compile and debug, with a built in editor to help you fix your screwup when you find it. Programmers editors are meant for programming, and doing it really, really fast. Intellisense, refactoring, etc. are supported by Visual SlickEdit and I suspect all of its peers. As for the definition of the job, it's kicking out good, maintainable code and meeting the deadline. IDEs, with VS being a great example, try to be all things to all people. That's rarely a recipe for best in class functionality. And by the way, I didn't just come up with this perspective out of the clear blue sky. I've used IDEs, visual design tools, programmers editors, etc. over the years, and that's how I've formed my opinions on the merits of half assed IDE editors, half assed IDE visual design tools (yeah, VS, I'm talkin' to you), etc. For compiling and debugging, VS gets my vote, but it's hardly best of breed in the other categories.
Christopher Duncan
www.PracticalUSA.com
Author of The Career Programmer and Unite the Tribes
Copywriting Services -
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
Thank you, that makes me feel much better. Now I am not allowed work on .NET projects yet, I have to use some java crap that pretends to be an IDE. The problem I had yesterday is even funnier than yours: Everything I typed appears backwards. Java becomes avaJ, String becomes gnirtS, which makes me want to flesym llik. Now I know I am not the only one who is suffering. :-D
My .NET Business Application Framework My Younger Son & His "PET"
-
Rama Krishna Vavilala wrote:
Text editors are meant to edit text, IDEs are meant to edit code.
Text editors (notepad) are meant to edit text, IDEs are meant to compile and debug, with a built in editor to help you fix your screwup when you find it. Programmers editors are meant for programming, and doing it really, really fast. Intellisense, refactoring, etc. are supported by Visual SlickEdit and I suspect all of its peers. As for the definition of the job, it's kicking out good, maintainable code and meeting the deadline. IDEs, with VS being a great example, try to be all things to all people. That's rarely a recipe for best in class functionality. And by the way, I didn't just come up with this perspective out of the clear blue sky. I've used IDEs, visual design tools, programmers editors, etc. over the years, and that's how I've formed my opinions on the merits of half assed IDE editors, half assed IDE visual design tools (yeah, VS, I'm talkin' to you), etc. For compiling and debugging, VS gets my vote, but it's hardly best of breed in the other categories.
Christopher Duncan
www.PracticalUSA.com
Author of The Career Programmer and Unite the Tribes
Copywriting ServicesWhat does Visual Slick Edit give me which the IDE editor does not? I see that it is full of features but I can see all those features in VS editor too. Also I do not see it supporting any kind of refactoring.
-
What does Visual Slick Edit give me which the IDE editor does not? I see that it is full of features but I can see all those features in VS editor too. Also I do not see it supporting any kind of refactoring.
Well for one thing, you can edit Line 2. :)
Christopher Duncan
www.PracticalUSA.com
Author of The Career Programmer and Unite the Tribes
Copywriting Services -
Well for one thing, you can edit Line 2. :)
Christopher Duncan
www.PracticalUSA.com
Author of The Career Programmer and Unite the Tribes
Copywriting ServicesThat's something Chris found probably the soy latte did not work for him :). He needs real coffee. I tried SlickEdit after a friend recommended it, but he was not able to show me anything concrete which was not already there in VS. He had lot of "Aha" moments. I do not buy that the whole premise that VS editor is somehow half baked or that IDE's meant for writing, compiling and debugging code cannot be good in all these things. In fact code editing is much more of a defining feature of an IDE than the ability to debug.
-
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
I've had a similar issue with VS05, except it would be an entire file I couldn't edit. I couldn't even see my cursor when I clicked on it. But if I tapped the Shift key, or sometimes turned caps lock on and off, then it would start working. I think I absentmindedly held down the Shift key while I clicked on something else, and VS was like "WTF, I don't know what to do with that!?" So it decided to wait until I "undid" whatever it was i did. Dybs
The shout of progress is not "Eureka!" it's "Strange... that's not what i expected". - peterchen
-
You know I just had to fire up a dos prompt to see if it still lived. Regrettably, it's suffered the same fate as MS development tool quality. Edlin may be gone to that great bit bucket in the sky, but you'll be delighted to know that edit lives on. :)
Christopher Duncan
www.PracticalUSA.com
Author of The Career Programmer and Unite the Tribes
Copywriting ServicesChristopher Duncan wrote:
edit lives on
Wonderful! An editor that just works! :-D I'm glad it survived...
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
I bow to your superiour knowledge.
------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave
Second notice - there's no U in Superior.
Cheers, Vikram. (Got my troika of CCCs!)
-
Second notice - there's no U in Superior.
Cheers, Vikram. (Got my troika of CCCs!)
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).
-
Second notice - there's no U in Superior.
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!!
-
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!!
maybe there isn't an S in uperior? :)
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).
-
maybe there isn't an S in uperior? :)
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).
There's no R in ass... (Disclaimer - Must be pronounced the Australian way for that joke to make sense!)
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!!
-
There's no R in ass... (Disclaimer - Must be pronounced the Australian way for that joke to make sense!)
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!!
Now that is a word without a U. :)
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).
-
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
-
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
-
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.
