[IronPython] IronPython/NWSGI 0-byte 200/404 response with HelloWorld?

[Markus Törnqvist]

On Tue, Sep 22, 2009 at 09:56:58PM +0300, Markus T�rnqvist wrote:
>On Tue, Sep 22, 2009 at 09:43:50AM -0600, Jeff Hardy wrote:
>>I'd like to help more, but I'm a bit overwhelmed at the moment - sorry.
[...]
>Anyway, I'll tell you which way it goes, don't worry about that :D

I upgraded to IronPython 2.6rc1 by removing IronPython, so it left
only my site-packages and scripts intact, and then installing the
new version.

I replaced the seven IronPython DLLs in ...\site-packages\myapp\lib 
with the new versions (dated 9/15/2009), reset IIS and restarted
the Default Website to be safe.

http://localhost/

 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) 

[FileLoadException: 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)]
   NWSGI.WsgiHandler..cctor() +0

[TypeInitializationException: The type initializer for 'NWSGI.WsgiHandler' threw an exception.]

[TargetInvocationException: Exception has been thrown by the target of an invocation.]
   System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck) +0
   System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache) +86
   System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache) +230
   System.Activator.CreateInstance(Type type, Boolean nonPublic) +67
   System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) +1051
   System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) +111
   System.Web.Configuration.HttpHandlerAction.Create() +57
   System.Web.Configuration.HandlerFactoryCache..ctor(HttpHandlerAction mapping) +19
   System.Web.HttpApplication.GetFactory(HttpHandlerAction mapping) +96
   System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) +125
   System.Web.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +93
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155

What can I do here?

I haven't played much with the registry, but it says

 WRN: Assembly binding logging is turned OFF.
 To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
 Note: There is some performance penalty associated with assembly bind failure logging.
 To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

So I figured I'd create a DWORD named Fusion!EnableLog and set the value to 1.

But it didn't have a visible effect even after restarts.

Is this a problem with NWSGI not understanding 2.6rc1? A recompile
required? Will there be an update on the site? Something else bad? Help?

Thanks!

-- 
mjt