Please enable Javascript to correctly display the contents on Dot Net Tricks!

Debugging Web App On IIS and Various Authentication Mode

 Print 
  Author : Shailendra Chauhan
Posted On : 27 Feb 2017
Total Views : 4,554   
Updated On : 27 Feb 2017
 

Remote IIS Debugging

We can easily debug any web application that is hosted on IIS by attaching worker process of that application to Visual Studio as shown below.

From Visual Studio IDE > Tools > Attach to Process Select the particular Process, then start debugging.

IIS Debugging

Then click on attach button

IIS Debugging

Now, enjoy debugging with Visual Studio.

Debugging With VisuaStudio

Different Authentication Mode Available for IIS Remote Debugging

There are two authentication modes available in IIS for remote debugging:

  1. No-Authentication

  2. Windows Authentication

Windows Authentication

- Msvsmon provide high level security with the windows authentication mode. The user who want to debug the application remotely he should be authenticated, means he should have sufficient permission to access the debugging facility from the remote system.

No-Authentication

- There is no security involved with this authentication mode. Anyone can debug remotely, if the authentication mode is set to "No-Authentication". As this debugging mode is not at all secure, so it should be used only on secure network.

IIS Allows Multiple User to Remote Debug Simultaneously

This is one of the most fantastic features of Msvsmon tool. Msvsmon debugging monitor tool allow multiple user to debug simultaneously. Each instance of the remote debugger has a unique server name. As I have already shown that server names are configurable, so we can give an instance of the remote debugger any server name. Now multiple user can able to access the same.

aspnet_regiis -i Command

The following command installs the ASP.NET version that is associated with the ASP.NET IIS registration tool and updates the script maps of all existing ASP.NET applications. Note that only applications that are currently mapped to an earlier version of ASP.NET are affected.

Default Location for IIS Log Files

The default location for IID log files varies from IIS versions. In IIS6 & IIS7 these are given below-

For IIS7:

%SystemDrive%\inetpub\logs\LogFiles

For IIS6:

%windir%\System32\LogFiles

    Common Errors & Status Codes in IIS

    The list of errors with status code is given below-

    common errors & status codes in IIS
    Status Code
    Description
    100
    Informational
    200
    Successful
    300
    Redirection
    400
    Client Error

    I hope now you have better understanding about Remote IIS Debugging. Your valuable feedback, question, or comments about this article are always welcome.



ABOUT AUTHOR

Shailendra Chauhan
Author, Architect, Corporate Trainer and Microsoft MVP

He is the author of some of most popular e-books which encompass technical Interview on Node.js Interview Questions and Answers, ASP.NET MVC Interview Questions and Answers, AngularJS Interview Questions and Answers and LINQ Interview Questions and AnswersKnow more...

Free Interview Books
 
COMMENTS
14 OCT
Angular2 and Angular4 (Online)
03:00 PM-05:00 PM IST (+5.30GMT)
12 OCT
ASP.NET Core (Online)
09:00 PM - 11:00 PM IST(+5:30 GMT)
10 OCT
Microsoft Azure Infrastructure Solutions (Online)
08:00 AM-09:30 AM IST / 09:30 PM -11:00 PM CST
30 SEP
Angular2 and Angular4 (Classroom)
08:30 AM-11:30 AM IST
20 SEP
MEAN Stack (Online)
07:00 AM-09:00 AM IST
20 SEP
ASP.NET MVC with Angular4 (Online)
9:00PM- 11:00PM IST(+5:30GMT)
16 SEP
Angular2 and Angular4 (Online)
08:00 AM-10:00 AM IST(+5.30 GMT)
22 AUG
ASP.NET Core with Angular4 (Online)
07:00 AM - 9:00 AM IST(+5:30 GMT)
LIKE US ON FACEBOOK
 
+