Introduction: A few days ago, I received a letter from a beginner .NET, I would like to ask me some experience in learning .NET. Just, I have always wanted to write something about learning myself, I hope I can help some lovers who are interested in .NET.
I don't know that your current difficulty is to develop technology or just a strange to the IDE environment. As for now, it is now in Shenzhen. Net training, I don't know, now in addition to the training of North University Jade Birds in IT development, other training institutions have never heard of this short-term training, I am not very good. After all, it is easy to get through our own learning and online check. Since you asked, then I have a right to come back (should come over the middle, when working :-)), talk about some of the experience of the .NET, and recommend some .NET's technical resources.
If you used to develop (OOP), it is time to make this basic knowledge, this thing is actually very easy, in the general C / C # / VB.NET language tutorial book There are mentions in it. Because we use .NET to develop applications, more or less will involve database operations, especially in the Management Information System (MIS), then all front-end technology in .NET is stored and stored with ADO.NET. Operating database resources, ham is also one of our focus and foundations in our study. I only recommend a book in this regard. "ADO.NET technology insider" [http://www.china-pub.com/ Computers / Common / Info.asp? id = 14096]. For more details, see the system.data namespace in MSDN.
In various languages in .NET use the same set of APIs, ie .NET Framework, so understanding of this huge library is naturally the basic skills we have developed. When you come into contact .NET Framework, you may make you feel at a loss because of the complicated branches of the architecture, in fact, this is just confused by its surface, because .NET Framework organizes all classes through namespace (Namespace). These classes are logically nested in the namespaces of these slots by namespace layers, so as long as they organize our learning, you will find that this is a smooth and natural thing! Before studying this "great" architecture library, I suggest to deal with it first, here, here, I will recommend ".NET Framework program design (revised)" book [http://www.china -pub.com/computers/common/info.asp?id=13534] This book is for every important thing and fundamentality of each .NET developers, just look at this When this book, maybe you will have a lot of unknown places, then you don't worry, don't worry, because this is not a guide to teach you instant operation or test a technology, it is related to the architecture Something such as design or principles, this may be a bit boring, but I think it is the cornerstone of our technology. As a result, you don't have to be annoyed and depressed for the frustration, because I started in 2002 (the Chinese version of the book just came out), until today I still see, every time I look at it. Different understandings and discovery. If you want to know how delegate and event work? Why is it designed to look like this? How does the CLR run? How do our classes loaded? How does .net find the reference library? What is a strong signature? How is the reflection work? Wait ... Too much more interesting questions, if you want to get the answer to these interesting questions, then everything is in the book.
Finally, it is about learning entry points. It is true that such a large .NET Framework, we should always have a selective to learn, because there is no energy and time flowering everywhere. You can decide whether you start learning from ASP.NET or starting from the ASP.NET or starting from WinForms, no matter where you choose, you must do it, you must do it, you need to know some. In XML WebService shuttles, the deeper understanding of these basic things for HTTP / SOAP, the more you feel like a fish in the web development process, such as tiger to add. If you start starting from WinForms, you must be sufficient for each common control (inherited from Control) and components (inherited from Component) for System.Windows.Forms's namespace. In the client data binding operation, you may find that you know how urgent Binding, BindingManagerBase, DataGrid, and related classes (DataGridTableStyle, DataGridColumnStyle), and whether it is in WinForms or ASP.NET's programming Binding technology may be one of the technologies you have to master. Finally, about XML, because XML is such a prevail, because it is the basis of many technology stores in .NET (such as the storage and expression of Dataset in ADO.NET, the webservice carrier, even yours) Sequence expression and carrier of class), so I want to turn it vice versa. Then when you really do it yourself to try XML, the DOM model (System.xml namespace) may be a good object you quickly start, and we don't forget to have XmlReader, Xmlwriter, and their derivative class. It is an embodiment of two ways to manipulate the XML. For XML, it is not possible to be XPath. It is like the development of our database development, and the SQL language is our importance, of course, unless you decide all in XML. , Positioning, confident, conversion, etc. use cyclic judgment to get it. If you have something to hear, or some interest in design mode, then you suggest you look at MSDN's help, when you learn these .NET Framework class, think about why it is this? Ask yourself why they want to design it into this? When thinking about these problems, you are actually the charm of understanding and feeling, maybe you will suddenly swear: Oh! It turns out that this is a certain in the design model ~ you see that all this happens so natural and not moving color ~
