On Fri, Sep 25, 2009 at 06:22:24PM +0200, Dody Gunawinata wrote:
>Yup. NWSGI beta 2 was built against older version. Either rebuild or use
>assembly rebinding
>http://aspadvice.com/blogs/ssmith/archive/2006/11/15/AssemblyBinding-in-Web-Config-and-XMLNS.aspx
Thanks, man, for the quick reply :D
>> Could not load file or assembly 'Microsoft.Scripting, Version=0.9.6.20,
>> Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its
>> dependencies.
>> The located assembly's manifest definition does not match the assembly
>> reference. (Exception from HRESULT: 0x80131040)
I configured for 1.0.0.0 as Properties of Microsoft.Scripting.DLL says and
2.6.10920.0 for IronPython.dll.
AND IT WORKS! :)
(My only outstanding issue is now
Line 9: engine = __import__(settings.SESSION_ENGINE, {}, {}, [''])
Line 10: session_key =
request.COOKIES.get(settings.SESSION_COOKIE_NAME, None)
Line 11: request.session = engine.SessionStore(session_key)
Line 12:
Line 13: def process_response(self, request, response):
which is a Django error I'll have to fight with, hopefully it's not too bad :)
Here are the configuration tags if they'd help anyone else.
<!-- ATTEMPT AT FIXING NWSGI LINKED AGAINST 2.6B2 -->
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="IronPython"
publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="2.6.0.20" newVersion="2.6.10920.0"
/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.Scripting"
publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.9.6.20" newVersion="1.0.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
Thanks!
--
mjt
_______________________________________________
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
