I am already a junior, but I feel that what I learned is no different from what I learned in my freshman year. At most, I have a bit more publicity.
As a result, I decided to work hard this summer vacation. In view of my special liking for C ++, I just went to the library and saw Sun Xin's VC ++ in-depth explanation. it took me a dozen days to finish reading this book and get a preliminary understanding of MFC.
Indeed, although this book is already a very old one, it is a classic book that understands the principles of Message Passing in Windows programs. After reading it, I found that MFC is too cumbersome, and many things should be handled by myself, and many function calls are also very troublesome. When I first came into contact with an MFC function, staring at the MSDN document for a long time is not very good in English, it looks a little difficult), and many functions have many parameters, each time you use it, you can only open the MSDN document for search. The feeling of MFC is one word: annoying.
Later, I read the C # book and practiced it with vs. Compared with the VC ++ MFC, C # is quick and easy to use. Can MFC adapt to the increasing demand for development efficiency in the future? Is MFC outdated?
I agree with this person's point of view.
Cascade,
The more you know, the more you don't know.Someone must have said, no! Most of these are middle-aged people.
Someone must have said that it has long expired. Many of these people are younger. However, you should not only listen to the comments of one person or a group of people when such things involve certain technologies. Most people usually use several technologies, and the technology they are most familiar with knows its advantages and disadvantages. However, it is usually one-sided to understand unfamiliar technologies. So it is better to ask more questions.
Although C #'s winform and WPF have now become excellent substitutes for MFC, my suggestion is that this book can still be viewed, and I do not need to be proficient in it, for more information, see. After understanding the Internal principles, a lot of relevant knowledge will get twice the result with half the effort. The previous classics, frameworks and ideas are worth learning. Will any technology be outdated? In order to catch up with the technology, all you may learn in your life is just a glimpse. Go deep into a study and get all done. So it doesn't matter if it's out of date. If you are interested in learning, you will not be interested in learning.
If you are interested in learning, I have some materials here.
Msdn help manual MSDN_Oct_2001.iso
In-depth explanation of vc ++ video
Welcome to shoot bricks. If something is wrong, let's say it's just a personal experience.
This article is from the "Calm dreamer" blog, please be sure to keep this source http://idiotxl1020.blog.51cto.com/6419277/1288582