C # Programming Summary

To be honest, read the Zhu Guangming C # video tutorial, feel a bit messy, but the general design of things are still there. I've integrated what I've been involved with in my own understanding.

Zi Yue: "Learning and time learning, the joy?" "It's really a happy thing," Wen told the new. C # Early Learning has passed, but the delay has not summed up. So when learning design patterns, only to find that there is no C # foundation, design patterns are difficult to learn. Lucky to learn a little more seriously, so relatively learning is still effortless. Just have an individual knowledge point has the impression, but still do not want to come. This needs to be reviewed again.

It's easy to understand that C # has been seen. Before this, we learned VB, the computer language of all aspects of knowledge has a certain understanding. Computer language is all figured out, like English and Chinese, are used to communicate, take apples for example, but the difference between "Apple" and "Apple", refers to the same thing. VB we learn the data type, constant variables, arrays, three structures, object-oriented knowledge also involves a point, operators, strings, exception handling such knowledge is also involved. These "apples" are always there, but in another computer language it may become "Apple". But the only thing that is a bit regrettable is that VB is based on objects, and some of the code we write is process oriented. From the beginning of the design of small procedures to later works show The big program to student information management system, computer room charge system. We are used to the process-oriented code. So it was a little bit of a circle to face the image. It's hard to say that it's just a little difficult here. None of the rest is yet. Know this point, then learn not to have targeted it? Now I feel that object-oriented is more holistic, independent and easy to understand than the process of orientation.

Some of us have learned the C and C + + languages before, which is easier to understand. C + + is itself an object-oriented language, and its contents are similar to that of C #. Look at the picture below, and I thought about what I learned from C + +. The new knowledge only adds so little.

Let's talk about my understanding of C #. In fact, it makes sense to say that C + + is similar. C # is the component-oriented language for the latest trends in the C and C + + language families. It is from C and

A simple, modern, type-safe object-oriented programming language derived from C + +. I didn't say much about what it was designed for, and most of it was figured out in other languages. A picture has been visualized to illustrate everything. Basically, it's very similar to C + +. In my blog about C + + summed up more than 10 blog posts, you can find through this link. http://blog.csdn.net/qwlzxx/article/details/38065571.

If you are careful, you will find that there will be a UML diagram, we have learned the UML diagram, and now know that it can interact with C #. You can convert a class diagram to code, or you can convert object-oriented code to a class diagram. This can also be done through vs software. About UML, the blog is also introduced, can be found through this link. http://blog.csdn.net/qwlzxx/article/details/41522465

New knowledge points, such as delegates and events, will be summarized in detail later in the study of design patterns. Please look forward to!

C # Programming Summary