ASP.NET and the testing with IIS

Slide 1:

While making a web site or even a form in classic asp or Asp.net web form if you wanted to check and debug your web application, you had one choice, and one choice only…run a version of Internet Information Services (IIS) on your local machine. Before hosting your form or website you have to be sure that the form you made is free from error and there is no technically fault in it. To make website compatible and error free you could attempt to debug against a remote instance of IIS but for most of the part that means peppering your code liberally with calls to Response.write and hoping that you remember to remove or make them comments before you pushed your code to protection. Asp .net provides you the feature by introducing the trace feature. This feature allows you to a special API in order to write out debugging statement i.e. it will show you all the error in the code in a separate box with the specific information about the error. You could view this information either in line with the page output or in separate trace box. But this is not really debugging and it doesn’t allow you to test any thing particular on the web server. Its just used to verify the state of your application at a given point in the request processing or page life cycle i.e. it doesn’t mean that if the form is working properly it will work same as in the real world. But if you wanted to see that how your application would behave at run time, IIS is the best way to check it which means you have to be an administrator. As IIS is a service all you have to do is to install it and to debug your application. IIS is programmed by Microsoft and it is most popular in today’s world. IIS is a great addition to the developer’s tool belt. The ability to take advantage of the full feature set of IIS in an easy to install package makes this a great way to have your local test environment in your personal machine. ASP.NET and the testing with IIS

Slide 2:

History: EMWAC server was not able to control the volume of traffic going to Microsoft.com. Microsoft was forced to develop its own web server, IIS. IIS has many versions and every version of IIS was released either along or with a version of Microsoft Windows operating system IIS 1.0, Windows NT 3.51 available as a free add-on IIS 2.0, Windows NT 4.0 IIS 3.0, Windows NT 4.0 Service Pack 2[10] IIS 4.0, Windows NT 4.0 Option Pack IIS 5.0, Windows 2000 IIS 5.1, Windows XP Professional and Windows XP Media Center Edition (requires retail CD) IIS 6.0, Windows Server 2003 and Windows XP Professional x64 Edition IIS 7.0, Windows Server 2008 and Windows Vista (Home Premium, Business, Enterprise and Ultimate editions)

Slide 3:

IIS 7.5, Windows Server 2008 R2 and Windows 7 (Home Premium, Professional, Enterprise and Ultimate editions) For more details on Code Protection technology, .net Obfuscator , .net Code Security and .net Code Security feel free to visit us at http://www.secureteam.net