[IronPython] Unable to find assembly 'Microsoft.Dynamic

[Dino Viehland]

Marcin wrote:
> Dino Viehland wrote:
> > Can you bring the interactive window up normally using Alt-I or
> > View->Other Windows->IronPython Interactive?
> 
> Sure -- you mean that I run the program via execfile()?
> 
> Here's result, it's an exception but different one this time:
> 
> 
> > execfile('Program.py')
> Traceback (most recent call last):
>    File "<string>", line 1, in <module>
>    File "Program.py", line 4, in <module>
> IOError: System.IO.IOException: Could not add reference to assembly ip_cl1
>     at
> Microsoft.Scripting.Actions.Calls.MethodCandidate.Caller.Call(Object[]
> args, Boolean& shouldOptimize)
>     at
> IronPython.Runtime.Types.BuiltinFunction.BuiltinFunctionCaller`2.Call1(CallSit
> e
> site, CodeContext context, TFuncType func, T0 arg0)
>     at
> System.Dynamic.UpdateDelegates.UpdateAndExecute3[T0,T1,T2,TRet](CallSite
> site, T0 arg0, T1 arg1, T2 arg2)
>     at
> Microsoft.Scripting.Interpreter.DynamicInstruction`4.Run(InterpretedFrame
> frame)
>     at Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame
> frame)
>     at Microsoft.Scripting.Interpreter.LightLambda.Run2[T0,T1,TRet](T0
> arg0, T1 arg1)
>     at IronPython.Compiler.PythonScriptCode.RunWorker(CodeContext ctx)
>     at IronPython.Compiler.PythonScriptCode.Run(Scope scope)
>     at IronPython.Compiler.RuntimeScriptCode.InvokeTarget(Scope scope)
>     at IronPython.Compiler.RuntimeScriptCode.Run(Scope scope)
>     at Microsoft.Scripting.Hosting.CompiledCode.Execute(ScriptScope scope)
>     at
> Microsoft.Scripting.Hosting.CompiledCode.ExecuteAndWrap(ScriptScope
> scope, ObjectHandle& exception)
> >

I was just more wanting to see if the REPL was behaving normally...  I'm
not entirely certain what the problem is for why this won't work but I have
at least one guess.  I'll try and see if I can get a repro on my side

But the good news is I'm pretty sure the next release will fix it.  The next 
release will have Microsoft.Dynamic in the GAC and so we'll always be able
to load that assembly (right now the app domain needs to be setup correctly
and it could be there's an issue w/ the remote domain here).