Consider open sourcing JSProvider.dll
glenrgordon opened this issue · 5 comments
I for one am interested in writing a Python provider and/or writing a JSProvider that uses the V8 engine. Both of these in pursuit of better understanding the exposed interfaces. Being able to see how things are done in the existing JSProvider would be of tremendous help and a productivity boost. The documentation is great, but it doesn't bring complex concepts together nearly as well as debugging through existing C++ code.
@wmessmer-msft started a Python provider a couple years ago, maybe he can share that?
We have a JSProvider built on V8 and it should be available very soon. You might already have it, but it's not enabled by default.
Good news about the V8 JS provider. How do I know if I already have it, and if not is there a way to get it? Would be great to see the start of a Python provider though I think I have since figured out a bit more about how to make such a thing.
0:000> .veighton
Switching to the new V8 JsProvider.
You may find it useful to turn on redirection to the V8 JsProvider permanently:
.settings set Extensions.EnableRedirectToV8JsProvider=true
.settings save
It will look for JsProvider.dll inside winext\v8\JSProvider.dll which I did not see in downloading the latest Debugging Tools.
@wmessmer-msft Bump on the Python provider. And while not analogous directly, would it be possible to get a C# port of DbgModelClientEx.h? A C# provider in general would be very very welcome.