Why JIT Debugger Doesn't Work on Particular Project?

[Chuck Ritzke]

Hi,

I've been using VS for a number of projects and the debugger has worked as
advertised until now. I have a desktop solution with three projects, two of
which are class modules. For some reason, in only one of them, the JIT
debugger doesn't seem to be working. (At least I asssume this is a JIT
debugger issue.)

Anyways, in all my other projects an error causes the pop-up window with the
break button option that breaks at the line with the problem. For some
reason, any error in this one particular project just pops-up the window
that says the JIT debugger needs to be enabled. I tried setting JITDebugger
to True in the Machine.config file per the window instructions, but that
didn't help (and I wondered why I'd need to anyway because the debugger
works everywhere else). It also talks about changing this setting in the
app's config file, but the only config files I see are those in the ASP.NET
projects.

Does anyone know where I should look to see why the JITDebugger window
doesn't pop-up in a particular application? The only different thing that I
can think of that I did in this project was to include a reference to a COM
object. But even when I removed the reference, still no debug window.

Any help will be appreciated. Thanks in advance,
Chuck

 

[Andy Gaskell]

With your solution open in VS.NET right click the solution in the Solution
Explorer and click on Configuration Manager. It's probably on Release,
change it to Debug. Click Close and run your application again.

 

[Leon Lambert]

Could it be some attribute on the classes? I know this attribute causes
the debugger to step over any method withing this class. I had to
comment them out so i could step in with the debugger.
[System.Diagnostics.DebuggerStepThrough()]
I got this from an auto-generated class from using one of the .Net tools.

Hope this helps.
Leon Lambert

 

[Chuck Ritzke]

Thanks, but I forgot to mention I did check that.

Chuck

 

[Chuck Ritzke]

Thanks. Sorry to be dense (I'm fairly newbie)... I don't think
System.Diagnostics.DebuggerStepThrough is the problem, but I don't know for
sure as I don't know what these attributes do exactly.

I searched thru my projects and the only place I see that is in my form
classes, but the problem class is just a generic "no-form" class where I do
calculations and call it from a form class. The form class debugs fine and
the other non-form class it calls works fine. I don't see any system
generated code at all in my non-form classes. And I can't see anything
different in any settings that I can find.

Unless somebody has something obvious, I guess my only other options is to
rebuild the class piece by piece and see when the debugger stops working.

Thanks,
Chuck

Chuck

Could it be some attribute on the classes? I know this attribute causes
the debugger to step over any method withing this class. I had to
comment them out so i could step in with the debugger.
[System.Diagnostics.DebuggerStepThrough()]
I got this from an auto-generated class from using one of the .Net tools.

Hope this helps.
Leon Lambert

Hi,

I've been using VS for a number of projects and the debugger has worked as
advertised until now. I have a desktop solution with three projects, two of
which are class modules. For some reason, in only one of them, the JIT
debugger doesn't seem to be working. (At least I asssume this is a JIT
debugger issue.)

Anyways, in all my other projects an error causes the pop-up window with the
break button option that breaks at the line with the problem. For some
reason, any error in this one particular project just pops-up the window
that says the JIT debugger needs to be enabled. I tried setting JITDebugger
to True in the Machine.config file per the window instructions, but that
didn't help (and I wondered why I'd need to anyway because the debugger
works everywhere else). It also talks about changing this setting in the
app's config file, but the only config files I see are those in the ASP.NET
projects.

Does anyone know where I should look to see why the JITDebugger window
doesn't pop-up in a particular application? The only different thing that I
can think of that I did in this project was to include a reference to a COM
object. But even when I removed the reference, still no debug window.

Any help will be appreciated. Thanks in advance,
Chuck