Asp. NET Novice Tutorials: A technical understanding of the misunderstanding

. NET is now popular and is the first choice for trendy programmers. However, a large number of just contact. NET programmer There is a certain misunderstanding, here to introduce a part.

A. NET program will be faster once it is run again

Many people interpret this as: when the. NET program is first run, it is compiled with cost code, so it is faster to run it again. But unfortunately, every time you run, those il will be translated once, will not be preserved. So it doesn't get any faster. But why does it sometimes feel so fast? In fact, all programs are like this, this is windows again for you to cache the used components. Really need CPU time of the program, more running is not faster.

Ii.. NET programs must be slow to run

Because there is a process where IL is translated into native code, the. NET program does consume a portion of the time. But. NET programs are still highly efficient, which is why many Java virtual machines are not comparable. Because most. NET programs contain very little code, almost all of them call the class libraries in the. NET Framework, which are all compiled into native-optimized local code when the. NET Framework is installed and saved in the assembly cache. With this assembly cache, most of your programs are actually highly efficient native code, so of course it's fast. However, if you do a lot of numerical computing classes, you can still feel the speed of the first operation is significantly reduced. So it is recommended that you separate the computationally intensive programs, compile the cost code and save it in the assembly cache, and then use it quickly.

C # faster than vb.net, more powerful function

It must be admitted that the C # compiler and the vb.net compiler do differ in the handling of some of the details, resulting in a general difference in the efficiency of programs that are similar in their compilation capabilities. But for a complete project, there will be no difference. The reason is that the first vb.net compiler does not have a substantial flaw than C #, and then most of the code is code in the. NET Framework class library, and the two calls are no different. As for C # is more powerful than vb.net, this involves psychological problems. VB is no worse than C #, there is no "grammatical confusion", "for compatibility and design" and other legends of the fault. With vb.net, you can write excellent, structure-perfect applications. And VB.net is also the only macro language of Visual Studio.NET.

There is also a problem, the famous Linux under the. Net--mono Support C # only? Of course not, the vb.net developed with the same program can be in mono correctly run. And the newest mono will include mono basic language, so that the person who grasps the vb.net grammar, can develop completely under the system such as Linux.

Four, Microsoft only wants to promote C #, he wants to give up vb.net

Don't listen to alarmist words. Microsoft is constantly promoting vb.net. The articles on. NET development on MSDN are more examples of vb.net than C #. Microsoft also specializes in the introduction of VB Technology Program--VBTV, to help developers better understand vb.net. When Microsoft lists the development tools in Visaual Studio, Visual Basic always comes first-this is Microsoft's 5-year tradition. So people who are worried that vb.net will be eliminated should be relieved now.

Microsoft uses. NET against Java, so I also want to support. NET, against Java

Do not have this idea, Ms of course want to occupy the Java market, Sun certainly do not want to, but this is none of your business. There is no real benefit to either side of winning. Let's learn from two. Instead of provoking an argument on the Internet, learn one more skill, and you'll soon see the rewards.

Well, from the next start, will focus on technical errors. Good luck to all of you.