If you're using WSE 2.0 you can turn on the trace files in App.Config
(Client) and/or Web.Config (server). Remember to create the directory
that the trace file is to be put in. Also, don't forget to turn off
the trace when you're done (especially on the server side) as it will
be a performance drain.
-Paul
<microsoft.web.services2>
<!--
<soapExtensionTypes>
<add type="Microsoft.Web.Services2.WebServicesExtension,
Microsoft.Web.Services2, Version=2.0.3.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" priority="1" group="0" />
</soapExtensionTypes>
-->
<diagnostics>
<trace enabled="true" input="c:\traces\ClientInput.xml
output="c:\traces\ClientOutput.xml" />
</diagnostics>
> Hi,
>
[quoted text clipped - 3 lines]
> regards
> sanjaya
Sanjaya - 27 Jul 2006 20:03 GMT
thx pal . currently i'm not using WSE 2.0. is it only configuration or do i
need to use the classes from it ?
> If you're using WSE 2.0 you can turn on the trace files in App.Config
> (Client) and/or Web.Config (server). Remember to create the directory
[quoted text clipped - 24 lines]
>> regards
>> sanjaya
Ravi Shankar - 28 Jul 2006 07:21 GMT
You can try using SOAP Toolkit. The download is available in
http://www.microsoft.com/downloads/details.aspx?familyid=c943c0dd-ceec-4088-9753
-86f052ec8450&displaylang=en

Signature
Thanks & Regards
Ravi Shankar S
> thx pal . currently i'm not using WSE 2.0. is it only configuration or do i
> need to use the classes from it ?
[quoted text clipped - 27 lines]
> >> regards
> >> sanjaya