Closed ghost closed 10 years ago
In addition to commit message: Although .NET remoting is bit ancient technology it works ok for this case. I even think to make possible to run it in process via factory during dev debugging. So debugging process will be less painful.
The type provider uses a proxy process to host Python for .NET (and thus python27.dll) at compile time. This is to isolate the Python for .NET from Visual Studio etc, which seems like a very good idea, e.g. to avoid a 32/64-bit dependency problem among other things.
Make the communication to the proxy robust. It uses .NET remoting right now. Is this robust enough? It also uses WaitForInputIdle - is this robust enough?