Re: VS 2005 (NO sp1)

Tech-Archive recommends: Fix windows errors by optimizing your registry



Do the following:

1. Set a breakpoint in your Web service method
2. On the Debug menu, click Attach to Process
3. Attach the debugger to inetinfo.exe on the desktop
4. Call the Web service from the device

--
Neil Cowburn
Principal Partner
OpenNETCF Consulting, LLC.

Managed Code in the Embedded World

http://www.opennetcf.com/
http://www.smartdeviceframework.com/


"VJ" <nonewsaddress@xxxxxxxxx> wrote in message news:%23BVoXEmZHHA.2320@xxxxxxxxxxxxxxxxxxxxxxx
when running my source code from the emulator or a device,

I am unable to debug into a web service code that is running on my computer. I have complied, updated reference, added/removed reference.

I am just able to debug the app code, not the webservice code.

Anything special needs to be done?

VJ


.



Relevant Pages

  • Re: VS 2005 (NO sp1)
    ... You can attach the debugger to both the device app and the web service at the same time. ... "Neil Cowburn" wrote in message ... On the Debug menu, ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Debugging a WebService
    ... Is it possible to automate this so we don't need to attach every time we ... >> Is there a secret trick to debugging a Web service? ... >> I compile my web service and test app in debug mode. ...
    (microsoft.public.dotnet.framework.webservices)
  • RE: Debugging errors (from VS - I cant even start debugging)
    ... It seems you are trying to debug a web service. ... The error is because you do not have access to attach to the process. ... Microsoft CDO for Windows 2000 ...
    (microsoft.public.vsnet.debugging)
  • Re: Cant write to folder
    ... To debug without running via studio, click Tools / Attach to Process. ... ensure in the attach to block that SQL Server is not selected. ... inpFileUpNIIN.PostedFile.SaveAs(strBaseDir & strFileName) ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Attach to Process
    ... Actually my question has to do with how to debug and step through managed CLR code applications that are running by themselves - not in visual studio debugger. ... If you are using a wizard, you cannot attach after you start the wizard, as some of the context is not available to the debugger. ...
    (microsoft.public.dotnet.framework.aspnet)