Hello Tim,

Thanks for the reply.

I've tested it and found the behavior you encountered and I think you 
haven't missed anything, the reason why the "invoke" submit's 
request/response is not captured by our Trace port(8888) is as below:

The "invoke" button actually do a HTTP POST  submit to the server, and the 
submit target address is defined in the  page's  <form > element below:

==================
 <form target="_blank" 
action='http://localhost/ASPNET/V2/WebServices/IISService/Service.asmx/Hello
World' method="POST">      
==================

You can find that the "action" attribute still point to the originall  "80" 
port rather than the 8888 port we registered in trace utility, that means 
the "invoke" submit the request to "80" port directly and bypass our trace 
channel, that's why we didn't get the trace log.  Since the <form > element 
is automatically generated by the service handler, we can not manually 
modify the page, if you do need to capture the "invoke" submit's request/ 
response, you can consider the following means:

1. still request the asmx page first and choose the certain 
webmethod/operation and go the to "invoke" page

2. instead of directly click the button on it, we first save this page as a 
local html page on our machine's disk

3. use text editor to open it and find the "<form>" element I mentioned 
above, change the <form> element's "action" attribute from

"http://localhost/................"     to   
"http://localhost:8888/..............."  

and save the file.

4. open our modified local html page and click the "invoke" button on it, 
that should send the request through our trace channel and the utility can 
capture the request/response.


BTW, I'm wondering whether you're wantting to capture the http get/post 
invoking request/response or the SOAP request/response message?  Because 
the  asmx test page's  "invoke" button only simulate the webservice 
behavior by using simple  http get/post request, and it won't generate any 
SOAP message. Therefore, if you want to captuer SOAP messages of webservice 
request/response,  you need to create the webservice proxy and use proxy to 
call webservice and trace the request/response.  To redirect the 
request/response of  webservice proxy, we can change the proxy's "Url" 
attribute in code. e.g.


=====================
wslocal.Service wsproxy = new ProcessConsole.wslocal.Service();


wsproxy.Url = 
"http://localhost:8888/ASPNET/V2/WebServices/IISService/Service.asmx";

wsproxy.callmethod();
=======================

Thus, our trace utility's listening channel can capture the SOAP 
request/response message.

Hope this helps. If there is any other information you wonder, please feel 
free to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

This posting is provided "AS IS" with no warranties, and confers no rights.