You can create an ASP.NET form in a separate ASP application that will take DLL paths for registering and scheduling a batch file (with job ID, timestamp and serial number in the file name to identify it) to run with the Windows scheduler at the beginning of the next minutes, displaying the result of registration in a text file of the result. And which deletes old time files and result files. And which supports status request / text return / return for previous jobs. And call this ASP interface from the command line over the network using a C # script. Ugh. Actually a really terrible shaky shaky decision and there may be more work than the application (itself).
Borland ++ , , , . .
, .