|
|
You're in the
visual studio .net debugging
group:Office or InDesign breaks VS 2005 debugging?
visual studio .net debugging:
I've recently updated my Office install to 2007, and added the Windows Desktop Search feature initially to get rid of the intrusively annoying prompt to use it in Outlook. (I've now figured how to turn this prompt off). I also installed Adobe InDesign CS3 (trial) to support a user request for art files received...(yes, I have to wear many hats.) A very negative side effect (and I'm willing to consider it a coincidence, though it's the only changes recently made) has been the impact on my Visual Studio 2005 debugging. Let me be clear - debugging isn't entirely broken. But there is definitely a problem with the "child" projects. I did try uninstalling desktop search as my first fix option, but this hasn't helped, so it may be unrelated to Office. I have left DS UNinstalled for the meantime. The scenario: An ASP.NET 2.0 website, using WAP and nested MasterPages, sub-projects set to compile libs to the parent project's /bin, using local IIS server rather than the VS built-in server. This is per instructions on the msdn blog: http://blogs.msdn.com/webdevtools/archive/2006/07/01/652986.aspx I've been working on this project for several months without issue. So, prior to installing Office 2007, I was able to make a change to the child-project code, recompile that dll, set a breakpoint and run the solution (which starts with the parent project). This would take me to the start page of the parent project, from which I would navigate to the page needing testing and follow conditions to trigger the breakpoint, and get into the child project for debugging. All well and good. After Office 2007/desktop search (which is good, though the ribbon takes some getting used to) and the debug symbols for the child project are no longer loaded, so breakpoints will never be hit. I get both the breakpoint warnings of: "No symbols loaded for this document" and then "No executable code is associated with this line". I know there's a really long discussion about symbols not being loaded, but my woes don't end there. Now, when I make a change to the child project and recompile - either through "Build" or "Rebuild" - trying to F5 the solution hangs with the browser continually trying to connect. I have to use Task Manager to kill off the aspnet_wp.exe process before I can return to the IDE (or use the Windows crash reporting tool). I have to "kill" aspnet_wp at least four times, (sometimes more) before the IDE finally returns to normal. I have investigated using aspnet_regiis with various options such as -ir -enable (see list below), but while these will allow the root site to run again on F5, the system still fails to load the debug files for the "child" project. After issuing a build or rebuild command in the IDE, VS2005 status bar will indicate build completed successfully within a few seconds, but the IDE will not respond to any mouse input for upto 30 seconds. I have to re-issue the aspnet_regiis -i -enable command after every build/rebuild in order to get even the root (unaltered) site to load! The sub-project still won't debug. I have checked the pdb is dated same as new dll version. I have tried purging the local settings assembly folder. I have tried deleting the dll and pdb files and recreating by rebuild. I have tried setting the advanced compile options to generate a Full debug file (all I got was a larger pdb). (Optimisations are on for each project) I may have screwed up the aspnet_regiis command in my frustration. I have tried the following switches: -ir -enable -iru -enable -i -enable -c -r (I had to visit my 1.1 asp.net apps in Computer Manager and reset them back to use 1.1 framework) -s path (in my case, w3svc/1/root/copeohs/) I do have WCF and WPF extensions installed, but these were put on a while back with no issue arrising. I am getting REALLY annoyed that I cannot debug this solution properly - it's for my company's main website, so it's got to be a fixable issue. If necessary I will consider a full VS re-install, but I would prefer to avoid this if at all possible. I am pretty certain it remains a Framework config issue of some sort. Any constructive help will be gratefully received. Al
I should add my system config is:
XP Pro SP2 VS 2003 VS 2005 SP1
Further to this topic, I tested the same project on my home PC which also
has Office 2007, with the same problem - will not load the symbols for the sub-projects. Given tha I was using and debugging the sub-projects in this solution before Office 2007, and that Office 2007 and IDesign were the ONLY changes made on the Dev PC in that time period, I am led to the conclusion that Office 2007 must break this functionality. MS products breaking other MS products. Will try next on the Virtual PC without Office 2007 to confirm. May have to dump Offcie 2007 and revert to my last system ghost backup... Has anyone else had this issue? Is there a known fix? I cannot do without the sub-projects being debuggable!! Al [quoted text, click to view] "Alec MacLean" <alec.maclean@NO-SPAM-copeohs.com> wrote in message news:emSDUr22HHA.212@TK2MSFTNGP05.phx.gbl... > Hi. > > I've recently updated my Office install to 2007, and added the Windows > Desktop Search feature initially to get rid of the intrusively annoying > prompt > to use it in Outlook. (I've now figured how to turn this prompt off). > > I also installed Adobe InDesign CS3 (trial) to support a user request for > art files received...(yes, I have to wear many hats.) > > A very negative side effect (and I'm willing to consider it a coincidence, > though it's the only changes recently made) > has been the impact on my Visual Studio 2005 debugging. > > Let me be clear - debugging isn't entirely broken. But there is > definitely a > problem with the "child" projects. > > I did try uninstalling desktop search as my first fix option, but this > hasn't helped, so it may be unrelated to Office. I have left DS > UNinstalled for the meantime. > > The scenario: > > An ASP.NET 2.0 website, using WAP and nested MasterPages, > sub-projects set to compile libs to the parent project's /bin, using local > IIS server rather than the VS built-in server. > > This is per instructions on the msdn blog: > http://blogs.msdn.com/webdevtools/archive/2006/07/01/652986.aspx > > I've been working on this project for several months without issue. > > So, prior to installing Office 2007, I was able to make a change to the > child-project code, recompile that dll, set a breakpoint and run the > solution (which starts with the parent project). This would take me to > the > start page of the parent project, from which I would navigate to the page > needing testing and follow conditions to trigger the breakpoint, and get > into the child project for debugging. > > All well and good. > > After Office 2007/desktop search (which is good, though the ribbon takes > some getting used to) and the debug symbols for the child project are no > longer loaded, so breakpoints will never be hit. > > I get both the breakpoint warnings of: "No symbols loaded for this > document" > and then "No executable code is associated with this line". > > I know there's a really long discussion about symbols not being loaded, > but > my woes don't end there. > > Now, when I make a change to the child project and recompile - either > through "Build" or "Rebuild" - trying to F5 the solution hangs with the > browser continually trying to connect. I have to use Task Manager to kill > off the aspnet_wp.exe process before I can return to the IDE (or use the > Windows crash reporting tool). I have to > "kill" aspnet_wp at least four times, (sometimes more) before the IDE > finally returns to normal. > > I have investigated using aspnet_regiis with various options such > as -ir -enable (see list below), but while these will allow the root site > to > run again on F5, the system still fails to load the debug files for the > "child" project. > > After issuing a build or rebuild command in the IDE, VS2005 status bar > will > indicate build completed successfully within a few seconds, but the IDE > will > not respond to any mouse input for upto 30 seconds. I have to re-issue > the > aspnet_regiis -i -enable command after every build/rebuild in order to get > even the root > (unaltered) site to load! The sub-project still won't debug. > > I have checked the pdb is dated same as new dll version. > I have tried purging the local settings assembly folder. > I have tried deleting the dll and pdb files and recreating by rebuild. > I have tried setting the advanced compile options to generate a Full debug > file (all I got was a larger pdb). > (Optimisations are on for each project) > > > I may have screwed up the aspnet_regiis command in my frustration. I have > tried the following switches: > -ir -enable > -iru -enable > -i -enable > -c > -r (I had to visit my 1.1 asp.net apps in Computer Manager and reset > them > back to use 1.1 framework) > -s path (in my case, w3svc/1/root/copeohs/) > > I do have WCF and WPF extensions installed, but these were put on a while > back with no issue arrising. > > I am getting REALLY annoyed that I cannot debug this solution properly - > it's for my company's main website, so it's got to be a fixable issue. > > If necessary I will consider a full VS re-install, but I would prefer to > avoid this if at all possible. > > I am pretty certain it remains a Framework config issue of some sort. > > Any constructive help will be gratefully received. > > Al > >
OK,
I can now fully recant my question of Office 2007 or Adobe having anything to do with the debug problem. I rewound my PC back to it's state in Feb by Ghosting it back to image taken then. Only have a few updates and couple of additional tools to add to make up the difference. I determined that the debugger exhibits the same odd behaviour under those conditions of a known-good install. I have now discovered that the issue seems to be related to how much code is in a page's code-behind. I know it shouldn't, but that's what I'm seeing. If I add a block of code statements (e.g. a few link button handlers), the page in question WILL then load symbols and enter debug as expected. Will document further (with images) and then upload to blog page once done. Will post address here once completed. Al [quoted text, click to view] "Alec MacLean" <alec.maclean@NO-SPAM-copeohs.com> wrote in message news:%23K6fFOY3HHA.5740@TK2MSFTNGP04.phx.gbl... > Further to this topic, I tested the same project on my home PC which also > has Office 2007, with the same problem - will not load the symbols for the > sub-projects. > > Given tha I was using and debugging the sub-projects in this solution > before Office 2007, and that Office 2007 and IDesign were the ONLY changes > made on the Dev PC in that time period, I am led to the conclusion that > Office 2007 must break this functionality. > > MS products breaking other MS products. > > Will try next on the Virtual PC without Office 2007 to confirm. May have > to dump Offcie 2007 and revert to my last system ghost backup... > > Has anyone else had this issue? Is there a known fix? > > I cannot do without the sub-projects being debuggable!! > > Al > > > "Alec MacLean" <alec.maclean@NO-SPAM-copeohs.com> wrote in message > news:emSDUr22HHA.212@TK2MSFTNGP05.phx.gbl... >> Hi. >> >> I've recently updated my Office install to 2007, and added the Windows >> Desktop Search feature initially to get rid of the intrusively annoying >> prompt >> to use it in Outlook. (I've now figured how to turn this prompt off). >> >> I also installed Adobe InDesign CS3 (trial) to support a user request for >> art files received...(yes, I have to wear many hats.) >> >> A very negative side effect (and I'm willing to consider it a >> coincidence, though it's the only changes recently made) >> has been the impact on my Visual Studio 2005 debugging. >> >> Let me be clear - debugging isn't entirely broken. But there is >> definitely a >> problem with the "child" projects. >> >> I did try uninstalling desktop search as my first fix option, but this >> hasn't helped, so it may be unrelated to Office. I have left DS >> UNinstalled for the meantime. >> >> The scenario: >> >> An ASP.NET 2.0 website, using WAP and nested MasterPages, >> sub-projects set to compile libs to the parent project's /bin, using >> local IIS server rather than the VS built-in server. >> >> This is per instructions on the msdn blog: >> http://blogs.msdn.com/webdevtools/archive/2006/07/01/652986.aspx >> >> I've been working on this project for several months without issue. >> >> So, prior to installing Office 2007, I was able to make a change to the >> child-project code, recompile that dll, set a breakpoint and run the >> solution (which starts with the parent project). This would take me to >> the >> start page of the parent project, from which I would navigate to the page >> needing testing and follow conditions to trigger the breakpoint, and get >> into the child project for debugging. >> >> All well and good. >> >> After Office 2007/desktop search (which is good, though the ribbon takes >> some getting used to) and the debug symbols for the child project are no >> longer loaded, so breakpoints will never be hit. >> >> I get both the breakpoint warnings of: "No symbols loaded for this >> document" >> and then "No executable code is associated with this line". >> >> I know there's a really long discussion about symbols not being loaded, >> but >> my woes don't end there. >> >> Now, when I make a change to the child project and recompile - either >> through "Build" or "Rebuild" - trying to F5 the solution hangs with the >> browser continually trying to connect. I have to use Task Manager to >> kill >> off the aspnet_wp.exe process before I can return to the IDE (or use the >> Windows crash reporting tool). I have to >> "kill" aspnet_wp at least four times, (sometimes more) before the IDE >> finally returns to normal. >> >> I have investigated using aspnet_regiis with various options such >> as -ir -enable (see list below), but while these will allow the root site >> to >> run again on F5, the system still fails to load the debug files for the >> "child" project. >> >> After issuing a build or rebuild command in the IDE, VS2005 status bar >> will >> indicate build completed successfully within a few seconds, but the IDE >> will >> not respond to any mouse input for upto 30 seconds. I have to re-issue >> the >> aspnet_regiis -i -enable command after every build/rebuild in order to >> get even the root >> (unaltered) site to load! The sub-project still won't debug. >> >> I have checked the pdb is dated same as new dll version. >> I have tried purging the local settings assembly folder. >> I have tried deleting the dll and pdb files and recreating by rebuild. >> I have tried setting the advanced compile options to generate a Full >> debug >> file (all I got was a larger pdb). >> (Optimisations are on for each project) >> >> >> I may have screwed up the aspnet_regiis command in my frustration. I >> have >> tried the following switches: >> -ir -enable >> -iru -enable >> -i -enable >> -c >> -r (I had to visit my 1.1 asp.net apps in Computer Manager and reset >> them >> back to use 1.1 framework) >> -s path (in my case, w3svc/1/root/copeohs/) >> >> I do have WCF and WPF extensions installed, but these were put on a while >> back with no issue arrising. >> >> I am getting REALLY annoyed that I cannot debug this solution properly - >> it's for my company's main website, so it's got to be a fixable issue. >> >> If necessary I will consider a full VS re-install, but I would prefer to >> avoid this if at all possible. >> >> I am pretty certain it remains a Framework config issue of some sort. >> >> Any constructive help will be gratefully received. >> >> Al >> >> > >
Ok, I've now got a bit more _useful_ info on this problem.
I have now discovered that if I do either a build or rebuild of a sub-project, the debugger will completely fail to launch. IE just hangs around waiting for the home page of the parent project to load and the IDE is indicating the symbols have not been loaded. I found if I close IE at this point and then try to close the IDE (which is failing to respond), this will generate a Windows Crash Report - normal behaviour for this type of application crash. If I then immediately re-load VS at this point and reset the break point (it doesn't get saved when the IDE crashes), the solution loads and runs correctly, and I _can_ then debug the sub-project. It seems like the debugger gets "reset" or something after being corrupted(? - confused certainly) by the recompile. So, as long as I'm OK with tolerating a crash and report for every code change and recompile, things are sweet (heavy irony here if you're not sure!) At least it does allow me to continue working until I can get anyone (Microsoft - hello? anyone reading this?) to respond with a possible solution. Al
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |