> You can either set the type to dynamic in the web reference in VS.Net, or
I will try that and see what the generated code looks like.
> you can use the publicly accessible "Url" property on the generated class to
Hmmm. Does that really work?
I thought about that but when I saw all of the string literals 'baked in' to
the proxy code I thought it would be unlikely to work.
Andy
> You can either set the type to dynamic in the web reference in VS.Net, or
> you can use the publicly accessible "Url" property on the generated class to
[quoted text clipped - 39 lines]
> > [System.Diagnostics.DebuggerStepThroughAttribute()]
> > [System.ComponentModel.DesignerCategoryAttribute("code")]
[System.Web.Services.WebServiceBindingAttribute(Name="CluProviderSoap",
> > Namespace="http://localhost/CluServer/")]
> > public class CluProvider :
[quoted text clipped - 6 lines]
> >
> > /// <remarks/>
[System.Web.Services.Protocols.SoapDocumentMethodAttribute("http://localhost
> > /CluServer/CanConnect", RequestNamespace="http://localhost/CluServer/",
> > ResponseNamespace="http://localhost/CluServer/",
> > Use=System.Web.Services.Description.SoapBindingUse.Literal,
ParameterStyle=System.Web.Services.Protocols.SoapParameterStyle.Wrapped)]
> > public bool CanConnect() {
> > object[] results = this.Invoke("CanConnect", new object[0]);
[quoted text clipped - 10 lines]
> >
> > Andy
Nathan Craddock - 07 Oct 2005 17:10 GMT
The VS.Net web reference thing is pretty much just a placeholder for
settings so it can run WSDL when you do "Update Web Reference".
Also, if you notice in the generated class for C#, the literals in the
constructor are actually being applied to "this.Url" which is the same
publicly accessible property I was suggesting you set. Setting that Url
property immediately after instantiating the object is pretty standard, I
think. It's how I've always done it, and it's never given me any problems.
>> You can either set the type to dynamic in the web reference in VS.Net, or
>
[quoted text clipped - 92 lines]
>> >
>> > Andy