Scripts Manager is a Windows application designed to manage multiple concurrent scripts. It currently supports Python, PHP, and NodeJS scripts.
Use System.Diagnostics.Process to manage the processes of the scripts, and Sockets to "communicate" with these processes (The implementation is not complete, but the scripts can already invoke the creation of user controls in the administrator)
The solution is ready to run in visual studio 2019 or higher. However, in order to run the examples, you need to add the dependencies and prepare the environment for each one. Below I list the necessary steps to prepare the environments.
The example is done in python 3. Therefore this version of the interpreter is required.
-
The ScriptsManager.py file, required for communication with the manager, imports the following packages:
- _thread
- threading
- functools
- socket
- os
- time
- re
It seems to me that all the packages come with the default python 3+ installation, but if not, you need to get them.
-
It is also necessary that the path of the python interpreter is available in the PATH environment variable. If you don't know how to add it, check this article
-
Make sure that in this path there is an executable called "python.exe", without the quotes. If the interpreter executable is found in your installation path, but it has another name, you must modify the line 6 of this file (just the excutable name not the path).
<process
...
filename="[Python executable name]"
...
/>If you don't have Python 3 installed, you can get it from the Official Page
The ScripsManager.js library uses arrow functions, so a version of NodeJs with EcmaScript6 support is required. I don't think there is any supported version that doesn't use it, so there shouldn't be any problems. Besides, the only two libraries that are imported are net and http, both included in every NodeJs version. So a default NodeJs installation should suffice.
As with python, it is also necessary that the nodejs path is available in the PATH environment variable. And in this path, the interpreter must be called "node.exe", without the quotes. If not, you must modify line 6 of this another file, just like you did with the one in python.
<process
...
filename="[Node executable name]"
...
/>If you don't have NodeJS installed, you can get it from the Official Page
Soon I will be updating this section...