|
|
You're in the
visual studio .net debugging
group:Config corruption?
visual studio .net debugging:
I have a Web Application Project solution which has multiple sub-projects that are configured to use nested master pages. I have now got a problem with trying to debug (step-through) the solution. The Visual Studio IDE freezes (non-responsive) and the IE browser just spins waiting for content to load, which no longer happens. I then either have to close VS (and submit an application crash report), or use Task Manager to kill off the aspnet_wp worker process (which I need to repeat at least 4 times before the VS-IDE returns to normal). I know the compiler is OK: If I just build the project being edited and manually browse to the corresponding localhost sub-folder of the site it corresponds with, the changes are being compiled and implemented correctly - but of course I can't debug problems if they occur. I have tested the scenario of creating a fresh solution, then creating a copy of the root project and one sub-project in a temp area and recompiling and setting a breakpoint. This all works as expected, allowing me to get into debug mode and access breakpopints in the sub-project when required. So this should indicate VS itself isn't broken. I therefore wonder if there is some sort of corruption in one or more of the config files that Visual Studio relies on for this particular solution. Can anyone provide guidance that might help me correct this? I could go down the route of re-creating all the sub projects and copying the existing files over from the original project to the new version, but I wondered if there was a quicker technique that would allow me to correct the problem in the original solution directories? For background info, just in case it's pertinent:- The original solution has the root project (where the masterpages are kept), then a total of 17 sub-projects. This solution set up is configured as per the guidelines provided at: http://blogs.msdn.com/webdevtools/archive/2006/07/01/652986.aspx Thanks for any input. Al
This morning I followed up on my earlier attempt to "clean" the solution
files completely by copying all content to a holding area, then recreating the entire solution again, only pasting back in the content files (aspx pages, images, flash, etc) from the holding area, then adding the required references and resources to the individual projects settings and the root web.config where required. This meant the project and solution files were all "as new". I then recompiled each project (right-click -> Build) to generate the DLL's in the root Bin folder. I then set a breakpoint in one sub-project I'm currently working on. The problem still manifested itself, with no code changes occuring. I then "removed" all except three projects from the solution and tried again. This time it worked - all remaining PDB files seem to load. I then "added existing project" to the solution, adding each of the removed projects one at a time, then running (F5) after each re-attached project (no code changing or recompilation required). Each time it worked as it should, allowing me to access the sub-project's breakpoint. This was without any code changes occuring, so the associated PDB file has not changed. I then made a very simple change (add a simple string var declaration) in the sub-project in order to force a change to that projects debug symbols file, and then re-ran the solution. Again I got the problem of the studio going unresponsive and IE just waiting for content to load (which won't happen). I then found that If I removed and re-added just one of the sub-projects (didn't matter which one) AFTER the sub-project recompilation, then everthing would operate again OK. It is important to re-add the existing project - just removing it doesn't seem to force VS to reload the new PDB for some reason, whereas the remove + add process does. If anyone can shed light on this behaviour by VS I'd be mighty grateful! Thanks Al [quoted text, click to view] "Alec MacLean" <alec.maclean@NO-SPAM-copeohs.com> wrote in message news:OLfb6hW8HHA.1484@TK2MSFTNGP06.phx.gbl... > Hi, > > I have a Web Application Project solution which has multiple sub-projects > that are configured to use nested master pages. > > I have now got a problem with trying to debug (step-through) the solution. > > The Visual Studio IDE freezes (non-responsive) and the IE browser just > spins waiting for content to load, which no longer happens. I then either > have to close VS (and submit an application crash report), or use Task > Manager to kill off the aspnet_wp worker process (which I need to repeat > at least 4 times before the VS-IDE returns to normal). > > I know the compiler is OK: If I just build the project being edited and > manually browse to the corresponding localhost sub-folder of the site it > corresponds with, the changes are being compiled and implemented > correctly - but of course I can't debug problems if they occur. > > I have tested the scenario of creating a fresh solution, then creating a > copy of the root project and one sub-project in a temp area and > recompiling and setting a breakpoint. This all works as expected, > allowing me to get into debug mode and access breakpopints in the > sub-project when required. So this should indicate VS itself isn't broken. > > I therefore wonder if there is some sort of corruption in one or more of > the config files that Visual Studio relies on for this particular > solution. > > Can anyone provide guidance that might help me correct this? > > I could go down the route of re-creating all the sub projects and copying > the existing files over from the original project to the new version, but > I wondered if there was a quicker technique that would allow me to correct > the problem in the original solution directories? > > For background info, just in case it's pertinent:- > > The original solution has the root project (where the masterpages are > kept), then a total of 17 sub-projects. > This solution set up is configured as per the guidelines provided at: > http://blogs.msdn.com/webdevtools/archive/2006/07/01/652986.aspx > > > Thanks for any input. > > Al >
Another day and another discovery....
After finding on Monday that removing and reloading a sub-project forced the use of the updated PDB files, I thought I had a suitable work-around. then yesterday on one build iteration this approach also failed. (Possibly just due to my impatience and being too quick on the clicking). I then found that by using Task Manager to kill off the aspnet_wp.exe (XP's localhost asp.net worker process) before running the solution, this seemed to resolve the issue. I'm hoping I don't now find that this stops helping after a few tries. I'm starting to get paranoid - I'm sure someone is now changing the rules behind the scenes - each time I find a solution it gets plugged to break at some other point! Finger in the dam.... Al [quoted text, click to view] "Alec MacLean" <alec.maclean@NO-SPAM-copeohs.com> wrote in message news:usRmF258HHA.1204@TK2MSFTNGP03.phx.gbl... > This morning I followed up on my earlier attempt to "clean" the solution > files completely by copying all content to a holding area, then recreating > the entire solution again, only pasting back in the content files (aspx > pages, images, flash, etc) from the holding area, then adding the required > references and resources to the individual projects settings and the root > web.config where required. > > This meant the project and solution files were all "as new". > > I then recompiled each project (right-click -> Build) to generate the > DLL's in the root Bin folder. > > I then set a breakpoint in one sub-project I'm currently working on. The > problem still manifested itself, with no code changes occuring. > > I then "removed" all except three projects from the solution and tried > again. This time it worked - all remaining PDB files seem to load. > > I then "added existing project" to the solution, adding each of the > removed projects one at a time, then running (F5) after each re-attached > project (no code changing or recompilation required). Each time it worked > as it should, allowing me to access the sub-project's breakpoint. This > was without any code changes occuring, so the associated PDB file has not > changed. > > I then made a very simple change (add a simple string var declaration) in > the sub-project in order to force a change to that projects debug symbols > file, and then re-ran the solution. Again I got the problem of the studio > going unresponsive and IE just waiting for content to load (which won't > happen). > > I then found that If I removed and re-added just one of the sub-projects > (didn't matter which one) AFTER the sub-project recompilation, then > everthing would operate again OK. It is important to re-add the existing > project - just removing it doesn't seem to force VS to reload the new PDB > for some reason, whereas the remove + add process does. > > If anyone can shed light on this behaviour by VS I'd be mighty grateful! > > Thanks > > Al > > > > "Alec MacLean" <alec.maclean@NO-SPAM-copeohs.com> wrote in message > news:OLfb6hW8HHA.1484@TK2MSFTNGP06.phx.gbl... >> Hi, >> >> I have a Web Application Project solution which has multiple sub-projects >> that are configured to use nested master pages. >> >> I have now got a problem with trying to debug (step-through) the >> solution. >> >> The Visual Studio IDE freezes (non-responsive) and the IE browser just >> spins waiting for content to load, which no longer happens. I then >> either have to close VS (and submit an application crash report), or use >> Task Manager to kill off the aspnet_wp worker process (which I need to >> repeat at least 4 times before the VS-IDE returns to normal). >> >> I know the compiler is OK: If I just build the project being edited and >> manually browse to the corresponding localhost sub-folder of the site it >> corresponds with, the changes are being compiled and implemented >> correctly - but of course I can't debug problems if they occur. >> >> I have tested the scenario of creating a fresh solution, then creating a >> copy of the root project and one sub-project in a temp area and >> recompiling and setting a breakpoint. This all works as expected, >> allowing me to get into debug mode and access breakpopints in the >> sub-project when required. So this should indicate VS itself isn't >> broken. >> >> I therefore wonder if there is some sort of corruption in one or more of >> the config files that Visual Studio relies on for this particular >> solution. >> >> Can anyone provide guidance that might help me correct this? >> >> I could go down the route of re-creating all the sub projects and copying >> the existing files over from the original project to the new version, but >> I wondered if there was a quicker technique that would allow me to >> correct the problem in the original solution directories? >> >> For background info, just in case it's pertinent:- >> >> The original solution has the root project (where the masterpages are >> kept), then a total of 17 sub-projects. >> This solution set up is configured as per the guidelines provided at: >> http://blogs.msdn.com/webdevtools/archive/2006/07/01/652986.aspx >> >> >> Thanks for any input. >> >> 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 |