paxScript.NET for .NETCF has been released
- From: "Alexander Baranovsky" <ab@xxxxxxxxxxxxxxxx>
- Date: Sun, 10 Apr 2005 07:14:52 +0300
The Microsoft .NET version of the paxScript scripting engine (paxScript.NET)
includes an interpreter of C# language.
The key features of paxScript.NET are:
- paxScript.NET is written in C#. Source code of paxScript.NET is CLS
compilant.
- You can integrate paxScript.NET with your smart device project written in
MS Visual Studio 2003.
- paxScript.NET compiles programs into byte-code. It does not use CodeDOM
and it does not generate a dynamic assembly.
- Separate compilation of modules is allowed. You can combine source code
modules and compiled (binary) modules in your paxScript.NET project.
- C# interpreter (paxCSharp) is based on the ECMA-334 standard. It
supports all C# language features with exception for the unsafe code and
attributes.
- paxCSharp extends standard of C# language with extra features which
simplify the use of C# for scripting needs.
- paxScript.NET is implemented as a .NET component which can be used with
Microsoft Visual Studio .NET, Delphi 8, Delphi 2005 and C# Builder. The
component allows you to embed paxScript.NET interpreter in your WinForms or
ASP.NET application so you can customize and extend the application without
having to recompile it.
- Any public classes, structures, enumerations, arrays, delegates, events
and interfaces of host application can be used in a script.
- You can call script-defined methods from host application.
- Debug capabilities: breakpoints, call stack, watch/evaluate, trace into,
step over etc.
Please visit site
www.paxscript.net
to learn more about paxScript.NET.
Thank you.
Alexander Baranovsky
VIRT Laboratory
www.paxscript.com
www.paxscript.net
.
- Prev by Date: Re: Self-Updating Applications
- Next by Date: Re: Custom Control - InitializeComponent() problem
- Previous by thread: Custom Control - InitializeComponent() problem
- Next by thread: KeybdDriverSetMode?
- Index(es):
Relevant Pages
|
