Suggestion: input for "code" in .NET script components

Replies to This Discussion

Permalink Reply by michael sprinzl on October 24, 2011 at 6:14am

some stolen code......

 

 

private void RunScript(string code_in, object y, ref object A)
  {
    String InputCode = String.Empty;
    InputCode = code_in;
    System.Reflection.Assembly Assembly = CompileCode(InputCode);
    if (Assembly == null) return;
    object Temp = Assembly.CreateInstance("RunTimeCompiler.Test");
    if (Temp == null) return;
    Type RefType = Temp.GetType();
    System.Reflection.MethodInfo MethodInfo = RefType.GetMethod("Ergebnis");
    A = MethodInfo.Invoke(Temp, new object[] { });
  }

 

//<Custom additional code>
  public static System.Reflection.Assembly CompileCode(string InputCode)
  {
    System.CodeDom.Compiler.CodeDomProvider CodeDomProvider = System.CodeDom.Compiler.CodeDomProvider.CreateProvider("CSharp");
    //Parameter für die Compilierung, wie die einzubindenen Bibliotheken usw.
    System.CodeDom.Compiler.CompilerParameters CompilerParameters = new System.CodeDom.Compiler.CompilerParameters();
    CompilerParameters.ReferencedAssemblies.Add("System.dll");
    CompilerParameters.ReferencedAssemblies.Add("System.Windows.Forms.dll");
    CompilerParameters.CompilerOptions = "/t:library";
    CompilerParameters.GenerateInMemory = true;

    //Über den StringBuilder wird der Code zusammengesetzt
    string Temp;// = new StringBuilder();


    Temp = @"using System;";
    Temp = Temp + @"using System.Windows.Forms;";
    Temp = Temp + @"namespace RunTimeCompiler{";
    Temp = Temp + @"public class Test{";
    Temp = Temp + @"public object Ergebnis(){";
    Temp = Temp + InputCode;
    Temp = Temp + @"}}}";


    //Compilieren
    System.CodeDom.Compiler.CompilerResults CompilerResults = CodeDomProvider.CompileAssemblyFromSource(CompilerParameters, Temp);
    //Auf CompilerFehler prüfen
    if (CompilerResults.Errors.Count > 0)
    {
      MessageBox.Show(CompilerResults.Errors[0].ErrorText, "Fehler bei Laufzeitkompilierung", MessageBoxButtons.OK, MessageBoxIcon.Error);
      return null;
    }
    //Rückgabe der compilierten Assembly
    return CompilerResults.CompiledAssembly;
  }
  //</Custom additional code>

 

 

 

 

Permalink Reply by Giulio Piacentino on October 24, 2011 at 9:00am

Hi Michael,

 

you do not really want to do this because loaded assemblies are not candidates of garbage collection and will cause a small but noticeable amount of memory to be used and never released at each definition update (memory leak). This might be fine for a short-medium test, but if you play some time with the definition it will slowly use up all computer memory, up till making Rhino crash when no more is available.

You might have some luck - but I have not tried this and I speak mostly by heart - if you create a new AppDomain at each operation and then unload it. Frankly I would not spend too much time with this: it is then impossible to exchange any type and instance that is defined in your new assembly (class, struct, enum, delegate ... or instances thereof), as that implies having the code loaded in memory. Also, everything will marshal (be copied or serialized+deserialized) across AppDomain boundaries. See here and here.

 

Python is interpreted and can therefore execute code at runtime. It's simple and the DLR makes a lot of this extra work for you.

 

- Giulio
_______________
giulio@mcneel.com
McNeel Europe

Permalink Reply by michael sprinzl on October 24, 2011 at 11:54pm

maybe a dispose at the end could help. I personally like microsoft visual express as editor... or maybe monodevelop. Do you have any suggestions on this field to get this done?

Permalink Reply by Steve Baer on October 28, 2011 at 9:47am

I would agree with Giulio that python is going to be much easier to work with as far as passing functions around that can be called in other components.  If you want to do this in C# or VB.NET, you are most likely going to need to use reflection.  Here's a trivial sample in C#

 

Attachments:

• reflection_call.gh, 2 KB