在 64 位操作系统上运行 32 位 .NET 应用程序，真的很糟糕吗? [英] Running 32bit .NET application in 64bit OS, is it really bad?

问题描述

我知道我们可以通过针对 AnyCPU 来编译 .NET 应用程序，这将导致在 32 位操作系统中运行 32 位，在 64 位操作系统中运行 64 位.

I understand that we can compile a .NET Application by targeting AnyCPU which will cause to run 32bit in a 32bit OS and 64bit in a 64bit OS.

但是，在 64 位操作系统上报告了一个错误*，我的应用程序出现了错误以及解决方案，我需要以 x86 为目标.

However there was a reported bug* on a 64bit OS that my app was giving an error and the solutions for that, I need to target x86.

现在我的问题是:即使您的代码要在 x64 中运行，以 x86 为目标真的很糟糕吗?我们在谈论什么样的表现?(我的应用程序非常占用 CPU，但真的很难想出)

Now my question: Is it really bad to target x86 even though when your code is going to run in x64? What sort of performance we are talking about? (my application is quite CPU intensive but it's really hard to come up with )

毕竟 .NET Framework 将在 32 位上运行，这对我来说听起来很糟糕，而不是充分利用 x64 CPU 的寻址能力**.

After all .NET Framework will run in 32bit which sounds bad to me instead of taking the full addressing power of x64 CPU**.

*我不记得这个错误，但解决方案专门针对 x86，并解决了问题.

*I can't remember the bug but the solution was targeting x86 specifically, and solved the problem.

** 我不确定它是否重要，但我的应用程序不使用任何 Int64 变量.

** I'm not sure if it's any important but my application doesn't use any Int64 variables.

推荐答案

不，还不错；事实上，对于我正在开发的应用程序，我必须以 x86 为目标(因为它引入了供应商不支持 x64 的 COM 对象)

No, it's not bad; In fact, for an application I'm working on, I have to target x86 (as it brings in COM objects, for which the vendor doesn't support x64)

这篇关于在 64 位操作系统上运行 32 位 .NET 应用程序，真的很糟糕吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！