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.

相关文章推荐

重温WIN32 API ------ 最简单的Windows窗口封装类

如果你也厌倦了复杂的MFC,这里提供了一个非常简单的把C++类、对象与窗口类、对象联系起来的方式。...
  • smstong
  • smstong
  • 2015年01月04日 17:14
  • 11120

串口编程之一: WIN32 API 中串口DCB 结构的介绍

在应用WIN32  API 对串口进行编程时, 必定会使用到DCB 结构. 下面的DCB 结构的一些介绍. 首先是DCB 结构. typedef struct _DCB {       ...

学习win32 API开发6-给窗口添加菜单

看到别人做菜单有很多种,而我就比较不要麻烦就用较简单的来学习下吧,好用就行了。 一、用编辑资源来添加菜单 我用的VC++6.0,VS2013也是一样的!其他的工具嘛,没有用, 不知道。 先插入或者说添...
  • wo125
  • wo125
  • 2014年03月25日 00:47
  • 2894

基于c++使用win32 api遍历文件夹

在做图像处理算法过程中,有时需要将算法应用于某个文件夹下的所有图片,然后对比查看处理效果。有时文件夹内还有子文件夹,这时就需要递归遍历当前文件夹,以将算法应用于所有图片。遍历文件夹程序网上可以找到一些...

Win32API学习笔记第八章

Win32API学习笔记第八章

ruby的魅力:直接呼叫Win32API

ruby的魅力:直接呼叫Win32API Ruby是很强大,可以利用附加库dl/win32的Win32API模块直接呼叫win32API Win32API.new 参数1 字符串 呼叫dll...

基于WIN32 API及MFC的多线程技术

32位Windows环境下的Win32 API提供了多线程应用程序开发所需要的接口函数,而相应的MFC类库封装了多线程编程的类,用户在开发时可根据应用程序的需要和特点选择相应的工具。以下将概括归纳基于...
  • hjh2005
  • hjh2005
  • 2012年02月19日 16:09
  • 766

win32 api 调用浏览文件 保存文件对话框 以及浏览文件夹对话框

 整理一下.. #include #include #include #include #include //选择文件夹 用到 //打开文件 保存文件 #define MAX_F...

<Win32 API> GDI和GDI+ 双缓冲模式绘图

使用兼容DC,在DC上创建一个DC进行图形绘制.

WIN32汇编实现进程导入表HOOK API

;**************************************************** ;DevName:进程导入表API_HOOK ;开发者:GhostHand ;*******...
内容举报
返回顶部
收藏助手
不良信息举报
您举报文章:Win32 API在Longhorn上会怎么样?
举报原因:
原因补充:

(最多只允许输入30个字)