M
Mike Labosh
I have developed a Service Application that kicks off batch jobs written by
other developers. It works great on my machine, and works great on another
developer's machine. On a third machine, when debugging the batch job that
the service kicked off, any line of code "stepped into" (F11) opens it in
the Disassembly Window, with the VB source listed as comments.
I thought that perhaps the debug symbols may have become out of sync with
the Service's binaries, so I just did a fresh build of the service and one
DLL that it uses. We then re-deployed the freshly rebuilt service, DLL, and
both .pdb files, but any attempt to use the debugger on the launched batch
still gives us the disassembly window on the launched batch's code (i.e.,
not the service's code)
Any other things we can try so we can use the debugger without the
disassembly window?
other developers. It works great on my machine, and works great on another
developer's machine. On a third machine, when debugging the batch job that
the service kicked off, any line of code "stepped into" (F11) opens it in
the Disassembly Window, with the VB source listed as comments.
I thought that perhaps the debug symbols may have become out of sync with
the Service's binaries, so I just did a fresh build of the service and one
DLL that it uses. We then re-deployed the freshly rebuilt service, DLL, and
both .pdb files, but any attempt to use the debugger on the launched batch
still gives us the disassembly window on the launched batch's code (i.e.,
not the service's code)
Any other things we can try so we can use the debugger without the
disassembly window?