Hello,
I'm wondering if anyone has any experience with debugging a Microstation or Promis-e add-in over a network? My situation is that my Visual Studio is on a different machine than my Microstation App. At present I do not have the option to install it on the same machine. I can get the program to start over the network but it ignores my command line arguments and when I get it running it won't let me step through my code. I'm currently writing in VB.Net
Any help is appreciated.
Thanks
Dave
Hi Dave,
I have not too many experience with remote debugging, but I assume this is quite standard process. Accordingly to Microsoft documentation you have to install remote debugger to the computer where you application runs (which makes sense, there has to be something that takes care about local debugging / execution of the code). The remote debugger communicates with Visual Studio to provide functionality similar to local debugging.
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Jan,
Thanks for the reply. Yes, I followed the Microsoft documentation, but it seems to deal mostly with debugging an application that you have created, not one that you are just adding on to. Or maybe I'm just not knowledgeable enough about the issue to get it done correctly. I could perform the debug fine when it was on the local machine, so I'm pretty sure I have the command line arguments correct. I was just wondering if there was something specific to Microstation that I'm missing. I think it has something to do with where the symbols are being loaded...
Daverode said:but it seems to deal mostly with debugging an application that you have created, not one that you are just adding on to.
When talking about NET addins or native C++ application for MicroStation, there is no difference between debugging a hosting application itself (e.g. MicroStation) and extending application. They run in the same process as hosting application, so debugging requires to attach to the hosting process. So it's quite the same as normal debugging.
Of course it's necessary to ensure the debugger has an access to debug files (pdb) and it's attached to the process in a proper mode (sometimes it requires to switch off automatic mode to distinguish between NET and native code debugging). But again, it's not specific to debugging MicroStation applications.
Thanks Jan. I'll keep digging.