The Dot Net Call is expecting something that is executable. this does not mean everything has to be a exe, but it must be executable. For example Batch programs work. Remember the script must be in the Script folder of NC_NEt. And you need to enable NC_NEt to accept arguments after the command name.
In summary wrap your call to the script inside a .bat if you cannot call it directly.
tony
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As you stated it is not good add the perl binary to the Script folder since it would expose a security hole.
I think the most secure way of using the Scripts is to use executables or Bat's that do not accept arguments. This allows you to disable the donotblaimNC_NEt option. when the donto blaim option is off and since the command prevents .. in the path, It should be secure from Malicous usage.
Doesn't the Bat always exit OK? Do you recall the way to capture the exit code?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
im looking in the new Script funktion. It looks fine but i ahve a Problem with Perlscript.
It sems to me, that only Executable programs are allowd? is this right?
If its right does anybody have ha solution vor Perlscript?
Thanks in advance,
Mark
The Dot Net Call is expecting something that is executable. this does not mean everything has to be a exe, but it must be executable. For example Batch programs work. Remember the script must be in the Script folder of NC_NEt. And you need to enable NC_NEt to accept arguments after the command name.
In summary wrap your call to the script inside a .bat if you cannot call it directly.
tony
Ok, then i will look how i get the Exitcodes and Output throu the .bat.
Or just write somthing in .net.
Mark
Ok i found a Solution!
Copy the Perl-Binary in the script Path and aktive the Do_not_Blame... option
After that you can give the Perlscript as an option to perl.exe.
Only problem it will be problem that you can run any code yoy want with the commandline option of Perl.
Mark
Sometimes i think too complicatet, just write a .bat and add in the first line @echo off and then the Perl commandline.
Mark
As you stated it is not good add the perl binary to the Script folder since it would expose a security hole.
I think the most secure way of using the Scripts is to use executables or Bat's that do not accept arguments. This allows you to disable the donotblaimNC_NEt option. when the donto blaim option is off and since the command prevents .. in the path, It should be secure from Malicous usage.
Doesn't the Bat always exit OK? Do you recall the way to capture the exit code?