Some variables are on the deployed machine and some will be ont he server itself.  The one that you are looking at above should be on the server.  In order to take advantage of that variable, the job will need to be run "Locally on the Deployment Server".

i managed to work with those variables on deployed machine

by using batch file i wrote the variable value to txt file...

so why i cant use them in .Net code ?

The way DS performs its replacement of these special variables like %JOBNAME% is to parse the scripts which are directly passed through the engine before executing.

Compiled code (like .NET) cannot have 'token replacement' function performed on it, as in order to do so the engine would have to decompile the code, replace the tokens and recompile before executing.

The way I get around this is to have my compiled code accept arguments, and have this executed by DS. For example,

 call mycode.exe %JOBNAME% %COMPNAME% 

Kind Regards,
Ian./

First, thanks for the reason explanation !

what i actually did is to wrote all relevant variables to text file (execution of batch file) and then i'm reading it from the compiled .Net, I have many of argument to pass :)

Or set the variables as environment variables in your embedded script before calling your script or executable:

set JOBNAME=%JOBNAME%
set COMPNAME=%NODEFULL%

cscript myscript.vbs

Note that these System tokens are always in uppercase.

These system tokens are replaced in the first script (in this case the embedded script) and are replaced not only with "Locally on the deployment server" but also on normal tasks.