WHO KNOWS THE WINDOWS CORE PROGRAMMING DIRECTORY OF THE 5TH EDITION, WRITTEN BY MICROSOFT STRONGMAN

How to say it, this is the first English technical book that I plan to read in order to rough the former Iwan Wuzhou is just ** and some information. The biggest benefit I get is precisely the rhythm of my reading, which used to be a bit fast, and I didn't notice it. But this.

There are 3 ways to write Windows applications using VC, API, MFC and MFC. net, for. NET I'm not too familiar with it, I feel like using VC's. net, it is better to make the tease of filial piety with c

Let's talk about API and MFC, API is an application programming interface function provided by Windows to software developers, and Windows applications can be developed using Windows API.

MFC is the Microsoft Foundation Classes that was released with the VC. MFC encapsulates most of the functions of the API, and the use of MFC can greatly improve the efficiency of developing Windows applications, because MFC is a wrapper of the API, and Microsoft has done a lot of work to hide a lot of program developers who use C++ MFC to compile software under Win, such as application implementation message processing, device environment drawing, etc.

Learning Windows programming can learn API programming, or you can directly learn MFC programming, but understanding API programming will be of great help to understand the structure of MFC class libraries.

Suffice it to say, if you want to have an in-depth study and research on developing Windows applications with VC, then it's best to start with API programming. Or start with MFC and then go back and look at Windows API programming;

If you just want to write some simple programs without in-depth learning, then you can just learn MFC programming.

As for what you said about Windows Core Programming, Windows Network Programming, Windows Graphics Programming, Windows System Programming, Windows Game Programming, etc., these are just different development directions after you get started, and it's too early to think about them.

So, if you want to learn Windows programming in depth, I recommend you read Windows Programming (5th Edition), because the most important thing for you right now is to get started with the basics.

Of course, after learning Windows programming, you can do some practical things.

The key is what program do you want to program? If you're a win32 platform application that compiles a stupid notepad, like notepad, you just look at MFC programming and win32 APIs.

Windows Programming (Fifth Edition) This book is good.,If you're getting started, read this book right.,No matter which direction you're in, you always have to play and foundation.。

You don't learn the data structure and the operating system well. Heap, stack, process, thread, synchronization, mutex, and memory management are all in the last 2 courses.

Handles are not the concept of MFC, on the contrary, MFC still uses less handles, more often pointers. Handle is the concept of windows, to put it bluntly, it is a resource digital flag, such as window, **, etc., like a person's name, we can get a handle and we can do all kinds of operations on it. It can be said that every resource of Windows is finally operated by a handle by calling the API.

It's not necessary to figure out the principle of Windows.,This task,Personally, I think it's too arduous.。 It's not appropriate for you to look at core programming right now, but when you have a certain foundation in Windows SDK and MFC, look at core programming. If you don't understand it, you can take it slowly, some things can't be mastered in 1 or 2 days, even if you master it, you won't forget it after a few days, and most of them still have to be accumulated slowly in programming practice.

Let's look at Windows programming first, and then look at core programming.

As a beginner, I think it's best to practice more. If you can make something based on what you have learned, you may be able to stimulate your interest in learning.

The heap and stack of memory allocations are not the same thing as the heap and stack of data structures.

In memory, the things in the heap are dynamically allocated, and the stack is automatically allocated, for example.

int i;

int *p= new int;

where i is stack-allocated and p is heap-allocated.

The things in the stack are automatically allocated and released (see the lifetime of i), and the things in the heap are dynamically allocated (need new or malloc, etc.) and need to be released manually (use delete or free).

For example, the parameters of the function are also allocated in the stack, and they are automatically released after the function is called; There are also global variables in the stack.

The heap and stack in the data structure are just a structure for storing variables, just like arrays, linear tables, and queues.

Handles are the stuff in the SDK, and Windows programming is mainly about how to use C for simple SDK programming. These are also very basic API programming knowledge. Programming needs to be gradual, and if you don't understand it in the front, you may not understand it in the back.

I'm a junior like LZ.

I'll tell you how I got started, I hope it helps.

I studied C for one semester in my freshman year, and then there were no computer classes, so I studied on my own.

When I was a sophomore, I studied VB for a month, and then when I was in my junior year, I watched Sun Xin's C++ tutorial from beginner to proficient for more than a month (one episode a day), and then I watched "Core Programming" for a week, and now I am learning WDMOf course the rest of the time was playing, one after another.

PS: "Core Programming" is a true TM classic!

。。。Dizzy.

In this way, learn the courses in school first, and then talk about it, get the GPA up, what's the urgency As for Windows programming, since you are experiencing a bottleneck now, then take your time, you will learn it right now, what do you want to do now??? Write a software to apply? It's better to treat it as a hobby, nothing to see, in addition, many things are interconnected, broaden your horizons, and usually get in touch with all kinds of knowledge, even if it's just a general understanding

In fact, I found that no matter what you learn, after the confusion time accumulates to a certain extent, it will inevitably break up, and the time will not be very long, believe in yourself, good luck!

After reading your description, first of all, I feel that your C language foundation is not particularly good, including data structures, if you are very proficient in both, what memory allocation, stack, heap are very easy to understand, as for MFC, my suggestion is to look at the example, some concept examples will be used even if you don't understand it.

When doing examples, you should turn over the original books, such as Tan Haoqiang's C language and data structures, plus MFC, and strive to turn these three books roughly once a week, with the examples you make, you will have a deeper understanding.

In addition, the biggest problem for programming is mentality, because programming is a test of logical thinking ability, usually the more anxious you are, the more you have no ideas, you need to calm down, analyze the problem well, don't look at the problem of finding a job after graduating from senior year, you should take programming as a lifelong career, correct your mentality, use as much time as possible to read some programming books, even if you can't find a job after graduating from your senior year, you can still continue to learn programming, and you can always become a programming master one day.

So instead of feeling sorry for yourself, it's better to spend more time reading books and practicing.

If you don't understand some of the concepts in C++, you can take a look at assembly.

Although assembly is a low-level language, many high-level language concepts can still find satisfactory answers from it.

Such as stacks, threads, processes, etc. Learning from the structure of the 8086 computer helps to better understand C++

I don't read any books and read MSDN directly, so I can learn it by writing more ** and debugging more.

Learning VC doesn't need to go deep, just go simple.

If you want to learn VC well, you must have a certain C++ foundation. Don't force yourself to memorize any MFC classes before you start programming in Windows, that will only add to your burden. In the beginning, let yourself write some simple Windows console programs, for example:

If you want to read and write a file, and you don't know which class to use because you're not familiar with the MFC library, this is normal, but you can go to Baidu, Google and search for this information. After some searching, you will find that the original cfile can be used to manipulate files, and the next thing is easy to do, which is nothing more than to generate a cfile object, and use the read and write member functions of the object to read and write the file. The important thing is to do it, not to see.

Windows Programming", a must-see classic for learning SDK!

Windows applications can be written in many languages, including C, C++, Pascal, Visual Basic, and many more. If you want to write a Windows program, you can take a look at <

If you want to learn about Windows development, you can delve deeper into Microsoft's MSDN than any book.

But if you want to learn programming well, you need to learn programming ideas, programming languages are just tools, and you can learn different languages as needed.

APIs are like toolboxes, if you're going to build a car, and you have wheels, engines, gearboxes, etc., that someone else has made, you just have to assemble them. See MSDN for details.

GUI is the image user interface, which is the Windows window interface you usually see, which can be designed in a very good way in Microsoft's development environment. Again, see MSDN for details.