Debug deployed extension

I have a custom data extension I'm working on. I can debug this when the
report using it is being designed by adding a line in the code for the
extension like:
System.Diagnostics.Debugger.Break();
When I then run the report in design mode I'll get a choice of debuggers and
I can then open one and debug the extension.
However, if I then deploy the report (with
System.Diagnostics.Debugger.Break(); still in the code) and run the report
from say Report Manager or just via URL I don't get the choice to debug and
the report just seems to hang. Right now this is all just on my one
development PC (when I'm deploying I'm actually just deploying it to my
development machines version of reporting services).
Any thoughts on the problem or how to debug a deployed custom extension?
Cheers!Hi Cayman:
You might have to use Debugger.Launch if the debugger is not already
attached (which you can check with the Debugger.IsAttached property).
Is this in a custom assembly? Let me know if this works, I might check
it out later this evening. I imagine there still might be a problem
since the reporting service has it's own desktop / winsation where GUI
elements appear that are invisible to the logged in user. An old
school solution to this problem is to run as Local System and check
"Allow service to interact with desktop", but running as Local System
is risky, and allowing a service to interact with the desktop is even
riskier, because a malicious program could start pumping Windows
messages into the service.
--
Scott
http://www.OdeToCode.com/blogs/scott/
On Thu, 11 Nov 2004 07:00:06 -0800, "Cayman Visitor" <Cayman
Visitor@.discussions.microsoft.com> wrote:
>I have a custom data extension I'm working on. I can debug this when the
>report using it is being designed by adding a line in the code for the
>extension like:
>System.Diagnostics.Debugger.Break();
>When I then run the report in design mode I'll get a choice of debuggers and
>I can then open one and debug the extension.
>However, if I then deploy the report (with
>System.Diagnostics.Debugger.Break(); still in the code) and run the report
>from say Report Manager or just via URL I don't get the choice to debug and
>the report just seems to hang. Right now this is all just on my one
>development PC (when I'm deploying I'm actually just deploying it to my
>development machines version of reporting services).
>Any thoughts on the problem or how to debug a deployed custom extension?
>Cheers!