Win32 API在Longhorn上会怎么样?

原创 2005年05月03日 09:57:00

Q: So what's changing from a developer's standpoint?

A: In the technology generations leading up to Longhorn, Microsoft has been moving to a .NET-based managed code environment dubbed WinFX, and the Longhorn generation will finally mark a clean split with the Win32 APIs of the past. That is, Win32 will be in maintenance mode, and all new development will occur with WinFX managed APIs. One such API, Avalon, forms the basis for the new Desktop Compositing Engine (DCE) in Longhorn that replaces GDI and GDI+. These and other new Longhorn APIs will utilize the XML Application markup language (XAML) to make Longhorn more accessible to developers than ever before. The idea is to significantly reduce the number of APIs and make the APIs more standardized. Today, there are over 76,000 Win32 APIs, and countless wrappers. With Longhorn, Microsoft hopes to reduce the API set to 8,000 to 10,000.

Another significant change in Longhorn involves device drivers. In the past, Microsoft allowed customers to use non-signed drivers, which helped compatibility, but caused stability problems. No more: In Longhorn, users hoping to take advantage of the system's exciting new capabilities will only be able to use signed drivers.

Developers interested in Longhorn should examine the Visual Studio 2005 "Whidbey" release, currently in beta, and the Longhorn SDK. which includes developer-accessible UI components and behaviors.

Q: This sounds like a huge change from today's Windows. Will my current applications still work with Longhorn?

A: Yes. Microsoft has even pledged to retain DOS compatibility with Longhorn, though it's currently unclear whether DOS support will be improved over what's available today in Windows XP.

Q: I keep hearing that WinFS is a new file system. Is Microsoft abandoning NTFS?

A: No. WinFS is implemented as an add-on to NTFS and is not a completely new file system. Rather, it is a new storage engine built on the NTFS file system.


  • sugar88
  • sugar88
  • 2005年07月04日 08:36
  • 938

【怀旧】Windows Longhorn Build 4074安装教程(包括开启Aero特效)

昨天饶有兴趣地折腾了一下Windows Vista的开发版Windows Longhorn。为了折腾这玩意,投入了Google的怀抱,查阅了很多的外文教程和资料,才勉强成功!不过看看就好,要使用就算了...
  • mgsky1
  • mgsky1
  • 2017年07月20日 09:10
  • 1404

VMWare下安装Longhorn 5048 beta

  • yinleiwudi
  • yinleiwudi
  • 2005年05月20日 14:30
  • 1201

如果codefish架构在xml上会怎么样 ?

  • TJUsecretfish
  • TJUsecretfish
  • 2006年04月14日 15:23
  • 910

Longhorn:蓝屏更少 红屏惊现!

在网上看到的一个笑话,本来这个消息没有什么,主要回帖的人太逗了,大家看看:根据微软的描述,微软的下一代操作系统WindowsLonghorn出现BSOD(蓝屏,Blue Screen of Death...
  • yuzhongyuzhong
  • yuzhongyuzhong
  • 2005年07月28日 08:44
  • 507

译:如何使用win32 api中的edit控件

译:如何使用win32 api中的edit控件――――利用Edit类进行windows gui编程的方法和技巧© Guy Lecky-Thompson   Jun 14, 2007 Article d...
  • lidemin
  • lidemin
  • 2009年04月25日 08:31
  • 1908


  • RancherLabs
  • RancherLabs
  • 2017年05月02日 13:32
  • 909

win32中获得 文本框edit内容

/*wchar_t *szName; int iLength; iLength=GetWindowTextLength(hedit); szName =(wchar_t*)mallo...
  • az44yao
  • az44yao
  • 2015年08月14日 15:34
  • 4381

Windows Longhorn Server

Windows Longhorn Server Build 5744 X86 (可能就是Windows Server 2007)Longhorn Server 按照微软的命名方式,很有可能就是Wind...
  • lihulin
  • lihulin
  • 2006年10月21日 22:13
  • 925

Win32 API中使用定时器的三种方法

1.SetTimer(HWND,UINT,UINT,TIMERPROC);第一个参数设置为捕获该定时消息的窗口句柄, 第二个参数是定时器的id,第三个是以毫秒为单位的定时长度,最后一个参数设置为NUL...
  • fancycow
  • fancycow
  • 2011年08月10日 15:57
  • 15391
您举报文章:Win32 API在Longhorn上会怎么样?