How do I get started designing and implementing a script interface for my .NET application?
- by Peter Mortensen
How do I get started designing and implementing a script interface for my .NET application?
There is VSTA (the .NET equivalent of VBA for COM), but as far as I understand I would have to pay a license fee for every installation of my application. It is an open source
application so this will not work.
There is also e.g. the embedding of interpreters (IronPython?), but I don't understand how this would allow exposing an "object model" (see below) to external (or internal) scripts.
What is the scripting interface story in .NET? Is it somehow trivial in .NET to do this?
Background:
I have once designed and implemented a fairly involved script interface for a Macintosh application for acquisition and analysis of data from a mass spectrometer (Mac OS, System 7) and later a COM interface for a Windows application.
Both were designed with an "object model" and classes (that can have properties). These are overloaded words, but
in a scripting interface context object model is essentially a containment hiarchy of
objects of specific classes. Classes have properties and lists of contained objects.
E.g. like in the COM interfaces exposed in Microsoft Office applications, where the application object can be used to add to its list of documents (with the side effect of creating the GUI representation of a document).
External scripts can create new objects in a container and navigate through the content of the hiarchy at any given time. In the Macintosh case scripts could be written in e.g. AppleScript or Frontier.
On the Macintosh the implementation of a scripting interface was very complicated.
Support for it in Metroworks' C++ class library (the name escapes me right now) made it much simpler.
