VS 2010 driving me insane
-
It's not a lock-up. Everything works perfectly normally except I could not edit line 2. If the whole file gets locked then I can edit any other file, compile, whatever. Just that file. I then jiggle a mysterious *something* and then it works again. I think it's the WPF
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
You should post your problem in the Quick Answers, we've the
MysticalPowerstag there. :-DIf the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
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
Not the line 2 thing but the rest I've had in both VS2005 and VS2008 although not recently in 2008 and I only use 2005 infrequently. Unlike you, however, I never found the secret *something*, the only cure in my case was to close VS and reopen it.
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” Why do programmers often confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
-
My suspicion is that it was one of the adorners. The adorner layer sits on top, so it wasn't registering on your clicks underneath - hence modifying the line elsewhere.
"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.
Pete O'Hanlon wrote:
My suspicion is that it was one of the adorners.
Sounds like something you can only find in a gay bar...
.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 -
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
Have you tried turning it off then back on again?
-
Pete O'Hanlon wrote:
My suspicion is that it was one of the adorners.
Sounds like something you can only find in a gay bar...
.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, 2001I wouldn't know mate. I'm secure in my masculinity; I don't need to compensate with a big gun. ;P
"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.
-
Have you tried turning it off then back on again?
Sounds like dating advice - have you tried turning her on again?
"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.
-
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 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 Services -
Pete O'Hanlon wrote:
My suspicion is that it was one of the adorners.
Sounds like something you can only find in a gay bar...
.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, 2001I 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
-
Sounds like dating advice - have you tried turning her on again?
"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.
Sound advice is sound in many situations - up to and not excluding the fairer sex! (although knowing which buttons to press in that case is a matter of on-going research...)
-
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
Have you tried disabling all the addons/extensions you have. Perhaps, you've just got a buggy extension. You know..like have you installed the addon called ThouShaltNotTouchLineTwo?
-
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 ServicesWhat did you do during the war Grandpa Chris? :)
-
What did you do during the war Grandpa Chris? :)
Took potshots at smartass young whippersnappers like you, for the most part. :) I'm not opposed to something that does the job better than The Old Way. I was using Borland Turbo C's IDE with glee when MS C coders were fumbling around with a command line compiler, separate debugger, and some clumsy excuse for a Microsoft editor (m, if I recall correctly). But as good as the Borland IDE was for its time, someone showed me Brief and how much faster I could get my job done with it, and I immediately switched my coding habits. Intellisense is nice but Visual SlickEdit (and its competitors, I'm sure) do that, too. What, just because VS has a built in editor, I'm supposed to use it or I'm a Luddite? Even if it's pathetic? What if they threw in some photo editing capabilities - should I sell Photoshop? Man, what Koolaid have you been drinking? And by the way, bubba - you're older than me, if I recall. ;P
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
Chris Maunder wrote:
Today is "Thou Shalt Not Touch Line 2 Day".
how will you do THAT graphic for Bob??
_________________________ John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others." Shhhhh.... I am not really here. I am a figment of your imagination.... I am still in my cave so this must be an illusion....
-
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
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, 2001 -
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, 2001But 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.
-
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 was about to install that monstrosity. You're giving me pause.
.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 -
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 take it CTRL/F5 does not fix it for you? I can only suggest you put a big 5-line comment block on top of every file you create. ;P
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).
-
Took potshots at smartass young whippersnappers like you, for the most part. :) I'm not opposed to something that does the job better than The Old Way. I was using Borland Turbo C's IDE with glee when MS C coders were fumbling around with a command line compiler, separate debugger, and some clumsy excuse for a Microsoft editor (m, if I recall correctly). But as good as the Borland IDE was for its time, someone showed me Brief and how much faster I could get my job done with it, and I immediately switched my coding habits. Intellisense is nice but Visual SlickEdit (and its competitors, I'm sure) do that, too. What, just because VS has a built in editor, I'm supposed to use it or I'm a Luddite? Even if it's pathetic? What if they threw in some photo editing capabilities - should I sell Photoshop? Man, what Koolaid have you been drinking? And by the way, bubba - you're older than me, if I recall. ;P
Christopher Duncan
www.PracticalUSA.com
Author of The Career Programmer and Unite the Tribes
Copywriting ServicesChristopher Duncan wrote:
Man, what Koolaid have you been drinking? And by the way, bubba - you're older than me, if I recall.
In your dreams, sonny ;)
Christopher Duncan wrote:
Intellisense is nice but Visual SlickEdit (and its competitors, I'm sure) do that, too. What, just because VS has a built in editor, I'm supposed to use it or I'm a Luddite? Even if it's pathetic? What if they threw in some photo editing capabilities - should I sell Photoshop?
Seriously, though, I agree with you on that. You need tools and good tools at that and the best tools available when possible. Although there's a limit. For instance, in various bits and pieces that I do I need to produce nice page layouts. Now I could sink a chunk of money into InDesign - and it's not like I couldn't afford to - but I'd never use an eighth of the features or get passed the learning curve which is why I go for something more accessible. It's almost the same with VS, but slightly in reverse. VS does an extremely good job of masking the complexity of what's really going on at the expense of understanding what's really going on, but by masking that complexity it pretends that there is nothing better. Bring back 6502 machine code, is what I say. I understood computers back then!
-
I take it CTRL/F5 does not fix it for you? I can only suggest you put a big 5-line comment block on top of every file you create. ;P
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).
/////////////////////////////////////////////////////////////////
// Company : Code Project
// Author : Chris Maunder
// Description : This code autogenerated because of a bug
/////////////////////////////////////////////////////////////////"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.
-
/////////////////////////////////////////////////////////////////
// Company : Code Project
// Author : Chris Maunder
// Description : This code autogenerated because of a bug
/////////////////////////////////////////////////////////////////"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.
See? that wasn't hard, was it? Not worth the fuss. Such functionality could easily be added to the CodeProject Visual Studio add-in. :)
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).