I'm pretty far along on this but am going to table the effort for a while.
I've gotten the vs-debug container image working pretty well over in the nforgeio/neonsdk repo and I am able to deploy that as an ephemeral container to the target pod and it appears that the the Visual Debugger is attaching to the process, but pausing the debugger doesn't seem to do anything, even when I have the source solution loaded.
This is going to take some debugging. This was working for the RaspberryDebugger fine, but we were launch the process there, instead of attaching to and existing process. A good place to start would be to see if launching the process works for KubernetesDebugger.
Here's the remaining work items:
I'm pretty far along on this but am going to table the effort for a while.
I've gotten the vs-debug container image working pretty well over in the nforgeio/neonsdk repo and I am able to deploy that as an ephemeral container to the target pod and it appears that the the Visual Debugger is attaching to the process, but pausing the debugger doesn't seem to do anything, even when I have the source solution loaded.
This is going to take some debugging. This was working for the RaspberryDebugger fine, but we were launch the process there, instead of attaching to and existing process. A good place to start would be to see if launching the process works for KubernetesDebugger.
Here's the remaining work items: