Windows api reference msdn




















Remote Differential Compression. Transactional NTFS. Volume Management. Windows Storage Management. Windows Data Access Components. The Diagnostics API enable you to troubleshoot application or system problems and monitor performance. The Graphics, multimedia, audio, and video APIs enable applications to incorporate formatted text, graphics, audio, and video. The System Services APIs give applications access to the resources of the computer and the features of the underlying operating system, such as memory, file systems, devices, processes, and threads.

The Security and Identity APIs enable password authentication at logon, discretionary protection for all sharable system objects, privileged access control, rights management, and security auditing. The System administration interfaces enable you to install, configure, and service applications or systems. The Networking APIs enable communication between applications over a network. You can also create and manage access to shared resources, such as directories and network printers.

The following are technologies and APIs that are outdated or have been replaced or deprecated from the Windows client and server operating systems. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Don't get me wrong, I can find topics covering individual functions, but cannot find a 'home node' of sorts for referencing all Windows API documentation.

It makes it real difficult to learn what I need to learn. Is this intentional? But this is reference information, hardly suitable for learning. If you don't have a book you should definitely get one to study the basics. Yes, thank you. I have two of Petzold's 'Programming Windows' volumes. Referring me to Petzold's excellent books is hardly an adequate response to my question, Scott!! Where's Microsoft's documentation?

You know, the API's grouped in some intelligible way. Something more than just an endless yacking on and on about this and that, but a serious documentation of the subject matter By the way, an excellent help page explaining a particular API function that cannot be found, because, say, for example, the seeker doesn't know the name of the particular function might as well not exist at all!

The MSDN library is organised pretty well. It is a combined resource of all developer information for the various Windows platforms so there is going to be some problems. But the thing which Scott is very serious and correct on, the individual function specifications are not suitable for learning. For example, CreateFile, the function reference tells you exactly how CreateFile works, but only that, it doesn't give you information on paths especially important for create file since it can open UNC paths and handles to devices , it doesn't give you information on how to use the handles, constraints or anything like that, it just tells you how CreateFile works.

This is important to know because some functions have order constraints they must be called in a certain order but the individual function specification doesn't go into that at all. With the function reference, there is usually an about and using section along with it. These sections give you overviews and descriptions of usage which covers more than the function reference can.

So to use the MSDN effectively you have to read everything in the about and using sections too. Even then, sometimes the MSDN library reference is missing something that you can find in books, that is why references are harder to learn off of.

The documentation is grouped in an intelligable way too. Drawing is under Graphics and Multimedia. It is just that there is so much to cover you have to go through several layers of sections to get where you want. So the best thing you can do to get used to the MSDN is not be afraid of the sheer amount of data and start searching through it.

The link you provided appears promising and I appreciate that fact that your response is one that is truly constructive and helpful. I like books, too. I know I am not alone in my opinion. Unfortunately there are not any recent versions that cover the latest features available in Windows, to my knowledge, although it has been a while since I've searched Amazon. I don't understand why Microsoft constantly creates new frameworks for writing windows programs. At about the same time, there was MFC, which was a thin wrapper for the windows API, at least from a performance perspective.

Then came. What a mess it is! It makes ordinary pre. It has been and still is a lot of work developing my own frameworks, but I am happy I went to the trouble of doing it because it is now paying off.



0コメント

  • 1000 / 1000