Hi,
Marc Gravell wrote:
> You can debug cross-host calls using IIS; setup the site / virtual in
> IIS using the project root as the directory home (i.e. so that your
> pages work in IIS like normal). Note the root uri to your IIS project
> (e.g. "browse" in IIS and cut/paste the folder part (exclusing the
> page).
> In VS, use the properties page to set a custom server ("Start Options"
> -> "Server"; "Use cutom server" & "Base URL", and set the uri you
> noted (i.e. the IIS uri to the project root). Also set "Start action"
> to "Don't open a page...".
>
> Now set some breakpoints and hit play.
>
> What *should* happen is that VS will compile the app, and attach the
> debugger to the IIS process. Your phone should be able to call into
> IIS as normal, but it should get intercepted and hit the break-points.
>
> Marc
Alternatively, you can simply attach the VS debugger to the ASPNET
process using the "Debug / Attach to process" menu. This is usually
faster than starting the service in debug mode.
Greetings,
Laurent
--
Laurent Bugnion [MVP ASP.NET]
Software engineering, Blog:
http://www.galasoft-LB.ch
PhotoAlbum:
http://www.galasoft-LB.ch/pictures
Support children in Calcutta:
http://www.calcutta-espoir.ch