VB6 programmer: Where is the future? (See three myths)
Author:
Builder.com
Tuesday, July 23 2002 10:27 AM
The .NET occupied market speed is slightly slower than the original expectations, but it is inevitable to the entire market, and this process has never had any pauses. Many analysts predicted that in the third quarter of 2003, those mainstream software development companies using .NET will begin designing their first .NET application software. This transformation has a certain shock for groups that use Microsoft products, and now? 'This is closely related to the future of software development has also had an answer.
VB provides a convenient development method for millions of software development and designers. Microsoft has provided sweets in the process of providing sufficient powerful features to produce application software and allowing software developers away from Easible Windows and various development components.
However, the current situation has changed a lot. For .NET products, Microsoft has decided to create a development environment that is still separated by software development designers, but in this way, programming staff will have to deal with various components development. . Program development designers can continue their work as before, without considering pointers, memory allocation, or how to create a Windows message processor, but program development designers can no longer ignore such as namespace, overload, etc. Waiting for the problem and concept of related components.
When .NET has passed the early familiar phase, VB program development designers can only have fewer choices in the future, only have certain changes. This is a vibration on the development of language, and it also makes many commenters to guess what kind of response does the VB program develop designer will produce? Will they turn to use Java to continue their work? Will they continue to use VB and complete the jump of .NET? If this is this, will they choose C # or vb.net? Will they ask Microsoft to continue to support VB6 and keep it maintaining a certain development space? Will there be many program developers who cannot complete the transition will work in the way they make up the components?
I will not make any forecasts for these problems. But I think it is time to clarify the three myths around these problems.
Myth 1: .NET is a change in the basis, so transition to Java may easily be more easier.
In this regard, the FRANK E. Gillett of the Forester Research investigation has made the following discussion:
"For VB programmers, the transformation of the .NET is not more than the change in the work to work to the Java2 platform. What does this mean? For Microsoft, it is now re-considering redmond. Commitment, and re-evaluate the Java2, .NET platform, and various tools software. "
What we need to remind is: "Management should pay attention to that this practice will cost a huge amount of money, this is no one is willing to see!" If you can notice the infrastructure of these languages (especially In Java and C # languages), you can understand what this is coming. Therefore, it is similar or identical to the requirements of VB application software. However, there are many important factors to be considered. The following is just a subset of it.
The Java development environment is always more complex.
A number of tools that can be used in the Java environment, as one of the strong capabilities that have been confirmed, naturally leading to many new applications and tools (application servers, IDE, debugging tools) These are all software development designers must master. Every new skill has its own learning curve, even when these developments will be completed in a Windows environment. From another perspective, after many improved Visual Studio, it will feel simpler and easy to master for those VB programmers. They immediately understand how to set out breakpoints or how to use the functionality features that complete the encoding. Attempting to complete the development of language, development tools, and various infrastructure transitions, it is very likely to have to increase more capital investment, and the possibility of failure will be relatively high. Use .NET to enhance the feasibility of completing transformation
Most software development companies have their own acceptable deadlines, and in completion of the project's plan, it does not include a few months for completing application software and infrastructure transformation. The page of ASP.NET can run in parallel with the ASP page, and it can also share the management mechanism, however, if you want to complete the transformation of JSP, you need more effort to implement. The mechanism for calling COM objects from C # and VB has been explained in some articles, books or meetings. Com Services's combination is also very good recorded.
A large number of "from VB6" is also available
One thing that makes me feel very surprised, that is, only a few resources can help us complete the transition from VB to Java. Although I have seen some customer training courses to help people who have opened this shift, I have seen some relevant books (most of which seem to have an outdated knowledge now), but these courses And books are far less than helping to do this. As you may expect, there are a lot of books for how to complete the VB.NET and C # transformation, which contains very detailed various coding and skillful content. After having these materials, the program development designer can complete their transformation more quickly and more convenient.
I suggest that the following is an alternative to the myth:
Transition to Java is not like transition to .Net, it is simple, but if you consider going to make such a change, it is now the determination.
Since the event of VB, it is now requested that the programmer is changed to .NET, it is the largest change of Microsoft to make Visual program develop designers. If you have considered it to use Java, you must consider clearing the consequences of this and follows the fees.
Myth 2: A large number of VB program development designers will turn to use Java
In the past, these procedures develop designers turn to use Java one of the reasons that Java languages are far exceeding VB6 in terms of performance. This kind of advanced distance may be in light years, and Java is preparing large The performance of object-oriented applications is also particularly prominent. People can argue that Java is still a more appropriate choice for these tasks, but at least now, this problem is already a match. The answer to this question is no doubt before .NET appears. It is unlikely to implement powerful object-oriented design in a Visual environment. The ASP is a huge tap that often leads to a slow speed and often generates some program code that cannot be maintained. You can write a book about VB and ASP Antipalns. Of course, those who want to turn and use Java are due to their technical advantages. However, those who are ready to accept .NET have to be more than one of people who have access to Java, and to make them do these transformations, there are other factors, such as sales and considering security. Reason, etc.. I think that the future of VB program developing designers is very bright. There will definitely have a proportion of program development designers can't complete this jump. VB program developers have now begun to make certain adjustments to their roles they play in the development. One result is that they have become integrated with Excel's forms, and they are making single-screen tools; another result is that they are writing e-commerce applications that will be widely used. Some people in these software development designers, their interest, efforts, and capabilities will be at a level between VB6 and VB.NET. Retail may not be their future, but they can turn into a supportful role, no longer like the previous programmers. In addition to these people, most software development designers will also complete the transformation of .NET.
Mythology: If you are ready to turn to .NET, then you'd better turn to C #.
C # has its own name. It is very new, very cool, and it has become more hot. But different than the syntax of C language style, C # is basically the same as VB.NET. These situations have also been known from people. What is written here is that I have recently been a conversation record of the same C programmer, which is preparing to complete the transition from C to C #.
Programmer: "I don't understand why all people want to learn VB.Net."
Author: "Then why can not they learn it?"
Programmer: "There are many things that are VB.NET can't be done, but C # can do it."
Author: "Really, are you referring to what things?"
Programmer: "VB.NET can't do attributes!"
Author: "VB.NET can do."
Programmer: "Yes? Can you do it, but can it be Delegates?"
Author: "Yes, it can do this."
Therefore, there is also a certain misunderstanding in the professionals. Dan Appleman did a very good job when commented on this issue, his e-book Visual Basic .NET or C # ... Which one should you choose? Can be found on Amazon.com. There is a lack of support for overload and the XML file, VB.NET has all the powerful features owned by C #, but also add some additional functional features, such as it can provide complete real-time error detection, light This will make C # program developers envious.
I very much agreed with this sentence: "Since VB.NET and C # are so similar, make a decision may not need so many technical background." Perception is still a driving force in this market, and for program development For designers, C # is also a new field. If the action of VB.NET is not so fast, the emergence of third-party tool support is not impossible. C # It is possible to become a lot of VB programmers is not because it has a congenital advantage in technology.
Find the essence and core of the problem
Without these so-called myths to disturb our sight, we can further understand the essence of the problem. In the future, .NET will have support for software development designers who now use VB.
In the subsequent article, I will introduce some VB programmers who have completed the transition to Java, VB.NET or C # transitions. Moreover, I will also check that they will learn from their experience, and how to learn from their experience, how to make changes in the transformation be minimally, and how to turn into transitions at least funds.
