Veteran VS2008 users here? Ever lost your debug functions?
-
Yes, I know VS2008 is old, but I have to use it for a development project. Anyway, a couple of weeks ago, I installed some software from Intel that broke my VS2008. Nothing would compile, I could not set breakpoints, etc. Using a clean Windows 10 VM, I re-installed VS2008, SP1 and an ATL update required for WEC7 development. I can compile and set breakpoints again. Joy. Now it gets a little weird. The step over (F10) and step into (F11) functions refuse to work. They are being treated as the go (F5) commands, making it just about impossible to get anything done. Note that even the menu debug commands behave this way. Now it gets a little weird now - it seems to be project/solution related. If I debug project A the functions work, debug Project B (the one I really need to work on) they don't. So a clean re-install did not fix this, a reset to all settings didn't fix it, deleting .suo, etc files didn't fix it... maddening :omg: Thoughts? Ever run into this?
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
Yes, I know VS2008 is old, but I have to use it for a development project. Anyway, a couple of weeks ago, I installed some software from Intel that broke my VS2008. Nothing would compile, I could not set breakpoints, etc. Using a clean Windows 10 VM, I re-installed VS2008, SP1 and an ATL update required for WEC7 development. I can compile and set breakpoints again. Joy. Now it gets a little weird. The step over (F10) and step into (F11) functions refuse to work. They are being treated as the go (F5) commands, making it just about impossible to get anything done. Note that even the menu debug commands behave this way. Now it gets a little weird now - it seems to be project/solution related. If I debug project A the functions work, debug Project B (the one I really need to work on) they don't. So a clean re-install did not fix this, a reset to all settings didn't fix it, deleting .suo, etc files didn't fix it... maddening :omg: Thoughts? Ever run into this?
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Perhaps some project-specific configurations are overriding the behavior? Check this thread, [asp.net - 'Step Into' not working in Visual Studio? - Stack Overflow](https://stackoverflow.com/questions/28783233/step-into-not-working-in-visual-studio)
The shit I complain about It's like there ain't a cloud in the sky and it's raining out - Eminem ~! Firewall !~
-
Yes, I know VS2008 is old, but I have to use it for a development project. Anyway, a couple of weeks ago, I installed some software from Intel that broke my VS2008. Nothing would compile, I could not set breakpoints, etc. Using a clean Windows 10 VM, I re-installed VS2008, SP1 and an ATL update required for WEC7 development. I can compile and set breakpoints again. Joy. Now it gets a little weird. The step over (F10) and step into (F11) functions refuse to work. They are being treated as the go (F5) commands, making it just about impossible to get anything done. Note that even the menu debug commands behave this way. Now it gets a little weird now - it seems to be project/solution related. If I debug project A the functions work, debug Project B (the one I really need to work on) they don't. So a clean re-install did not fix this, a reset to all settings didn't fix it, deleting .suo, etc files didn't fix it... maddening :omg: Thoughts? Ever run into this?
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
Yes, I know VS2008 is old, but I have to use it for a development project. Anyway, a couple of weeks ago, I installed some software from Intel that broke my VS2008. Nothing would compile, I could not set breakpoints, etc. Using a clean Windows 10 VM, I re-installed VS2008, SP1 and an ATL update required for WEC7 development. I can compile and set breakpoints again. Joy. Now it gets a little weird. The step over (F10) and step into (F11) functions refuse to work. They are being treated as the go (F5) commands, making it just about impossible to get anything done. Note that even the menu debug commands behave this way. Now it gets a little weird now - it seems to be project/solution related. If I debug project A the functions work, debug Project B (the one I really need to work on) they don't. So a clean re-install did not fix this, a reset to all settings didn't fix it, deleting .suo, etc files didn't fix it... maddening :omg: Thoughts? Ever run into this?
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
Perhaps some project-specific configurations are overriding the behavior? Check this thread, [asp.net - 'Step Into' not working in Visual Studio? - Stack Overflow](https://stackoverflow.com/questions/28783233/step-into-not-working-in-visual-studio)
The shit I complain about It's like there ain't a cloud in the sky and it's raining out - Eminem ~! Firewall !~
You would think, but depending on machine / project the behavior varies.
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
It's a long shot, but if the issue is project-specific, then you can try to delete the .suo file from the project directory and re-open the project.
"Five fruits and vegetables a day? What a joke! Personally, after the third watermelon, I'm full."
This is a common suggestion - I've done it several times on multiple projects with no success. The part that I don't get is that the actual menu functions don't work, implying some sort of corruption in VS2008 - *but* that makes no sense since one project will work and the other won't. It should be corrupt for both.
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
Another approach is to create a VS2008 valid project and to import all your files from the old one. Then you will have your app settings fresh new. I know, is a little work to do, but I am sure will solve your issue.
Good suggestion, but I cannot even get a simple Yellow World dialog app to debug properly. Maddening. Thanks for the suggestions
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
Yes, I know VS2008 is old, but I have to use it for a development project. Anyway, a couple of weeks ago, I installed some software from Intel that broke my VS2008. Nothing would compile, I could not set breakpoints, etc. Using a clean Windows 10 VM, I re-installed VS2008, SP1 and an ATL update required for WEC7 development. I can compile and set breakpoints again. Joy. Now it gets a little weird. The step over (F10) and step into (F11) functions refuse to work. They are being treated as the go (F5) commands, making it just about impossible to get anything done. Note that even the menu debug commands behave this way. Now it gets a little weird now - it seems to be project/solution related. If I debug project A the functions work, debug Project B (the one I really need to work on) they don't. So a clean re-install did not fix this, a reset to all settings didn't fix it, deleting .suo, etc files didn't fix it... maddening :omg: Thoughts? Ever run into this?
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Well, I may have isolated the issue a little closer - the behavior changes depending on what SDK I select - I have multiple embedded CE projects.
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
Yes, I know VS2008 is old, but I have to use it for a development project. Anyway, a couple of weeks ago, I installed some software from Intel that broke my VS2008. Nothing would compile, I could not set breakpoints, etc. Using a clean Windows 10 VM, I re-installed VS2008, SP1 and an ATL update required for WEC7 development. I can compile and set breakpoints again. Joy. Now it gets a little weird. The step over (F10) and step into (F11) functions refuse to work. They are being treated as the go (F5) commands, making it just about impossible to get anything done. Note that even the menu debug commands behave this way. Now it gets a little weird now - it seems to be project/solution related. If I debug project A the functions work, debug Project B (the one I really need to work on) they don't. So a clean re-install did not fix this, a reset to all settings didn't fix it, deleting .suo, etc files didn't fix it... maddening :omg: Thoughts? Ever run into this?
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
In case someone runs into this in the future - Microsoft has released an update for SP1 for VS2008 Professional that addresses the problem I was having. I really think I applied it one time before, but maybe I got things out of sequence. Anyway, it's KB2483802, link: Download Visual Studio 2008 update for Windows Embedded Compact 7 from Official Microsoft Download Center[^]
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759