02-22-2013, 01:04 PM
I see that CS-Script does the following:
So are you suggesting a possible solution is for .NET functions to co-distribute CS-Script with QM-generated exe's and call when necessary from QM-exe for those .NET functions?
That would work for me....gotta learn a little C# now!
S
Quote:The main idea of CS-Script is to allow "plain vanilla" C# code execution from both command-prompt and form any CLR application hosting the script engine.
Simple deployment approach: just bring both script and engine file (about 100 K size) on the system that has .NET runtime installed and script can be run
All .NET functionality is available (FCL, COM Interop, Remoting, WPF, WCF etc.).
Portability: Scripts can be run on any system, which has CLR installed (including Mono).
So are you suggesting a possible solution is for .NET functions to co-distribute CS-Script with QM-generated exe's and call when necessary from QM-exe for those .NET functions?
That would work for me....gotta learn a little C# now!
S