There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
It should be possible to create a ScriptRuntime without specifying any languages
In the default configuration, ScriptRuntime.CreateFromConfiguration() throws an exception tht no engines have been configured. This is a counter-intuitive place for the error, many simple hosting applicatoins will want to simply declare a default ScriptRuntime
as a initialized (possibly static) memeber, and this is hampered by having to wrap it in error handling.
If and when the application attempts to create a ScriptEngine is the time to raise any errors about availablility of a specific engine. Even if there are no engines, other features on the ScriptRuntime might be useful.
The built-in "invariant" language, which is always available to a ScriptRuntime through the Operations property, should count as a language when creating a ScriptRuntime.
The TestDefaultRuntime() function in the attached unit test module demonstrates the problem.