4

我正在使用 Windows 7 x64。启动 MVC 应用程序时出现 BadImageFormatException。如果它在启用了 32 位应用程序的应用程序池中运行，则不会引发异常。看起来加载 global.asax 是个问题。我启用了融合日志记录 (HKLM\software\Microsft\Fusion!EnableLog) 注册表设置。这是日志：

    === Pre-bind state information ===
LOG: User = NT AUTHORITY\SYSTEM
LOG: Where-ref bind. Location = C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\spl.sim.mvc\5802065c\a2782d40\App_global.asax.olejmmua.dll
LOG: Appbase = file:///C:/Spl/SimSvn4.5/Source/Spl.Sim.Mvc/
LOG: Initial PrivatePath = C:\Spl\SimSvn4.5\Source\Spl.Sim.Mvc\bin
Calling assembly : (Unknown).
===
LOG: This bind starts in LoadFrom load context.
WRN: Native image will not be probed in LoadFrom context. Native image will only be probed in default load context, like with Assembly.Load().
LOG: Using application configuration file: C:\Spl\SimSvn4.5\Source\Spl.Sim.Mvc\web.config
LOG: Using host configuration file: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config.
LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/Temporary ASP.NET Files/spl.sim.mvc/5802065c/a2782d40/App_global.asax.olejmmua.dll.
ERR: Failed to complete setup of assembly (hr = 0x8007000b). Probing terminated.

使用不同的构建配置，结果如下：

构建 x64、32 位应用程序池 false：错误

构建 x86，32 位应用程序池错误：错误

构建 AnyCPU，32 位应用程序池 false：错误

构建 x64、32 位应用程序池 true：错误

构建 x86，32 位应用程序池 true：OK

构建 AnyCPU，32 位应用程序池 true：OK

IIS 快递：好的

如何找到 64 位配置中使用的 32 位问题 dll？

4

1 回答 1

6

I found the problem. I used Instrumentation for profiling. This added the following lines to the web.config:

<dependentAssembly>
    <assemblyIdentity name="Microsoft.VisualStudio.Enterprise.AspNetHelper" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
    <codeBase version="11.0.0.0" href="file:///C:/Program%20Files%20(x86)/Microsoft%20Visual%20Studio%2011.0/Common7/IDE/PrivateAssemblies/Microsoft.VisualStudio.Enterprise.AspNetHelper.DLL" />
  </dependentAssembly>

After removing this dependentAssembly from the web.config section the program is working as expected. I also removed the assemblyPostProcessorType attribute from the compilation element

于 2012-10-31T13:46:00.510 回答