为什么没有VS2013的64位版本? [英] Why is there no 64-bit version of VS2013?
问题描述
我从DreamSpark下载了Visual Studio 2013，但它是32位版本，找不到任何64位版本.是否没有?如果可以，为什么没有64位版本的Visual Studio?
I downloaded Visual Studio 2013 from DreamSpark but it's the 32-bit version and I couldn't find any 64-bit version. Is there none, and if so why is there no 64-bit version of Visual Studio?
推荐答案
首先，Visual Studio工具集附带了一个64位C ++编译器.因此，您随时可以更改项目设置，以根据需要对应用程序进行64位构建.
First, there is a 64-bit C++ compiler that comes with Visual Studio tool set. So you can always change your project settings to make 64-bit builds of your app as needed.
现在，回答原始问题.
从成本和投资回报率角度考虑.在Microsoft多年的软件发布中，这就是我如何考虑对64位版本进行考虑的方法.
Think of it from a cost and ROI perspective. From years of shipping software at Microsoft, here's how I've seen the consideration for 64-bit builds get made.
-
当32位应用在64位上运行正常时，考虑使用64位几乎是初学者.
When the 32-bit app works just fine on 64-bit, it's almost a non-starter to consider 64-bit.
Microsoft的大多数项目不是简单的Visual Studio小项目，开发人员可以在其中将Project设置从32位翻转到64位. (我实际上不知道Visual Studio团队是否用VS项目来编译Visual Studio.)它们通常是一百万行以上的代码，这些代码是使用VS编译器集构建的，但是来自命令行和Makefile环境.切换到64位意味着更新了许多此构建基础结构.
Most of the projects at Microsoft aren't simple little Visual Studio projects in which the developer can just flip the Project settings from 32-bit to 64-bit. (I actually don't know if the Visual Studio team compiles Visual Studio with a VS project.) They are often well over a million lines of code that build with the VS compiler set, but from a command line and Makefile environment. Switching to 64-bit means updating a lot of this build infrastructure.
从32位移植到64位需要一定的成本.第一个成本就是修复错误，使代码编译，重构构建环境以及所有的前期工作，只是为了使初始构建顺利进行.
There is a cost of porting from 32-bit to 64-bit. The first cost is just fixing the bugs, getting the code to compile, restructuring the build environment, and all the upfront work just to get the initial build going.
为应用程序分别构建32位和64位版本需要支付持续的费用.您必须每天构建两次.您必须每天对其运行两次测试抵押品.这不是2倍的成本，但也不是免费的.
There is an ongoing cost you pay for having separate 32-bit and 64-bit builds of an application. You have to build it twice every day. You have to run the test collateral on it twice every day. It's not a 2x cost, but it's not free either.
在相同代码库中有更多SKU，这增加了开发人员签入时可能破坏某些东西的机会.当然可以进行自动化测试来防止这种情况，但是由于开发人员需要他进行自动测试，因此降低了速度将必须返回并修复他尚未在其测试计算机上本地安装的其他SKU.
With more SKUs from the same code base, it increase that chances that a developer will break something when he checks in. Of course there can be automated tests to prevent this, but it will slow the developer down since he will have to go back and fix the other SKU that he doesn't have installed locally on his test machine.
现在，有一些迁移到64位的动机:
Now here are some of the motivations for moving to 64-bit:
-
您确实需要利用64位性能和内存体系结构.占用更多内存的大型数据库服务器将受益于对32位Windows进程施加的超过2GB的限制.
You really need to take advantage of 64-bit performance and memory architectures. Large database servers that use as much memory as possible will benefit from accessing more than 2GB limit imposed on a 32-bit Windows process.
您需要与已经用64位编译的内容集成.例如，如果要编写Windows的Shell扩展，则需要64位版本才能在64位Windows上运行.这并不意味着必须移植整个应用程序，而是意味着该组件将需要单独的64位版本.
You need to integrate with something already compiled with 64-bit. For example, if you want to write a shell extension for Windows, you will need a 64-bit build to run on 64-bit Windows. That doesn't mean the entire app has to be ported, but it does mean this component will need a separate 64-bit build.
您有一个平台或API故事供外部开发人员考虑.通常，他们对64位版本有自己的需求.因此，即使您的本机应用程序可以摆脱32位支持，他们也可能需要您提供64位就绪的API.
You have a platform or API story for external developers to consider. Usually, they have their own needs for 64-bit builds. Hence, they may need a 64-bit ready API from you even if your native app can get away with 32-bit support.
您的团队刚刚被重组为Windows部门，并且您的团队代码被认为必须包含在下一Windows版本中.无需再做任何决定-您的代码将针对32位，64位和ARM(Surface RT)进行编译.
Your team has just been re-organized into the Windows division and your team's code has been deemed necessary to be included into the next Windows release. There's no decision to be made anymore - your code will be compiling for 32-bit, 64-bit, and ARM (Surface RT).
这篇关于为什么没有VS2013的64位版本?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
