00:41
HirenBhut
A shopping cart is a cart supplied by a shop, especially supermarkets, for use by customers inside the shop for transport of merchandise to the check-out counter during shopping. Customers can then also use the cart to transport their purchased goods to their cars.
In some places, customers are allowed to leave the carts in the parking lot, and store personnel will return the carts to the storage area. In most European premises however, coin (or token) operated locking mechanisms are provided to encourage shoppers to return the carts to the correct location after use.
ASP.NET is a web application framework developed and marketed by Microsoft to allow programmers to build dynamic web sites, web applications and web services. It was first released in January 2002 with version 1.0 of the .NET Framework, and is the successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using any supported .NET language. The ASP.NET SOAP extension framework allows ASP.NET components to process SOAP messages.
How to set up Internet Information Service (IIS)
These instructions are written for Windows 2000 Professional.
There is an issue with the implementation of the web server shipped with Windows 2000 Professional and Windows XP Professional. This is not a problem with Windows 2000 Server or 2003 Server. The issue is that there is a limit on the number of connections the server accepts. This is set to 10 connections. A single user who loads the web site may in fact use up 2 or 3 connections at a time. With the default settings, these connections are persistent, which means that you reach the 10 connection limit very quickly.
There is a knowledge base article on Microsofts web site which sort of explains the problem. Search for article 262635 or goto http://support.microsoft.com/default.aspx?scid=kb;EN-US;262635
Make Sure you Can See Admin Tools menu
Most of the next instructions rely on you being able to get at the Administrative Tools menu. Again, this is hidden by default. Right click in the start menu, and choose Properties. Go to the Advanced tab, and tick the box Display Administrative Tools. Press OK.
Use Performance Monitor to see the problem
One way to view the connections is to use Performance Monitor (Start Menu: Programs: Administrative Tools) , and add (Press the + button) the Web Services counter of Current Connections. You also need to change the scale from 100 to 10 (so its easier to see). Itll look something like this when set up right
You can use this to keep track of this problem during busy periods or testing. You can see above the spike to three connections. This was made by a single web request to load a results screen. Note also that the connection values drop back to zero almost straight away? This is not the default behaviour. By default these are kept alive for a lot longer.
ASP.NET aims for performance benefits over other script-based technologies (including Classic ASP) by compiling the server-side code to one or more DLL files on the web server.[20] This compilation happens automatically the first time a page is requested (which means the developer need not perform a separate compilation step for pages). This feature provides the ease of development offered by scripting languages with the performance benefits of a compiled binary. However, the compilation might cause a noticeable but short delay to the web user when the newly-edited page is first requested from the web server, but will not again unless the page requested is updated further.
The ASPX and other resource files are placed in a virtual host on an Internet Information Services server (or other compatible ASP.NET servers; see Other implementations, below). The first time a client requests a page, the .NET Framework parses and compiles the file(s) into a .NET assembly and sends the response; subsequent requests are served from the DLL files. By default ASP.NET will compile the entire site in batches of 1000 files upon first request. If the compilation delay is causing problems, the batch size or the compilation strategy may be tweaked.
Developers can also choose to pre-compile their "codebehind" files before deployment, using MS Visual Studio, eliminating the need for just-in-time compilation in a production environment. This also eliminates the need of having the source code on the web server.
Other differences compared to ASP classic are:
* Compiled code means applications run faster with more design-time errors trapped at the development stage.
* Significantly improved run-time error handling, making use of exception handling using try-catch blocks.
* Similar metaphors to Microsoft Windows applications such as controls and events.
* An extensive set of controls and class libraries allows the rapid building of applications, plus user-defined controls allow commonly-used web template, such as menus. Layout of these controls on a page is easier because most of it can be done visually in most editors.
* ASP.NET uses the multi-language abilities of the .NET Common Language Runtime, allowing web pages to be coded in VB.NET, C#, J#, Delphi.NET, Chrome, etc.
* Ability to cache the whole page or just parts of it to improve performance.
* Ability to use the code-behind development model to separate business logic from presentation.
* Ability to use true object-oriented design for programming pages and controls
* If an ASP.NET application leaks memory, the ASP.NET runtime unloads the AppDomain hosting the erring application and reloads the application in a new AppDomain.
* Session state in ASP.NET can be saved in a Microsoft SQL Server database or in a separate process running on the same machine as the web server or on a different machine. That way session values are not lost when the web server is reset or the ASP.NET worker process is recycled.
* Versions of ASP.NET prior to 2.0 were criticized for their lack of standards compliance. The generated HTML and JavaScript sent to the client browser would not always validate against W3C/ECMA standards. In addition, the framework's browser detection feature sometimes incorrectly identified web browsers other than Microsoft's own Internet Explorer as "downlevel" and returned HTML/JavaScript to these clients with some of the features removed, or sometimes crippled or broken. However, in version 2.0, all controls generate valid HTML 4.0, XHTML 1.0 (the default) or XHTML 1.1 output, depending on the site configuration. Detection of standards-compliant web browsers is more robust and support for Cascading Style Sheets is more extensive.
* Web Server Controls: these are controls introduced by ASP.NET for providing the UI for the web form. These controls are state managed controls and are WYSIWYG controls.
By Hiren Bhut
In some places, customers are allowed to leave the carts in the parking lot, and store personnel will return the carts to the storage area. In most European premises however, coin (or token) operated locking mechanisms are provided to encourage shoppers to return the carts to the correct location after use.
ASP.NET is a web application framework developed and marketed by Microsoft to allow programmers to build dynamic web sites, web applications and web services. It was first released in January 2002 with version 1.0 of the .NET Framework, and is the successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using any supported .NET language. The ASP.NET SOAP extension framework allows ASP.NET components to process SOAP messages.
How to set up Internet Information Service (IIS)
These instructions are written for Windows 2000 Professional.
There is an issue with the implementation of the web server shipped with Windows 2000 Professional and Windows XP Professional. This is not a problem with Windows 2000 Server or 2003 Server. The issue is that there is a limit on the number of connections the server accepts. This is set to 10 connections. A single user who loads the web site may in fact use up 2 or 3 connections at a time. With the default settings, these connections are persistent, which means that you reach the 10 connection limit very quickly.
There is a knowledge base article on Microsofts web site which sort of explains the problem. Search for article 262635 or goto http://support.microsoft.com/default.aspx?scid=kb;EN-US;262635
Make Sure you Can See Admin Tools menu
Most of the next instructions rely on you being able to get at the Administrative Tools menu. Again, this is hidden by default. Right click in the start menu, and choose Properties. Go to the Advanced tab, and tick the box Display Administrative Tools. Press OK.
Use Performance Monitor to see the problem
One way to view the connections is to use Performance Monitor (Start Menu: Programs: Administrative Tools) , and add (Press the + button) the Web Services counter of Current Connections. You also need to change the scale from 100 to 10 (so its easier to see). Itll look something like this when set up right
You can use this to keep track of this problem during busy periods or testing. You can see above the spike to three connections. This was made by a single web request to load a results screen. Note also that the connection values drop back to zero almost straight away? This is not the default behaviour. By default these are kept alive for a lot longer.
ASP.NET aims for performance benefits over other script-based technologies (including Classic ASP) by compiling the server-side code to one or more DLL files on the web server.[20] This compilation happens automatically the first time a page is requested (which means the developer need not perform a separate compilation step for pages). This feature provides the ease of development offered by scripting languages with the performance benefits of a compiled binary. However, the compilation might cause a noticeable but short delay to the web user when the newly-edited page is first requested from the web server, but will not again unless the page requested is updated further.
The ASPX and other resource files are placed in a virtual host on an Internet Information Services server (or other compatible ASP.NET servers; see Other implementations, below). The first time a client requests a page, the .NET Framework parses and compiles the file(s) into a .NET assembly and sends the response; subsequent requests are served from the DLL files. By default ASP.NET will compile the entire site in batches of 1000 files upon first request. If the compilation delay is causing problems, the batch size or the compilation strategy may be tweaked.
Developers can also choose to pre-compile their "codebehind" files before deployment, using MS Visual Studio, eliminating the need for just-in-time compilation in a production environment. This also eliminates the need of having the source code on the web server.
Other differences compared to ASP classic are:
* Compiled code means applications run faster with more design-time errors trapped at the development stage.
* Significantly improved run-time error handling, making use of exception handling using try-catch blocks.
* Similar metaphors to Microsoft Windows applications such as controls and events.
* An extensive set of controls and class libraries allows the rapid building of applications, plus user-defined controls allow commonly-used web template, such as menus. Layout of these controls on a page is easier because most of it can be done visually in most editors.
* ASP.NET uses the multi-language abilities of the .NET Common Language Runtime, allowing web pages to be coded in VB.NET, C#, J#, Delphi.NET, Chrome, etc.
* Ability to cache the whole page or just parts of it to improve performance.
* Ability to use the code-behind development model to separate business logic from presentation.
* Ability to use true object-oriented design for programming pages and controls
* If an ASP.NET application leaks memory, the ASP.NET runtime unloads the AppDomain hosting the erring application and reloads the application in a new AppDomain.
* Session state in ASP.NET can be saved in a Microsoft SQL Server database or in a separate process running on the same machine as the web server or on a different machine. That way session values are not lost when the web server is reset or the ASP.NET worker process is recycled.
* Versions of ASP.NET prior to 2.0 were criticized for their lack of standards compliance. The generated HTML and JavaScript sent to the client browser would not always validate against W3C/ECMA standards. In addition, the framework's browser detection feature sometimes incorrectly identified web browsers other than Microsoft's own Internet Explorer as "downlevel" and returned HTML/JavaScript to these clients with some of the features removed, or sometimes crippled or broken. However, in version 2.0, all controls generate valid HTML 4.0, XHTML 1.0 (the default) or XHTML 1.1 output, depending on the site configuration. Detection of standards-compliant web browsers is more robust and support for Cascading Style Sheets is more extensive.
* Web Server Controls: these are controls introduced by ASP.NET for providing the UI for the web form. These controls are state managed controls and are WYSIWYG controls.
By Hiren Bhut
Posted in: ASP Project
Posts
0 comments:
Post a Comment