To elaborate on VB. NET (Next)

To elaborate on VB. NET (Next)
(Author: Green Apple Studio compiled March 07, 2001 14:47)

Forms and new IDE faces
Visual Basic.NET is a great object-oriented feature, but it was not noticed the first time you started vb.net. Perhaps the first thing you notice is its IDE. The IDE may seem familiar to you, the team that built the Vs.net IDE was working on developing the IDE for VB, and the IDE's enhancements draw on the experience of the VB IDE.

At the same time, the IDE's changes are far more profound than the appearance. All. NET language uses the same IDE, and the new tools in the IDE are powerful and easy to understand. You can set any design window to be automatically hidden (as you can automatically hide the Windows taskbar), which greatly reduces clutter. The main work area is a series of tabs, which means that the IDE no longer explicitly multiple forms and code modules at the same time. When you open the source code for an object, the IDE adds a new tab to the working object in its main work area.

The IDE also includes a new window called Task List. Its contents consist of projects created by the IDE. For example, if you receive an error while trying to compile a project, VB creates a project in the task table to explain the error. You can add items directly to the task table, or you can create a connection between the code location and the task by starting a comment line in the code with "TODO:". I love how Microsoft implements the Task table, and what needs to be done before the program is released? I guess it will save me a lot of time and trouble. When you see it, one of the easiest ideas you have is: How come no one thought of it before?

Another change you can notice is this: the VB.net form. Microsoft has discarded the old form engine and replaced it with Windows Form. All CLR-based languages use the Windows Form engine. It has several important improvements relative to the VB6 form engine. For example, Windows form allows you to create a form that automatically adjusts the size of a component and allows the control to be anchored to a specific location in the form. In other words, it is no longer necessary to use a Third-party control to accomplish these special tasks. Windows form also allows you to perform cool techniques such as transparent forms.

In the past, VB hides all the magic of creating a form. You use the IDE to design the form and add the code to the Initialize event, but you have no means to control the process between the two points. Now, the form is a class that contains all the code that is used to create the form. I call this code fertilizer code, because most developers want to leave them far away, as far as possible. There's no better way to break your program reliably than to toss the code. On the other hand, skilled users can do a lot of cool things with this code, because it allows you to go behind the scenes of vb.net forms. If you don't want to see the code, you can't look at it, because the new code editor has the ability to expand and collapse the code area, and the fertiliser code is collapsed by default. The Code Editor also has several cool new features. For example, now it automatically indents all the code for you (and does a good job), and it has a built-in display line number feature.

To create a compiled server-side code
In addition to the new Windows Form engine,. NET also includes a form engine that is specifically designed to create Web forms. These forms, called Web form, are smart, just as VB makes it easy for you to create forms for traditional Windows desktop applications, which make it easy for you to create forms for the web. The Web form is an ASP. NET technology allows you to create a form with code using a familiar RAD tool. The ASP.net code created is compiled and resides on the server, where it is executed, and then sent in HTML to any browser that supports HTML 3.2.

The underlying structure captures the event data on the client and sends it to the server. This means that you can use the various user interface tools to leverage existing form design techniques, and the application interface is not dependent on browsers. If you can give up without relying on browsers, you have another option to take advantage of some of the features unique to Internet Explorer. Web Form makes it easier for Web-enabled applications to create better, richer user interfaces.

Web Service Policies
Vb. Another important web-oriented feature in NET is: Web services. Microsoft's marketing Department lists Web services as one of several big reasons to adopt. NET. In fact, the essence of a Web service is a COM-like object that is provided by a Web server using a standard protocol. Note that technically they are not COM objects, but they are similar to the way COM objects behave. Microsoft wants to see all companies using Web services, and future applications can simply "glue" to different Web services, just as you can now use visual Basic for Applications (VBA) Create a solution that is based on office and programs that support VBA.

On the PDC, a demo program provided by Microsoft provides a good example of how it wants developers to "stick" to these services. In this demo, an imaginary clinic provides an appointment system through a Web service, demonstrating how you can use a smartphone to make an appointment via the Web. Visual Basic.NET will even allow you to query the server and get relevant data about all Web services that the server can support. With IntelliSense dropdown This absolutely useful tool, programmers can access Web services. Web services are an ambitious strategy for Microsoft, but only time can test whether it succeeds in being widely accepted.

Microsoft is trying to eliminate problems associated with wrapping and distributing applications, including scary DLLs. All. NET application is encapsulated as a component. A component contains data to describe what it needs to run. This data is called the manifest, includes a lot of information, such as symbol identity (name, version, and so on), a table that lists dependencies between all files, and their location and version, including external dependency information for DLL-related data, and other components that developers do not create. Components are self explanatory (through their manifest), so. NET applications do not need to modify the registry to work. In other words, you no longer need the registry component. In the best case, that's already in the client. NET runtime, distributing a complex application may simply be a matter of copying a folder to the target machine. Another benefit of components is that you can have different applications use different versions of the same DLL and run them in a coordinated way on a single machine. If all this works as planned, the nightmare of the DLL's Hell and version will be the past.

The right way
Microsoft has completely updated its technology, not just the core language. For example, the Ado.net is also available in Visual Studio.NET, which is the next generation ActiveX Data Objects (ADO) version with special advantages. One of its flexible changes is that Ado.net uses extensible Markup Language (XML) as a format for passing data sets between components. This means that the receiving component does not necessarily have to be a ado.net component, and that the receiving component can accept any XML-formatted dataset. When it comes to XML, it supports anything in vs.net, from configuration files to remote procedure calls. Ado. NET performs better than ADO in processing disconnected datasets and is more scalable.

Visual Basic.NET has made important changes to VB that we are all familiar with. C + + revolutionized the leap to. NET has a new name: C #, and the name of Visual Basic does not change. However, it may be easier to master vb.net as a new language of grammatical similarity rather than a simple "upgrade". This article gives you a starting point, but it is a difficult process to absorb all kinds of knowledge and make a decision based on the future, it is just a starting line of this process. I do not know. NET is so successful, it attracts me in many places, but not in some places. This tool has made a lot of promises, boasting many features that make it easier for VB developers to create more scalable high-end applications. Finally, its success will depend on how well developers can apply it to the real world. Looking at Microsoft's stride over performance and stability between the PDC and Beta 1 releases, I firmly believe that Microsoft is on the right path!

< finished full >