We have seen a lot of customers reporting the fact that sometimes the breakpoints are not getting hit and the connection to the device is lost popping the error dialog "The connection to the device is lost ...", while debugging a NET CF V2 application...

Unable to start debugging: How to attack the issue. I am the owner for the device debugging efforts from the Visual Studio for Devices team. If you are hitting "Unable to start debugging" or any similar issue in F5 experience, please feel free to convey...

Let me also add that the below issue is very sporadic and not a common one.

We are hearing some reports of VSD debugger popping up "Unable to start debugging" dialog sometimes on customer boxes trying to debug with Win CE 5.0 device. We are suspecting this to be a issue with side by side installations_and_usages of PB and VS...

In VS 2005, VSD does not support Seamless "Mixed mode" debugging a.k.a interop debugging. However this is being actively considered for future releases of VS and .NET CF. However if you need to debug a solution that includes both Managed and Native...

In this blog, I shall touch upon two important and cool features in VS 2005 device debugging. Feature1: Attaching to NET CF V2 process VS 2005 allows for attaching to a NET CF V2 process running on the device/emulator. This is disabled by default...

Visual Studio 2005 debugger component cpde.dll (debug engine) hosts components which implement ICorDebug, the managed debugging API. (For details refer ICorDebug blogs at http://blogs.msdn.com/jmstall ). This API is implemented in mscordbi.dll for...

This is my first official blogging experience and that explains the topic. Let me introduce myself before getting into anything techie. I am Srinivas N working as a developer for the Visual Studio for Devices (VSD) team where I currently drive the...