Feature Request - C# scripting

Now that Roslyn is stable, please can we add C# as a scripting language?
I would guess that the majority of your users that use the scripting in Opus would much prefer C# to JavaScript or VB.

I know I's use scripting more if C# was available.

Thanks...

You're welcome to develop a C# scripting engine for use with DO.
DO is a scripting host that use scripting engines available through windows, like JScript and VBScript.

More information here.

That's very helpful of you, to suggest that I write a C# scripting engine myself.
My point was to raise it as a feature request, that many DOpus users would appreciate if it was bundled with DOpus.

If it already has a scripting engine, and it is installed on your computer then
you can enter the name of the engine into DO CLI's "script interpreter" field to make
DO use that scripting engine to execute the code.
If the file's file extension is tied to a properly defined scripting engine then DO
will use that one to execute the script if the file is placed into "\script addins".

Python, Perl, etc has been used (somewhat) successfully with DO.
Some engines may need some fiddling to make DO and other scripting hosts recognize
then as scripting engines (such as running a batch-file, doing some registry editing, or similar).

Roslyn doesn't seem to be a windows scripting engine, and I don't think GPSoft would
want to branch into developing those itself..but what do I know.

You're right, it's a compiler service rather than a scripting engine as such, but I feel it might be easily added to DOpus (but then again I don't have visibility of the source code, so could be completely wrong).

See blogs.msdn.microsoft.com/cdndev ... nal-part-1

This one might work, although I haven't tested it myself (found it through wikipedia:
CS-Script script engine.

I haven't been able to get DOpus to recognise CS-Script

Maybe it's worth writing a mail to the authors of cs-script and ask how they think the WSH integration should work.
I had a quick reading and to me it seems, the engine does not register as a valid wsh scripting language, at least it does not register like others. It also comes with its own interpreter executables, which makes me wonder.

Any language actually supported by WSH should be runnable by cscript.exe (the native tool to run activex scripts). Unfortunately this is not the case for *.cs files and cs-scripts, as can be seen here:

[code]>cscript.exe hello.cs
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

Input Error: There is no script engine for file extension ".cs".[/code]