Author: Steve Scott compilation: SnowedForest
Can publish a Microsoft Visual Studio article on a magazine who is often flying Delphi developers, which can be seen as a good opportunity for a day, or a glass of wine. When I wrote this sentence, I still don't know what I do. But as a developer, I have been holding this attitude: I have to use the best development tool in my work. In the past six years, I have almost all with Delphi. Even if we are trying to achieve the latest Microsoft technology (like COM, MTS, ASP and ISAPI, we still say that we are using the best tools, this is also my love for this development tool. With VS7, what can we keep this view when we say in front of us now?
On the occasion of the details of VS.NET, I would like to state such a fact: I can almost describe the specific form of the next Microsoft development environment before VS.Net is released later this year. (Because) VS.NET Beta 1 was available for free before November 2000. In the public news group, members of the development team often appear, and anyone can report the bug they find.
This is too obvious compared to Borland to the beta processing method. If you know someone is testing the Beta version of Delphi6, they may have not mentioned you, let alone this product is discussed. I believe that Borland has a good reason to handle software release, but I still can't understand them. Although I am not coheed with Microsoft, and in fact I have never used the current version of VisualStudio, but I really want to do something for its next version, you can add it to it to a certain extent. Now I feel that I am a little bit, I have the opportunity to bring this version with the characteristics I suggested, but this hope is definitely very embarrassing, but this kind of participation makes me like this product.
In contrast, I think I am like a bun, sitting waiting for Borland to tell me what I want in Delphi6. Unfortunately, the software's (pre-) perception accounts for an important role in its release failure, in this point, Microsoft wins. In addition, Delphi6 is likely to be released while VS.NET comes, but now I can only make a comparison of VS.NET and Delphi5.
Well, what is the difference between vs.net and current version? Different, this is more tempting. VS.NET is not an improved upgrade of Visual Studio. As its name, it is a development environment designed for Microsoft .NET architecture. In fact, I think unless you use Visual C (by way, it is not very high), otherwise it is impossible to develop standard API-based applications. (I have to exclude FoxPro outside of my conclusion, because I don't know which location it is suitable for this environment). VS.NET is worthy of the .NET architecture as its goal, providing a unified road to solving various problems, this is a fact. The most important thing is whether you are willing to develop the .NET framework as the preferred.
As a developer using Delphi, the closest thing we can compare with the .NET architecture is VCL. Microsoft spends a lot of time (more than 3 years) to develop a language-neuttical (NEUTRAL OBJECT) package Windows API. This package, or the architecture, also expands the fields including memory management and abnormal processing, also dominated in other products. Briefly, any language that uses frame design will get functions such as garbage collection and abnormal fault tolerance, and it can also make full use of any other .NET compatible language. First, the architecture will be released as an additional patch of Windows 95, 98, NT and 2000, which will become a complete portion that makes up the future Microsoft operating system. We guess Microsoft may no longer publish the Windows API at some point in the future, and only allow access to the operating system through the .NET architecture. Thinking of this, the question of our question will be released - the problem is not whether you want to develop .NET application software in the future, how long before you turn to .NET. This is a bit like a few years ago, the Windows 3.1 and the Windows95beta version, we still remember this. And the reality is, no matter what some people have previously said, almost no one is still developing under Windows3.1.
As you can see, because Visual Studio.net and Delphi 5 are for different platforms, it is not reasonable to make comparisons. When Net is released, Delphi 5 is as big as the difficulty of turning Delphi 1 into Windows 95. I mentioned that Borland did not formally announce any plan about support .NET architecture, but there is a message from Borland says Borland will support .NET architecture, and be closely combined with MS to ensure that Borland can complete this function (support .NET (AND Yes, MR Lawyer, We Have Permission To Say So! ED), however, until now they have made a formal declaration, start providing Beta, but now everyone is in addition to Visual Studio, in .NET How much room is reserved (for testing Delphi)?
I show up: I said that I think .net is the future hope, then what is VS.NET provides us to achieve this hope? These products include VB.NET, which is completely rebuilt, current VB and it is not comparable; there is also a new language called C #, based on C language, but removes its muddy, and absorbed other languages such as Java, Pascal A large number of essences such as languages. These two language functions are very powerful, support single inheritance, events (in proxy form) and attributes. I haven't found these two language limitations, even though I don't want to find (I left this kind of thing to Dave Jewell).
All .NET languages, including VB and C # to generate Microsoft's so-called neutral language or il, this is a must-have condition. Then .NET Public Language Run Time (CLR) uses IL and generates a machine code. This result is that the difference between various .NET language execution time is not sensing because they use the same final Just-In-Time compiler.
Because all the functions of the language are provided by the architecture, you have to choose which language (better) is completely decided by your preferences for the language syntax. I am now mainly using C #, it is also the masterpiece of our old friends - Andrs Hjelsberg, .NET architecture is also written by C #. Here I want someone to make some people feel uneasy: If Borland forced me to use a language other than PASCAL, I think it is good to use C #. The current Visual Studio .NET speed is quite slow, it is a bit blamed. But it is just a beta version. Its integrated development environment (IDE) is also convenient, but I have to say that I prefer Delphi's IDE. I don't want to launch a review about IDE here. This is just to say that if I have to use IDE, it must be convenient to use, and it is much better than Notepad.
Obviously, VS.NET supports numerous new engineering types to support new features on the .NET architecture. In the past, the messy ASP refer to the face became an ASP.NET. Once Microsoft has found alternatives to a certain technology, the old abandonment will be given. I have to say that Microsoft is very good at this. ASP was once the flagship developed by Microsoft networks, and when ASP.NET came, it was obvious, ASP was a bit stupid, and it was inconvenient. For the words, the ASP.NET looks really good, it has been included in the necessary list of I will develop tools. The control capability for your own server is a problem worthy of in-depth research. If you are a network development, you have to pay attention to this technology. Network services are also .NET important part, vs.net makes it easy to develop network services. Microsoft believes that network services are the core of future distributed applications, this is only proven, but (at the same time) I think the application field of network services is very broad.
Until at this time, I mainly focused on the new features available in VS.NET, which is much in vs.net. However, if it is considered to be .NET is only related to the Internet, it is wrong. The .NET architecture provides a unified component main body for the traditional single-tier and multi-tier (N-Tier).
As we can expand Delphi's VCL, we can now do the same matter in vs.net. This is really a heart. You can inherit a standard .NET class, use VB to expand it, and finally use C # to inherit your new VB class. When you debug, the debugger can walk through VB and C # code. In VS.NET, language will no longer be obstacles. So far, the only thing I feel disappointed is the source code of the .NET architecture itself. I don't know that it will not be published in the future. If you can, it will be fine. For years, many traditional Microsoft tools have always been talking to our Delphi developer (developed app), but it is clear that Microsoft will catch up with some aspects.
In short, despite so much improvement, VS.NET looks like Visual Studio (but don't forget this is just a beta version, who knows which differences will there be a final release?). However, in front of the traditional Windows application developed in Delphi, the application generated by VS.NET will be a refreshing thing and way.
I personally think that in the past six years, there is no common Windows development tool more energetic and practical than Delphi. Today, as the .NET world impacts to us, I suspect whether there is something more vital than .net. I hope that Borland will be awake in this new period, don't be too uncomfortable, but also have a business color and doubtful (my personal point) Linux, and the like is bleed. I will develop .NET app if I want to do this, I will use vs.net. But I am more willing to see Delphi.net. Since Microsoft has released this technology, it is like it to come to us in the middle of it. This is more troublesome. This means that Borland must speed up the progress. I will emphasize again: fast. We have long seen that developing products such as Paradox and DBase for Windows have been thrown behind from Microsoft competitors.
Postscript: This is translated before Delphi6 released. I didn't want to put it. But still put it up, I hope to learn from everyone.
