Learning ASP. NET (2.0 as an example) series from 0 -- 04C #/. NET FrameWork/ASP. NET Basics

Introduction:

Preface:In the previous articleBlogBoyI have already shared with you about development.Development Environment and configuration of ASP. NET ApplicationsThen, can we directly discuss code writing? The answer for BlogBoy is: NO. We are a programmer and not a code machine. It is not a good habit to "Write it without thinking about it". We still have some foundations that are unknown. When it comes to the basics, especially WEB development, the underlying things seem to be both profound and dispensable. It is said that they are profound because the underlying things are widely implicated, and the aspect can be deep and shallow; it is dispensable because many people can complete the task well without understanding them. Well, these things have been heard many times, but BlogBoy still believes that the 0-Based ASP. NET enthusiast should better master some of the most basic things. Only by understanding, can he talk about it.

Let's talk about the title of this article. There may still be a lot of garden friends who want to spray it. It is true that if the title prevails step by step, it will be a big headache and challenge for BlogBoy to explain everything in detail, this is mainly because C #,. NET FrameWork, ASP. NET, to fully understand the basics, is not what the monks can do. ReadC # entry classic, ASP. NET2.0 entry classic, CLR via C #Readers of other related books know that it takes a lot of time and effort to master the technical details, but it is not difficult to grasp the general knowledge, in the future, we will be able to achieve better targeted reading or practice.

First of all, I declare that BlogBoy is not a title party. Although the title involves a lot of content, BlogBoy will try its best to make its own explanations as long as it involves things related to the title. The content involved in this blog is the basis, the so-calledBasicIt must be a simple and complex thing. Why do you say this? For example, I believe no one knows that 1 + 1 = 2, right, this is nothing more basic. But can you tell us why 1 + 1 = 2! Oh, isn't it tricky.It may be difficult to learn a technology, but it may be difficult to clearly express them in words or languages.BlogBoy really admired those blogs, not only technically, but also helped countless latencies. SO,The basics are not fixed in one or two articles.BlogBoy and readers both need to do a good job.Protracted WarPreparation (many readers may feel discouraged or lost, but if you calm down and think about it, which real "martial arts master" is not developed slowly, do the "Explosive masters" that fall into the cliff, take the wrong medicine, or reverse the muscles and muscles, and return to the Dead? Do they really exist in the program world ...... SO, let's take a look at common people !).

Body:

I think the previous article is very clear. For the following basics, BlogBoy will only selectWEB-related or important partsAs part of the explanation, in order to allow readers of the 0 base to better grasp the main pulse, I will introduce some related blog addresses in the outline.

Part 1: c # Basics

In this section, I think the knowledge and sequence that readers should master are as follows:

C # variables and expressions:If you are familiar with their usage and understand the memory structure of various variables and their conversion processes (a hot topic of type conversion is related"Packing and unpackingYou can find some insights and views on this part of the content at this address: http://www.cnblogs.com/mqsuper/archive/2008/08/12/1265520.html), then congratulations, you can skip this part smoothly.

Object-Oriented Programming philosophy:In fact, this part of content has nothing to do with the language itself. There are a lot of materials for reference. The hot topic is about"Design ModeReaders can refer to the following address: http://www.cnblogs.com/cj723/archive/2007/11/23/962823.html, BlogBoy personally thinkThe design pattern or programming ideology must be constantly refined in the project experience and code refactoring.But it's easy to get angry. Recently, garden has a related post discussing the design pattern.Advantages and disadvantagesYou can find out if you are interested.

Set, generic, and interfaces:For WEB development, You Need To frequently use some advanced objects, such as various lists, datasets, and interfaces. You can easily use these objects and interfaces or customize your own data reprinted objects, for more information, see the following url: http://www.cnblogs.com/wf225/archive/2008/01/14/1038104.html, BlogBoy think the object or interface to be mastered mainly include:DataTable, DataSet, IEnumerable, IList, ICollection, IDictionary, and IDisposeAnd so on.

File IO, GDI +:These are the foundations closest to actual programming. You will hear them here.Managed and unmanaged ResourcesConcept, you will know how to release memory resources in a timely manner, and learn a little drawing line and other code that is very exercise digital thinking, refer to: http://www.cnblogs.com/alex-bn-lee/archive/2012/01/22/2328793.html.

Debugging and exception handling:This is naturally very basic, and it is necessary to master it. For more information about this blog, see.

After reading the list above, some readers may ask: why is there no event orDelegate, Why notLing, Why notMultithreading, NoSocketWhat about it! (In fact, multithreading and Socket are not the foundation of C #, and Socket usage is more common in Winform scenarios. We will mention this because they are supported in C, it is also a hot topic, and it is easy to be misunderstood as part of the foundation .) First of all, I think these are not the first things that readers should master. Second, these things are not very common in common WEB websites (specifically "Explicit use", maybe garden friends will laugh at me and mislead readers ...... In my opinion, 0-based readers still need more experience to understand these things a little, and rashly using these technologies without understanding them may be counterproductive, or you may be stuck in learning this knowledge. Instead of stuck here, it is better to learn more general basics, isn't it !)

Part 2:. NET FrameWork Basics

CLR basics:Core features of CLR Common Language Runtime include memory management, assembly loading, thread synchronization, asynchronous processing, etc. However, these are not what you need to know now, the only thing you need to understand is a general understanding of the CLR running process and some new terms involved in the process, suchManaged modules, metadata, and intermediate code......, Retain some concepts for these new names for future use. Reference: http://www.cnblogs.com/artech/archive/2010/10/18/clr_memory_mgt_01.html

Stack and stack in. NET:The content of this section should not only stay at the level of concept, but should be strictly divided and understood in depth the differences between them. For readers with zero base, for the moment, you can simply think that. the heap and stack in NET divide our memory into two different parts. The heap is characterized by large capacity and slow speed. Therefore, the heap is suitable for storing data and complex objects, stack features the opposite. It is generally used to store a small amount of data and address reference of objects (if you understand binary and data structures, the effect will be better, but you can remember the stack differences in your mind ). Reference: http://www.cnblogs.com/paulxie/archive/2011/03/09/1978056.html

. NET garbage collection mechanism:There are many articles on the Internet for reference. Similarly, readers with zero base can focus on the differences between hosted and unmanaged resources, and how to manually release the unmanaged part (we are familiarCOM, GDI, IO, databaseAnd so on are all non-managed code, which is why many articles focus onIDisposeAndUsingUsage reasons ). Reference: http://www.cnblogs.com/riccc/archive/2009/09/01/dotnet-memory-management-and-garbage-collection.html

Part 3: ASP. NET Basics

Principles and processes of page requests:

ASP. NET operating mechanism:Pending completion

HTML + CSS + JavaScript:Pending completion

Various files on the ASP. NET Website:Pending completion

Some major server controls:Pending completion

Ajax in ASP. NET:Pending completion

 

Conclusion:

Due to the time relationship, ASP. the basics of the NET part are not written, but a rough directory is listed. In fact, the content of this part is still relatively important, and the entire article is also messy. How can this problem be solved,There is no such thing as gold, no one is perfect, and you can live your wonderful life!BlogBoy will be supplemented in other times. Please do your best! I 've been tired recently. I just got a break ......