由于种种原因，不能。

这篇MSDN文章解释了原因。

First, from a performance perspective the pointers get larger, so data structures get larger, and the processor cache stays the same size. That basically results in a raw speed hit (your mileage may vary). So you start in a hole and you have to dig yourself out of that hole by using the extra memory above 4G to your advantage. In Visual Studio this can happen in some large solutions but I think a preferable thing to do is to just use less memory in the first place. Many of VS’s algorithms are amenable to this. Here’s an old article that discusses the performance issues at some length: https://learn.microsoft.com/archive/blogs/joshwil/should-i-choose-to-take-advantage-of-64-bit Secondly, from a cost perspective, probably the shortest path to porting Visual Studio to 64 bit is to port most of it to managed code incrementally and then port the rest. The cost of a full port of that much native code is going to be quite high and of course all known extensions would break and we’d basically have to create a 64 bit ecosystem pretty much like you do for drivers. Ouch.

不!Visual Studio没有64位版本。

如何知道它不是64位的: 下载Visual Studio并单击安装按钮后，您将看到它自动选择的初始化文件夹是C:\Program Files (x86)\Microsoft Visual Studio 14.0

根据我的理解，从Windows 7开始，所有64位程序/应用程序都到C:\Program Files，所有32位应用程序都到C:\Program Files (x86)。

不，但32位版本在64位Windows上运行良好。

有64位的Visual Studio吗?

是的，字面上有一个叫做“Visual Studio”，是64位的，但在Mac上，而不是在Windows上

为什么不呢?

做决定是我们大脑中产生的电化学反应，它有一个激活点(我能想出的最无聊的答案，但跟随)。历史上也发生过同样的情况:Windows 64!

So in order to answer this fully I want you to remember old days. Imagine reasons for "why not we see 64bit Windows" are there at the time. I think at the time for Windows64 they had exact same reasons others have enlisted here about "reasons why not 64bit VS on windows" were on "reasons why not 64bit Windows" too. Then why they did start development for Windows 64bit? Simple! If they didn't succeed in making 64bit Windows I bet M$ would have been a history nowadays. If same reasons forcing M$ making 64bit Windows starts to appear on need for 64Bit VS then I bet we will see 64bit VS, even though very same reasons everyone else here enlisted will stay same! In time the limitations of 32bit may hit VS as well, so most likely something like below start to happen:

Visual Studio将放弃对32位的支持，变成64位， Visual Studio Code将取而代之， Visual Studio将为旧的扩展提供类似WOW64的功能，我认为这是不太可能发生的。

我打赌Visual Studio Code会及时取代这个位置;我猜它的分岔点将是某个CPU制造商X开始与x86_64架构竞争，在笔记本电脑和/或工作站的主流市场上占据一席之地，

更新:从visualstudio 2022预览网站引用https://web.archive.org/web/20211030202827/https://visualstudio.microsoft.com/vs/preview/:

利用您计算机的所有资源，将Visual Studio扩展到最大的项目和复杂的工作负载，而不会耗尽内存。您可以继续运行和调试32位应用程序。

似乎他们做了我所期待的，他们放弃了旧的32位支持，引用https://web.archive.org/web/20210910130939/https://learn.microsoft.com/en-us/visualstudio/extensibility/migration/update-visual-studio-extension?view=vs-2022:

Visual Studio 2022 RC是一个64位的应用程序，在VS SDK中引入了一些突破性的变化

I want to thank every upvote for keeping this answer. As a thank you I want to add one more prediction: I still believe the trend will lean towards VSCode in time while VSCode forks or turns-into something like Eclipse Theia. Most probably they will give full support on cloud platforms with that. Especially for enterprises that will add great value and for the marketing sake I cannot find any better excuse about "move your onprem into the Azure" stuff. Anyhow seems we are correct about: Why Visualstudio was not 64 bit while it should be 64bit long ago,

更新:我想这将是最后一次更新。是的，这正是我所期待的方向:https://vscode.dev/被公开，

由于种种原因，不能。

这篇MSDN文章解释了原因。

First, from a performance perspective the pointers get larger, so data structures get larger, and the processor cache stays the same size. That basically results in a raw speed hit (your mileage may vary). So you start in a hole and you have to dig yourself out of that hole by using the extra memory above 4G to your advantage. In Visual Studio this can happen in some large solutions but I think a preferable thing to do is to just use less memory in the first place. Many of VS’s algorithms are amenable to this. Here’s an old article that discusses the performance issues at some length: https://learn.microsoft.com/archive/blogs/joshwil/should-i-choose-to-take-advantage-of-64-bit Secondly, from a cost perspective, probably the shortest path to porting Visual Studio to 64 bit is to port most of it to managed code incrementally and then port the rest. The cost of a full port of that much native code is going to be quite high and of course all known extensions would break and we’d basically have to create a 64 bit ecosystem pretty much like you do for drivers. Ouch.

不，但它在win64上运行良好，并可以创建win64 . exe