I said VB. NET (lower) (Author: Green Apple studio compilation, 2001 at 14:47 on March 7) forms and faces new IDE Visual Basic.NET object-oriented features are great, but the first time you start Shihai careful not to VB.NET To it. The first thing you may notice is its IDE. IDE seems to be familiar, and the team that establishes VS.NET IDE's previous work is to develop VB's IDE, and learn from the experience of VB IDE for Ide. At the same time, the change of IDE is far more than the exterior display. All .NET languages use the same IDE, and the new tools in the IDE are powerful and easy to understand. You can set any design window to automatic hide (just like you can automatically hide the Windows Task Bar), this greatly reduces confusion. The main work area is a series of tabs, which means IDE no longer explicitly explicitly explicitly a plurality of forms and code modules. When opening the source code of the object, the IDE adds a new tab to the object of its main work area. The IDE also includes a new window called a task list. It consists of items created by IDE. For example, if you receive an error while trying to compile a project, VB creates a project in the task table to explain this error. You can add a project directly to the task list, or start a comment in the code, you can establish a contact between code location and task. I like Microsoft to implement the task table; what do you need to do before the program is released? It is estimated that it can help me save a lot of time and trouble. When you see it, an idea you easily produced is: How did you think of it? Another change you can notice is: VB.NET's form. Microsoft discards the old form engine and uses Windows Form instead of it. All CLR-based languages use Windows Form Engines. There are several important improvements relative to the VB6 form engine. For example, Windows Form allows you to create a form that automatically adjusts component sizes and allows controls to be anchored in a specific location in your form. In other words, these special tasks can no longer need to use third-party controls. Windows Form also allows how cool technologies like transparent forms. In the past, VB hidden all the magic of the creation form. You use the IDE design form and add the code to the Initialize event, but you don't have a means to control the process between these two points. Now, the form is a class, which contains code used to establish a form. I called these code as fertilizer code, because most developers hope to leave them far, the farther the better. To rely reliably decrease your procedure, there is no better way than tossing these code. On the other hand, technical skilled users can do a lot of cool things through these code, because it allows you to go behind the VB.NET form. If you don't want to see these code, you can also see it, because the new code editor has the function of expanding and folding the code area, and these fertilizers are folded by default. The code editor also has several cool new features. For example, it is now automatically replaced with all code (and also working well), and it has built-in display line number function. Creating a compiled server-side code In addition to the new Windows Form engine, .NET also includes a form engine that specially designed to create a web form. These forms called Web Form are very smart, just like VB allows you to easily create a form for traditional Windows desktop applications, allow you to easily create a form for web. Web Form is the technology in ASP.NET that allows you to create a form with code using the familiar RAD tool.
Created ASP.NET code compiles and resides on the server and is executed there, then sends it to any browser that supports HTML 3.2 in HTML. The underlying structure captures event data on the client and sends it to the server. This means that you can use a variety of user interface tools, you can use existing form design techniques, and the application interface is not dependent on the browser. If you can abandon your browser, you have another option to use Internet Explorer's unique advantages. Web form enables support for web applications more easily to create better and abrupt user interfaces. Another important web-oriented feature in VB.NET is: Web service. Microsoft's market departments collect Web services as one of the reasons used .NET. In fact, the nature of the web service is the use of standard protocols, and is similar to the COM's objects from the Web server. Note that they are not a COM object, but the expression of COM objects is very similar. Microsoft wants to see all companies use web services, and future applications can simply "stick" on different web services, just like the Visual Basic for Applications (VBA) is now established based on Office and support VBA programs. The solution is the same. On the PDC, there is a good example of a demo program provided by Microsoft on these services on how it hopes that developers are "sticky". In this demo, a virtual clinic provides an appointment system through the web service, demonstrating how you can use the smart phone through 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. The programmer can access the web service through the absolute useful tool of IntelliSense Dropdown. Web services are a ambitious strategy of Microsoft, but only time can test whether it can be successfully received. Microsoft tries to eliminate issues related to packaging and distribution applications, including fearful DLLs. All .NET applications are encapsulated into components. Components contain data to describe what it needs to run. These data are called bills, including many information, such as components (name, versions, etc.); a table listing the dependencies between all files, and their location and version; including DLL related data External dependency information; there are other components that need to be needed and the developers have not created resources. Components are self-destruction (through them), so .NET applications do not need to modify the registry to work. In other words, you no longer need registry components. In the best case, when the client has a .NET runtime, distributing a complex application may just copy a folder as simple to the target machine. Another advantage of components is: You can let different applications use different versions of the same DLL and coordinately run on a machine. If all of this works like the plan, the nightmare of the Hell and version of the DLL will become the past. The correct way Microsoft completely updates its technology, not just a core language. For example, ADO.NET is also available in Visual Studio.NET, which is a next-generation ActiveX Data Objects (ADO) version of special advantages. Its flexible change is: ADO.NET uses EXTENSIBLE MARKUP LANGUAGE (XML) as a format that passes the data set between components. This means that the receiving component does not necessarily have to be an ADO.NET component, and the receiving component can accept the data set in any XML format. Talking about XML, it supports anything in vs.net, call from the configuration file to the remote process. ADO.NET is better than the performance of the ADO when processing disconnected data sets and has better scalability.
