cannot debug "with 'Just My Code' setting enabled" ??

  • Thread starter Thread starter Tim Hanson
  • Start date Start date
T

Tim Hanson

hi,

i have a solution in whidbey that began as a class library project.
for testing purposes I added a console application project. when I try
to debug the console application I get a dialog box that reads:

one or more projects in the solution do not contain user code
and cannot be debugged with 'Just My Code' setting enabled.
Make sure that all projects in your solution are configured
to be built in Debug mode.

the message is very specific, but I don't find either the "Debug mode"
setting nor a "Just My Code" setting.

cheers,

Tim Hanson
 
one or more projects in the solution do not contain user code
and cannot be debugged with 'Just My Code' setting enabled.
Make sure that all projects in your solution are configured
to be built in Debug mode.
Click to expand...

OK, there are at least two places where one needs to select "Debug"
apparently. One was staring me in the face and I ignored it: Next to
the Start Button is a pull-down in which one selects from (Debug,
Release, Configuration Manager) -- at least in my default settings.
The other place is under Project Properties / Build / Advanced / Debug
Info. Apparently all these need to be set to "Debug" in both projects
(a total of 4 places) for things to work.

Alas, i still can't debug into the Reference.cs code that the "Add Web
Reference" mechanism generates automagically (even when I comment out
the line:

[System.Diagnostics.DebuggerStepThroughAttribute()]
ahead of my class).

So I'd still be mucho grateful for hints here. Can this be done? I'd
probably even like to debug into the Invoke() method, since there
seems to be XML parse error happening at or below that point that I'd
like to get my eyes around.

Cheers,

Tim Hanson
 
Are you getting an error? Define "can't debug"

Jeff

Tim Hanson said:
one or more projects in the solution do not contain user code
and cannot be debugged with 'Just My Code' setting enabled.
Make sure that all projects in your solution are configured
to be built in Debug mode.
Click to expand...

OK, there are at least two places where one needs to select "Debug"
apparently. One was staring me in the face and I ignored it: Next to
the Start Button is a pull-down in which one selects from (Debug,
Release, Configuration Manager) -- at least in my default settings.
The other place is under Project Properties / Build / Advanced / Debug
Info. Apparently all these need to be set to "Debug" in both projects
(a total of 4 places) for things to work.

Alas, i still can't debug into the Reference.cs code that the "Add Web
Reference" mechanism generates automagically (even when I comment out
the line:

[System.Diagnostics.DebuggerStepThroughAttribute()]
ahead of my class).

So I'd still be mucho grateful for hints here. Can this be done? I'd
probably even like to debug into the Invoke() method, since there
seems to be XML parse error happening at or below that point that I'd
like to get my eyes around.

Cheers,

Tim Hanson
Click to expand...
 
Are you getting an error? Define "can't debug"
Click to expand...

i simply can't step into methods defined in my proxy (Reference.cs). i
can step in the rest of my code. btw, my impression is that i won't be
able to solve my problem by debugging in the Reference.cs code -- the
failure to parse the SOAP result envelope is happening at a deeper
level (inside invoke() perhaps).

--Tim
 
Back
Top