Summary of several important misunderstandings in. net Development

1. the. net program runs faster once again

Many people explain this: the first time the. net program runs, the code will be compiled at cost, so the re-running will be faster. However, unfortunately, the IL will be translated once and will not be retained. So it will not become faster. But why do you sometimes feel faster? In fact, this is the case for all programs. This is another component that Windows caches for you. For programs that really require CPU time, multiple operations will not speed up.

Ii... net program running must be very slow

Because of the process in which IL is translated into code, the. net program does take some time. However, the. net program is still very efficient, and many Java virtual machines cannot match it. Why? Because most. net program contains very few codes, almost all of which are called.. net Framework. net Framework is compiled into local code optimized by the local machine during installation, and stored in the Assembly cache. With this Assembly Cache, most of your programs are actually efficient local code, so of course it's faster. However, if you perform a large number of numeric computing operations, you can still feel that the speed of the first operation is significantly reduced. Therefore, we recommend that you separate computing-intensive programs, compile the code at a cost, and save it in the Assembly Cache. It will soon be used.

III. C # is faster and more powerful than VB.net

It must be admitted that the C # compiler and the VB.net compiler are indeed somewhat different in terms of processing some details, resulting in a difference in the efficiency of programs with similar compilation functions. However, for a complete project, there will be no difference. The reason is that the VB.net compiler does not have any substantive defects than C #, and most of the Code is the code in the. net Framework class library. There is no difference between the two. C # is more powerful than VB.net, which involves psychological issues. VB is no worse than C #, and there is no such thing as "syntax disorder" or "design for compatibility. Similar to VB.net, you can write excellent and well-structured applications. VB.net is also the only macro language of Visual Studio.net.

There is another question: does. net -- Mono in the famous Linux only support C #? Of course not. Programs developed using VB.net can run correctly in Mono. In addition, the latest Mono Basic language will be included. In this way, people who have mastered the VB.net syntax can develop it completely in Linux and other systems.

4. Microsoft only wants to promote C # And he wants to give up VB.net

Don't listen to worries. Microsoft is always trying to promote VB.net. On MSDN, there are more articles on. net development, using VB.net for examples than using C. Microsoft also launched the VB technology program VBTV to help developers better understand VB.net. When Microsoft listed development tools in Visaual Studio, Visual Basic always ranked first-this is a five-year tradition of Microsoft. So we are worried that VB.net will be eliminated. Now we should be relieved.

5. Microsoft uses. net against Java, so I also need to support. net against Java

Do not have this idea. MS certainly wants to occupy the Java market. Sun certainly does not want it, but it is none of your business. If either party wins, you will not have any substantial benefits. Let's learn both. Instead of initiating a debate on the internet, you should learn more, and you will see a return immediately.

Now, we will focus on the technical mistakes from the next time. Good luck.