Win32 API与MFC一样吗？？

To:2.在CONSOLE模式中可以调用不涉及图形接口的WIN32 API.
1，3 我也关注！

to 2
可以！
to 3
是一样的！

to 1
也是可以的！不然还用什么VC就是因为它可直接用，而不用象VB 还要申明！

當然不是啦! Console可以叫出窗口, 怎麼說不可以涉及GDI呀, vc++當然可以直接調用Win32API啦, VC++的Application本來就是建基於Win32API
而第3條問題, 你寫過Visual Basic的applicaton都應知道, VB大量使用ActiveX控件, 基本界的大部分工作都交由ActiveX控件包辦, 但當然可以呼叫Win32API.
declare sub "TextOut" lib "gdi32.dll" alias "TextOutA"(byval hDC as long, byval str as string, byval len as long)
只要開一個Module並加入以上的代碼, 程式中就可以呼叫TextOut, 都應該算是直接吧, VB把他再你用時才載入!!!

在　VC＋＋中调用WIN32　API与　在VB中的调用WIN32　API在其格式上有没有什么不同？？

Windows API一个平台上只有一套、、、

我在看＜深入浅出MFC＞时，提到的很多的行程，是不是就是我们所指的进程呢？

在VC中, 只需#include <windows.h>就已經可以用大部份的win32API
但VB中, 你要用那個Function, 就必需先:
declare sub "TextOut" lib "gdi32.dll" alias "TextOutA"(byval hDC as long, byval str as string, byval len as long)
...
之後再用
private sub form_paint()
  dim hdc as long
  hdc = GetDC(hwnd)
  TextOut hdc, "Hello", 5
  ReleaseDC hwnd, hdc
end sub

WIN32的API MFC里99%都封装了连调用的格式都一样

如果要想学WIN32 API 看什么书最好？？？

不一样，WIN32 API是WINDOWS中接口函数，所有编程工具都能调用它，而MFC是微软公司为开发WINDOW应用程序而专门设计的类库，是VC++特有的，其他编程工具没有

別常說MFC好不好, 老是使用別人寫的東東, 是學不到很多的, 是低層學起才是學習之道, 我不否認MFC的棒, 不過也就是太方便才不識合初學者, 要學Win32API最好就裝個MSDN Library + VC6再加很多的練習(可能因為我太Poor)

MFC 是部分 API 的封装,我建议你看看深入浅出MFC 这本书

如果要想学WIN32 API 看什么书最好？？？

MFC和VCL控件都只对WIN32 API部分封装，但在VC或C++BUILDER中都可以直接调用WIN32 API ，在VB中就不行了，需要进行声明。呵呵！！！

如果要想学WIN32 API 看什么书最好？？？
看什么书都不最好，最好是实践

在那里可以找到一些比较全面的，有关WIN32　API的资料！！
请各叔叔，阿姨，哥哥，姐姐，弟弟，妹妹们多多帮忙了！！

win 32 程序员参考大全
清华大学出版
microsoft corporation 著

<Windows 程序设计(第5版)>,Win32 API 的权威指导,经典中的经典!
这里有英版的下载: http://bigluo.tz163.net/download/prog-windows.zip

Windows 程序设计,有中文版 160大元，北大出版社

Language Options
Using C and the native APIs is not the only way to write programs for Windows 98. However, this approach offers you the best performance, the most power, and the greatest versatility in exploiting the features of Windows. Executables are relatively small and don't require external libraries to run (except for the Windows DLLs themselves, of course). Most importantly, becoming familiar with the API provides you with a deeper understanding of Windows internals, regardless of how you eventually write applications for Windows. Although I think that learning classical Windows programming is important for any Windows programmer, I don't necessarily recommend using C and the API for every Windows application. Many programmers—particularly those doing in-house corporate programming or those who do recreational programming at home—enjoy the ease of development environments such as Microsoft Visual Basic or Borland Delphi (which incorporates an object-oriented dialect of Pascal). These environments allow a programmer to focus on the user interface of an application and associate code with user interface objects. To learn Visual Basic, you might want to consult some other Microsoft Press books, such as Learn Visual Basic Now (1996), by Michael Halvorson. Among professional programmers—particularly those who write commercial applications—Microsoft Visual C++ with the Microsoft Foundation Class Library (MFC) has been a popular alternative in recent years. MFC encapsulates many of the messier aspects of Windows programming in a collection of C++ classes. Jeff Prosise's Programming Windows with MFC, Second Edition (Microsoft Press, 1999) provides tutorials on MFC. Most recently, the popularity of the Internet and the World Wide Web has given a big boost to Sun Microsystems' Java, the processor-independent language inspired by C++ and incorporating a toolkit for writing graphical applications that will run on several operating system platforms. A good Microsoft Press book on Microsoft J++, Microsoft's Java development tool, is Programming Visual J++ 6.0 (1998), by Stephen R. Davis. Obviously, there's hardly any one right way to write applications for Windows. More than anything else, the nature of the application itself should probably dictate the tools. But learning the Windows API gives you vital insights into the workings of Windows that are essential regardless of what you end up using to actually do the coding. Windows is a complex system; putting a programming layer on top of the API doesn't eliminate the complexity—it merely hides it. Sooner or later that complexity is going to jump out and bite you in the leg. Knowing the API gives you a better chance at recovery. Any software layer on top of the native Windows API necessarily restricts you to a subset of full functionality. You might find, for example, that Visual Basic is ideal for your application except that it doesn't allow you to do one or two essential chores. In that case, you'll have to use native API calls. The API defines the universe in which we as Windows programmers exist. No approach can be more powerful or versatile than using this API directly. MFC is particularly problematic. While it simplifies some jobs immensely (such as OLE), I often find myself wrestling with other features (such as the Document/View architecture) to get them to work as I want. MFC has not been the Windows programming panacea that many hoped for, and few people would characterize it as a model of good object-oriented design. MFC programmers benefit greatly from understanding what's going on in class definitions they use, and find themselves frequently consulting MFC source code. Understanding that source code is one of the benefits of learning the Windows API.
——《Programming Windows》

就好像积木,MFC的块大一些,外型更完整一些.
WIN32的块小,但效率和灵活性更强.

DX 的接口与 Win32 API 有什么不同？？

学API看Programming Windows95（就是Windows 程序设计）,高级点看programming Application for Microsoft Windows(以前的Advanced Windows),
DX是COM形式的接口，与API（纯C）完全不同。

请大家推一下这个帖子：http://www.csdn.net/expert/topic/385/385474.shtm拜托了》》》》》》》

I think that learning classical Windows programming is important for any Windows programmer..............................YES

->在　VC＋＋中调用WIN32　API与　在VB中的调用WIN32　API在其格式上有没有什么不同？？
主要是数据类型的不同，很大的不同。
比如VC 的int对应VB的long,而不是Integer

调试易

Win32 API与MFC一样吗？？

解决方案 »