P
Passiday
Hello,
I am looking for a stable solution for my dotNET projects, that would
allow to add scripting capabilities to my apps. The idea is to allow
application users to write their own scripts that impact the behaviour
of the application. It totally makes sense to offer the scripting with
well established standard scripting language, like ECMA script (ie
standard on what JavaScript, JScript and Adobe ActionScript are
based).
The solution should have the following features:
1) Script error reporting -- it there is a syntax error in the script,
there must be a way to get appropriate error information to tell user
so that he can fix his macro
2) Ability to access specifically exposed application objects from the
scripting scope
3) It would be great if the solution could be used also from
environments like ASP.NET, ie, light enough to allow use from web
applications that spawn several simultaneous sessions.
4) JIT compiling of the script is Ok, if it is transapent enough not
to mess up things if there's some runtime error and application can
not provide decent error context to the user.
In my search for solution, I contemplated using some web browser
control -- feed it with script and let it execute inside the control,
but it feels kind of heavy (especially if I'd like to use it in
ASP.NET), given I am looking only for scripting sandbox.
Thanks for any hints!
Passiday
I am looking for a stable solution for my dotNET projects, that would
allow to add scripting capabilities to my apps. The idea is to allow
application users to write their own scripts that impact the behaviour
of the application. It totally makes sense to offer the scripting with
well established standard scripting language, like ECMA script (ie
standard on what JavaScript, JScript and Adobe ActionScript are
based).
The solution should have the following features:
1) Script error reporting -- it there is a syntax error in the script,
there must be a way to get appropriate error information to tell user
so that he can fix his macro
2) Ability to access specifically exposed application objects from the
scripting scope
3) It would be great if the solution could be used also from
environments like ASP.NET, ie, light enough to allow use from web
applications that spawn several simultaneous sessions.
4) JIT compiling of the script is Ok, if it is transapent enough not
to mess up things if there's some runtime error and application can
not provide decent error context to the user.
In my search for solution, I contemplated using some web browser
control -- feed it with script and let it execute inside the control,
but it feels kind of heavy (especially if I'd like to use it in
ASP.NET), given I am looking only for scripting sandbox.
Thanks for any hints!
Passiday