从.Net框架4.0的应用程序运行的托管DirectX不打猎 [英] Managed DirectX running from .Net Framework 4.0 app dont hunt

问题描述

我的工作，使用托管DirectX的数据可视化的产品。我试图升级这个产品的.NET Framework 4.0，但我觉得我在使用托管DirectX和.NET 4.0中的问题一起玩。

I work on a product that uses Managed DirectX for data visualizations. I was trying to upgrade this product to .net framework 4.0, but I think I'm having issues with Managed DirectX and .Net 4.0 playing together.

主要组件未引用托管DirectX。但是，当它试图打电话到该做参考托管DirectX ......全部的寄托死机的程序集。它像调试器只是决定不再踏进大会。我没有得到任何的异常，什么都没有。当我按下暂停键，这个过程是坐在呼叫到该引用托管DirectX组装。

The main assembly does not reference managed directX. But when it tries to call into an assembly that does reference managed directX...everthing "halts". Its like the debugger just decided not to step into the assembly. I get no exception, nothing. And when I hit the pause button, the process is sitting on the call into the assembly that references Managed DirectX.

是否存在已知的兼容性问题与.net 4.0和托管DirectX？

Is there a known compatibility issue with .Net 4.0 and Managed DirectX?

推荐答案

以防万一有一个其他的店有使用管理DirextX编程与.net 4.0，如果你把下面的配置项在您的应用程序的配置，它会让你做到这一点。

Just in case there is one other shop out there using Managed DirextX with .Net 4.0, if you put the following config entry in your app config, it'll allow you to do it.

<startup useLegacyV2RuntimeActivationPolicy="true">
  <supportedRuntime version="v4.0"/>
</startup>

的问题是，对MDX混合模式组合后，编译的1.1运行，和CLR方式4.0载荷混合模式组件改变，所以这个配置文件条目将允许在CLR 4.0运行时使用lagacy组件加载

The problem is that the MDX mixed mode assemblies were compiled against 1.1 runtime, and the way CLR 4.0 loads mixed mode assemblies changed, so this config file entry will allow the CLR 4.0 runtime to use lagacy assembly loading.

这篇关于从.Net框架4.0的应用程序运行的托管DirectX不打猎的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！