Debugging a IIS hosted WCF Service

Using .NET3, have there been any changes in terms of being able to debug a
IIS hosted WCF service, i.e. stepping into service or setting breakpoints in
the service. The only way we have been able to debug WCF services in IIS
with the released .NET3, is by attaching the debugger to the aspnet_wp.exe
process manually and then setting breakpoints or stepping into service
methods. If anyone can shed some light on/debug this it would be much
appreciated as we have numerous dev teams struggling with the
development/debugging process.

Hello, wschaub!

IMO there are several ways how to enhance debugging.
- create ordinary ASP.NET project and add WCF stuff there
- create console application that will host your WCF services and
do the debugging using that console app
- insert into service method a call to Debugger.Lauch() this will trigger
debugger window

I'd recommend using separate host for debugging ( console app )

You wrote on Tue, 19 Dec 2006 14:11:49 +0200:

w> Using .NET3, have there been any changes in terms of being able to
w> debug a
w> IIS hosted WCF service, i.e. stepping into service or setting
w> breakpoints in
w> the service. The only way we have been able to debug WCF services in
w> IIS
w> with the released .NET3, is by attaching the debugger to the
w> aspnet_wp.exe
w> process manually and then setting breakpoints or stepping into
w> service
w> methods. If anyone can shed some light on/debug this it would be much
w> appreciated as we have numerous dev teams struggling with the
w> development/debugging process.



With best regards, Vadym Stetsyak.
Blog: http://vadmyst.blogspot.com

Thanks ... I agree with your recommendation using a seperate host.

"Vadym Stetsyak" <vadym_s@ukr.net> wrote in message
news:OslIKv3IHHA.1240@TK2MSFTNGP03.phx.gbl...
> Hello, wschaub!
>
> IMO there are several ways how to enhance debugging.
> - create ordinary ASP.NET project and add WCF stuff there
> - create console application that will host your WCF services and
> do the debugging using that console app
> - insert into service method a call to Debugger.Lauch() this will trigger
> debugger window
>
> I'd recommend using separate host for debugging ( console app )
>
> You wrote on Tue, 19 Dec 2006 14:11:49 +0200:
>
> w> Using .NET3, have there been any changes in terms of being able to
> w> debug a
> w> IIS hosted WCF service, i.e. stepping into service or setting
> w> breakpoints in
> w> the service. The only way we have been able to debug WCF services in
> w> IIS
> w> with the released .NET3, is by attaching the debugger to the
> w> aspnet_wp.exe
> w> process manually and then setting breakpoints or stepping into
> w> service
> w> methods. If anyone can shed some light on/debug this it would be much
> w> appreciated as we have numerous dev teams struggling with the
> w> development/debugging process.
>
>
>
> With best regards, Vadym Stetsyak.
> Blog: http://vadmyst.blogspot.com
>

Thus wrote wschaub,

> Using .NET3, have there been any changes in terms of being able to
> debug a IIS hosted WCF service, i.e. stepping into service or setting
> breakpoints in the service. The only way we have been able to debug
> WCF services in IIS with the released .NET3, is by attaching the
> debugger to the aspnet_wp.exe process manually and then setting
> breakpoints or stepping into service methods. If anyone can shed some
> light on/debug this it would be much appreciated as we have numerous
> dev teams struggling with the development/debugging process.

Debugging a IIS hosted service works like debugging an ASP.NET web site.
The only thing you want to do differently is to set your web site's startup
mode to "Don't open a web page" (unless your site hosts both ASP.NET pages
and WCF services) and you're good to go.

Cheers,
--
Joerg Jooss
news-reply@joergjooss.de