Re: Office or InDesign breaks VS 2005 debugging?

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


"Alec MacLean" <alec.maclean@xxxxxxxxxxxxxxxxxxx> wrote in message
news:%23K6fFOY3HHA.5740@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxx> wrote in message
news:emSDUr22HHA.212@xxxxxxxxxxxxxxxxxxxxxxx
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






.