为什么没有Microsoft.Win64命名空间？ [英] Why is there no Microsoft.Win64 Namespace?

问题描述

我们有一个Microsoft.Win32命名空间，但它保证在64位Windows环境下工作？是否有一个相当于需要有这样的定义为64位的情况？

We have a Microsoft.Win32 Namespace but is it guaranteed to work in 64-bit Windows environments? Is there an equivalent need to have such definitions for a 64-bit situation?

推荐答案

.NET通过它的目标操作系统的体系结构框架默认运行应用程序。所以，如果你正在运行32位Windows，安装在计算机上的.NET框架将是32位架构。在此框架内运行的所有.NET应用程序将随后运行在32位。

.NET applications by default run on the framework which targets the architecture of the OS. So, if you're running 32 bit Windows, the .NET framework installed on the machine would be the 32 bit framework. All .NET applications running on this framework would then run in "32 bit".

如果您正在运行64位Windows，那么你正在运行从32位IL的64位架构但是这在框架没有差别（默认值）上运行的IL。

If you're running 64 bit Windows then you're running a 64 bit framework but the IL that's running on top of the framework doesn't differ (by default) from that of the 32 bit IL.

因此​​，在短期：如果你运行的是32位或64位Windows，因为.NET框架抽象的距离C＃/ VB code无所谓

So in short: it doesn't matter if you're running 32 bit or 64 bit Windows since the .NET framework abstracts that away from the C#/VB code.

本的Microsoft.Win32架构指的是Windows内部的原生API。短期真正糟糕的名字，微软已经给它，它没有任何关系的32位和64位Windows。

The Microsoft.Win32 framework refers to the native APIs inside of Windows. Short of the really bad name that Microsoft has given it, it has nothing to do with 32 bit vs 64 bit Windows.

顺便说一下，有一些事情你不能与64位版本的框架做：比如，没有在64位架构一个JET数据库驱动程序

Incidentally, there are some things you can't do with the 64 bit version of the framework: for example, there isn't a JET database driver in the 64 bit framework.

这篇关于为什么没有Microsoft.Win64命名空间？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！