Home--> Articles -->Site Tools
Post By kwdez on 2008-9-26 15:40:52 [Reads:264]
ASP.net:Vaporware or reality?
Did Bill Gates announce the launching a few weeks ago, officially of. CLEAN (Dowry NET). Many analysts, often persifleurs, shouted to the vaporware again. Then, since the following day, Microsoft announced its will to create a new language the C #(C Sharp). Some immediately named it the J--. Last week (of the 11 to July 14, 2000), in the PDC of ORlando, 7000 developers found in their valisette offered the welcome, of the CD Roms with a version Alpha of functional ASP+. Certainly it is only a version Alpha (the definitive will probably come only during the 1st semester 2001), but she/it is already operational (the speech of B. Gates was not therefore that a dream), and already sites in ASP+ are present on the web, some books are in preparation, etc.
The continuation of this article is a presentation of the new functionalities of ASP+.
For what environment?
Before all things, ASP+ will be (finally it is what they say for the meantime), perfectly compatible with ASP. To use ASP+, it is sufficient to install it on a server web. She/it is independent of the operating system (NT4 ie or W2K) but is bound solely to the server web. For the meantime, only IIS4 and IIS5 are supported. There are not taken decisions concerning PWS again.
The Web Forms
One could believe in one term marketing. One Web Form designates a silly page web indeed with the new extension aspx that replaces asp. His/her/its content is similar to one page classic asp of the style:
< HTML > < LEOTARD > <% = "Hello World"% > < / LEOTARD > < / HTML >
But the underlying idea is to be able to create the pages web as merely that developers Visual Basic make it:
* drag & drop of controls, * management of the évènements of the same controls, * etc.
Of course, Microsoft develops its pack of development Visual Studio.NET currently (alias Visual Studio 7) in this sense.
Code compiled
A first element of importance (some will find that it is the main) is that the code is not interpreted anymore but compiled at the first access to the page. It means that the first time that a person will connect on this page, ASP+ will compile the code. for all other people who will connect thereafter, it will be the compiled code that himself will execute. The gain in performance is enormous. For memory, when Visual Basic passed of the version 4 (P-Code) to the version 5 (C++ compiler), the gain was of 10 (after the tests and this although Microsoft announced one gain of 20).
Independence of the language
Another important element: the language used. For the meantime, side server, you could use the VBScript or the #106avascript. Now more than 9 languages are announced officially (VB, C++, C #, Perl, etc.) although only the C #is supported currently in addition to the two traditional languages. Thus, all developers can keep their habits. A fan of the Perl who finds the "basic" VB will be able to use ASP+.
The controls servers
Windows has always been delivered with common so-called controls: for example, in the exploring Windows, you have on the left an arborescence (TreeView control) and on the right the content (ListView control). These controls are put at the disposal of the developers for their own applications without having to rewrite the code of their displays, management, etc. He/it is some in the same way with the controls servers of ASP+. ASP+ is delivered with 45 very various controls. It goes from a beast zones text to the calendar while passing by a treeview. Their declarations within one ASP+ page are very simple. For example, for a control text with an unwinding list zone:
< asp:textbox runat=server > < asp:dropdownlist runat=server >
Will you tell to me, what is the interest to use this type of control? As the developers who use MS Visual Interdev must begin to feel it, you can associate a control textbox very well in a field of a recordset. Besides, you can write the code in the Click évènement of a Button creates side server (a remark, ASP+ analyzes the navigator interrogant the page to optimize the generated code. If it is, for example IE5, he/it will use some DHTML functions, on the other hand, for navigators of "low" level, the code will only be executed side server). Last example for you persuades, you certainly display your registrations of a recordset in a picture. The code to write is consequent enough. With ASP+, use the control datagrid: 2 lines of code, one to create the object, another to associate it to a recordset! Of course, and this contrary to the DTC controls of Visual Interdev, the aspect of these controls is perfectly modifiable.
The invisible controls
Some invisible controls also exist (as the Timer in Visual Basic). An example of this type of control is the controls of validation. For example, they permit to insure that the text Name of a form (side server) has been filled well and correctly by the internaut, that an element of a zone of list déroulable has been selected well, etc. As describes above, the code of validation will execute itself either side server for the low-level navigators, either client side for the navigators high-level (some will say here that it is the new solution found by Microsoft to impose MS Internet Explorer 6!). Among these controls of navigation, you have a control that insures that you filled a zone of text well, an another one that insures that of the #118alues are consisted well between a maximal #118alue and a minimal, etc.
The pagelets
To simplify the pagelets permit you to create your own controls servers. With ASP+, you can create a page aspx containing a control server, then to add him the properties and supplementary methods that you wish and it, precisely as you make it currently while developing some OCX controls for your local applications. These pages have for extensions aspc (c for control). A pagelet can contain several controls and can manage in intern his/her/its own events. Thus, you can ask one for your developers to create a pagelet for the login in your Intranet. This pagelet will consist of two zones of text, one for the name, the other for the password. Your developer can create in the pagelet codes it that will validate that the entries are correct. She/it will expose a évènement asklog that will be generated solely when all parameters entered by the internauts will be formed well. On your side, you will have only to use this pagelet in your pages, either only one line of code.
Other advantage, you will be able to have (contrary to the Include) several pagelets of the same type in only one page.
Finally, you will be able to instancier of the pagelets dynamically in your pages.
ASP net:Vaporware or reality?
Post By kwdez on 2008-9-26 15:40:52 [Reads:264]
ASP.net:Vaporware or reality?
Did Bill Gates announce the launching a few weeks ago, officially of. CLEAN (Dowry NET). Many analysts, often persifleurs, shouted to the vaporware again. Then, since the following day, Microsoft announced its will to create a new language the C #(C Sharp). Some immediately named it the J--. Last week (of the 11 to July 14, 2000), in the PDC of ORlando, 7000 developers found in their valisette offered the welcome, of the CD Roms with a version Alpha of functional ASP+. Certainly it is only a version Alpha (the definitive will probably come only during the 1st semester 2001), but she/it is already operational (the speech of B. Gates was not therefore that a dream), and already sites in ASP+ are present on the web, some books are in preparation, etc.
The continuation of this article is a presentation of the new functionalities of ASP+.
For what environment?
Before all things, ASP+ will be (finally it is what they say for the meantime), perfectly compatible with ASP. To use ASP+, it is sufficient to install it on a server web. She/it is independent of the operating system (NT4 ie or W2K) but is bound solely to the server web. For the meantime, only IIS4 and IIS5 are supported. There are not taken decisions concerning PWS again.
The Web Forms
One could believe in one term marketing. One Web Form designates a silly page web indeed with the new extension aspx that replaces asp. His/her/its content is similar to one page classic asp of the style:
< HTML > < LEOTARD > <% = "Hello World"% > < / LEOTARD > < / HTML >
But the underlying idea is to be able to create the pages web as merely that developers Visual Basic make it:
* drag & drop of controls, * management of the évènements of the same controls, * etc.
Of course, Microsoft develops its pack of development Visual Studio.NET currently (alias Visual Studio 7) in this sense.
Code compiled
A first element of importance (some will find that it is the main) is that the code is not interpreted anymore but compiled at the first access to the page. It means that the first time that a person will connect on this page, ASP+ will compile the code. for all other people who will connect thereafter, it will be the compiled code that himself will execute. The gain in performance is enormous. For memory, when Visual Basic passed of the version 4 (P-Code) to the version 5 (C++ compiler), the gain was of 10 (after the tests and this although Microsoft announced one gain of 20).
Independence of the language
Another important element: the language used. For the meantime, side server, you could use the VBScript or the #106avascript. Now more than 9 languages are announced officially (VB, C++, C #, Perl, etc.) although only the C #is supported currently in addition to the two traditional languages. Thus, all developers can keep their habits. A fan of the Perl who finds the "basic" VB will be able to use ASP+.
The controls servers
Windows has always been delivered with common so-called controls: for example, in the exploring Windows, you have on the left an arborescence (TreeView control) and on the right the content (ListView control). These controls are put at the disposal of the developers for their own applications without having to rewrite the code of their displays, management, etc. He/it is some in the same way with the controls servers of ASP+. ASP+ is delivered with 45 very various controls. It goes from a beast zones text to the calendar while passing by a treeview. Their declarations within one ASP+ page are very simple. For example, for a control text with an unwinding list zone:
< asp:textbox runat=server > < asp:dropdownlist runat=server >
Will you tell to me, what is the interest to use this type of control? As the developers who use MS Visual Interdev must begin to feel it, you can associate a control textbox very well in a field of a recordset. Besides, you can write the code in the Click évènement of a Button creates side server (a remark, ASP+ analyzes the navigator interrogant the page to optimize the generated code. If it is, for example IE5, he/it will use some DHTML functions, on the other hand, for navigators of "low" level, the code will only be executed side server). Last example for you persuades, you certainly display your registrations of a recordset in a picture. The code to write is consequent enough. With ASP+, use the control datagrid: 2 lines of code, one to create the object, another to associate it to a recordset! Of course, and this contrary to the DTC controls of Visual Interdev, the aspect of these controls is perfectly modifiable.
The invisible controls
Some invisible controls also exist (as the Timer in Visual Basic). An example of this type of control is the controls of validation. For example, they permit to insure that the text Name of a form (side server) has been filled well and correctly by the internaut, that an element of a zone of list déroulable has been selected well, etc. As describes above, the code of validation will execute itself either side server for the low-level navigators, either client side for the navigators high-level (some will say here that it is the new solution found by Microsoft to impose MS Internet Explorer 6!). Among these controls of navigation, you have a control that insures that you filled a zone of text well, an another one that insures that of the #118alues are consisted well between a maximal #118alue and a minimal, etc.
The pagelets
To simplify the pagelets permit you to create your own controls servers. With ASP+, you can create a page aspx containing a control server, then to add him the properties and supplementary methods that you wish and it, precisely as you make it currently while developing some OCX controls for your local applications. These pages have for extensions aspc (c for control). A pagelet can contain several controls and can manage in intern his/her/its own events. Thus, you can ask one for your developers to create a pagelet for the login in your Intranet. This pagelet will consist of two zones of text, one for the name, the other for the password. Your developer can create in the pagelet codes it that will validate that the entries are correct. She/it will expose a évènement asklog that will be generated solely when all parameters entered by the internauts will be formed well. On your side, you will have only to use this pagelet in your pages, either only one line of code.
Other advantage, you will be able to have (contrary to the Include) several pagelets of the same type in only one page.
Finally, you will be able to instancier of the pagelets dynamically in your pages.