Guide: Each organization migrates to .NET will choose which .NET language. Microsoft provides four languages: C #, VB.NET, manageable C and JScript. This article briefly discusses what we will use on these languages and which language will be used.
Translation finishing: 51DotNet.com (high flying family)
Original source: http://www.dotnetdan.com/articles/misc/languagechoice.htm
Each organization migrates to .NET which .NET language will be selected. Microsoft provides four languages: C #, VB.NET, manageable C and JScript. This article briefly discusses what we will use on these languages and which language will be used.
In short, we believe that C # will occupy the main market share; JScript is not competitive; C will be ignored, VB.NET shows deficiencies to the market.
Loser
Jscript
We hope that JScript ends its mission on the basis of very few users. Nowadays, there are few information about this aspect and in the .NET Forum, there is no significant content on JScript. It is no longer mainstream. Don't give money to this technology, give it to it is the most sensible.
Manageable C
C , even if its new manageable form will gradually be neglected. When more and more developers tend to grammar clear languages, such as JScript, Java, VB.Net, and C #, the C circle is getting smaller and smaller. Another problem with C is that he cannot be a teaching language. Undoubtedly, despite this, experienced C developers will continue to use its capabilities, template, multiple code inheritance and decisive final determination. The rest can be easily coping.
Victor
It is exactly here that it should be a winner. Because we believe that C # is the only true victory. VB.NET is in an unmanned situation.
C # has quite advantages
Most professional software developers, even in independently developing Microsoft platforms, there will be some form in some Java languages.
Java is more advantageous to C and VB6. He went to a lot of C syntax characteristics without reducing its function (so C developers turned to use Java very easy). It is better than VB6 in terms of object-oriented tools.
Java occupies the highest status in most mainstreams in most mainstream in a productive language with its clear object-oriented syntax structure and huge libraries. For this reason, many C and VB developers who are good at object-oriented technology began to transfer to Java.
C # provides a basis for the development tools that have not been supported by Microsoft. In fact, it is consistent with Java, but only in their differences, C # has shown it uncomfortable advantages. In addition, it is a language of ECMA standards, so it provides potential capabilities across multiple platforms.
Serious speaking, developers want Microsoft's most productive and mainstream .NET language, C # is the most sensible choice.
VB.NET is isolated and helpless
There is also a VB.NET. Why do we still make questions about Microsoft why only make VB.NET a more complex C # and ask questions. Perhaps the historical background of these two languages is the key to knowing this shift, but we have to discuss technical problems rather than market problems.
undoubtedly, VB.NET has grown to a new stage. It has now become a member of the rapid growth of an object-oriented club. But who is care about it now? Perhaps a group of people who are dissatisfied with their dissatisfaction and non-faced objects, but they will get it immediately. With the generation of C #, VB.NET looks more like an outdated product, not improved.
Dechand Code Generator generates code in VB.NET or C #. If you choose a VB.NET option, you will get a file, it and C # implement the same function, but it is about 33% more than the file generated by C #. When you read the code written by VB.NET, a lengthy statement will bring a lot of trouble. When we combine this with the reasons mentioned earlier, we can only hope that there is an experienced object-oriented developer should like C # more VB.NET. So what kind of market will lose VB.NET? The current market has enabled software companies to use VB as a development tool, and a large number of VB enthusiasts. Unfortunately, it is not that VB.NET is not It is developed for these people.
Transplantation from VB6
Using the VB writing program may be expected to be updated from VB6 to VB.NET, and it is easy to easily like existing VB upgrades. Unfortunately, they may be hit by a harsh. Although there is already a tool that can be automatically completed, it will be more tired to upgrade to VB.NET.
As mentioned above, VB.NET is an object-oriented language, while VB6 is not. The problem is that if you don't think about object-oriented, many organizations are doing this, you can't experience the fun of VB.NET conversion experience. Because this is not just a structure, it is a modest change, and this shift is very expensive. Many organizations may feel that if they want to change their thinking, they are not as good as changing the language. If VB.NET is eliminated soon, it is not surprised.
Over the past, there is a brilliant fan of life
The final market segmentation creates a fan. For them, VB6 is an alternative language. It provides a simple and powerful tool to build simple applications including Guis.
VB.NET is not as simple as it is. As we have said earlier, it is a powerful object-oriented language. But for general enthusiasts, they don't want to know about '-ism' and abstract transactions in the object-oriented domain. They only want to complete a task as soon as possible, and ignore the fineness of our professionals.
To this end, these VB enthusiasts may not continue to use VB6 any more, or they don't have much hope for it.
VB.NET's future
The above annotations are only a small part of the publicly released .NET Beta. When we see the ultimate .NET product distance now has a considerable period of time, Microsoft will use some of them to produce Visual Studio.NET features hidden VB.NET complex Visual Studio.NET feature. We can only wait for it. What we can't do this, I can only believe that they can do, in order to develop, let us give Microsoft to love the traditional, so they will do more efforts.
About the execution of the runtime
If you see this is far from what you think, you may ask "What is the performance?" When you decide which language is faster, this is everyone. It is naturally asked.
There is no doubt. Net completely excludes those standards.
In order to understand why .NET language will run as fast (or slow), we need to look at the compiler, or it is exactly the compiler of two phases.
The first phase occurs when you use Visual Studio to press Ctrl-Shift-B keys. At this point, perform a compilation, your language compiler is creating an intermediate language (IL). The second phase occurs when you run the app. The second phase is sometimes seen as JIT compilation (we will feel strange, but we can't explain). It uses IL and generates local code in particular using the CPU.
Microsoft is not optimistic about the code generated by IL compiled in the first stage. Instead, they began to extend all their capabilities to optimize the second phase IL --- local code compilation. They do this to make language unknown reasons. All .NET languages are the same on the execution of runtime.
About debugging and compiler support
Visual Studio.net provides the same complex debugging and compiler using tools for all languages. When you decode the Managed C , you will not see something more detail, for example, compared to other languages. You can reach the depth you want to achieve. Similarly, the automatic completion method is also applicable to other languages. Summary
If you want to find a safer method, then use C #. We are sure now VB.NET's function is so powerful, and C # is even more, choose it, you won't regret, because we have clearly described its production performance to you.
