As I recall, that server side debugging is for ASP scripts, not for the general debugging. Anyway, that is orthogonal to what you are trying to achieve.
As I said in post #2, your web app needs to be running for you to able to attach the (remote) debugger. Hit the home page of the web app with your browser from your client machine. Then on the server you will find that w3wp.exe is running via Task Manager. Start up the remote debugger proxy on the server. Then on your client machine start up VS, and do the remote debugging attach. Remember to point to the server machine.
Let me summarize your answers.This is how I understood your answer.
Your Answer) Hit the home page of the web app with your browser from your client machine.
====> (1) In Client PC(My PC), Search for
www.webip.com in a web browser.
Your Answer) Then on the server you will find that w3wp.exe is running via Task Manager.
====> What it means, I didn't understand.
Your Answer) Start up the remote debugger proxy on the server.
====> What it means, I didn't understand.
Your Answer) Then on your client machine start up VS,
====> In My PC(your client machine), Debug Mode (Brake Point) is set in the VS source code of
www.webip.com.
Your Answer) and do the remote debugging attach.
Your Answer) and do the remote debugging attach.
====> Is the picture below my understanding of your answer correct?
Your Answer) Remember to point to the server machine.
====> What it means, I didn't understand.
Please Help me.