"FredB" <Fr***@discussions.microsoft.comwrote in message
news:9E**********************************@microsof t.com...
This particular issues caused me to throw a small fit for far too long...
anyway, i easily fixed it by manually setting the .Url property to the
correct site...
i.e.
myWebRerence.Lists ws= new myWebReference.Lists();
ws.Url = "http://site/SUBSITE/_vti_bin/lists.asmx";
ws.Credentials = System.Net.CredentialCache.DefaultCredentials;
WSS v3 i think is at fault here...
I've learned a bit more about SharePoint since your previous posts. I have a
new theory about this now.
All of the files in a SharePoint site are identical to the files in the
parent site collection until you customize them. This is true for the .aspx
pages, isn't it? So why would it not be true for the .asmx files, or even
any .WSDL files if there are any? Among other things, this implies that the
URL in any such a file will still be the URL of the site collection.
At any rate, like I said, the <soap:addressin the WSDL is only a hint. You
should never depend on it being there, or being valid.
--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer