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

问题描述

据我所知，我们可以通过瞄准值为anycpu这将导致在一个64位操作系统32位操作系统和64位运行32位编译.NET应用程序。

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.

不过有一个报告的bug *在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.

现在我的问题：是不是真的坏到目标86，即使当你的code是要在64运行？什么样的表现，我们在谈论什么？ （我的应用程序是非常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框架将在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.

推荐答案

没有，这不是坏的;事实上，对于我工作的一个应用程序，我的有无的目标86（因为它带来的COM对象，为此，供应商不支持64位）

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屋！