Carlos Peix
1/22/2003 8:10:00 PM
Tracy,
The fact is: your web service exposes just the synchronous version of the
method, the asynchronous one is generated by the proxy class (helped by the
FCL), so, you do not have control on that.
BTW, if a developer can generate a proxy class for you WS I think he/she
will understand the whole thing...
-cp
Tracy Fletcher <spambox@fletchercentral.com> wrote in message
news:64d36a83.0301220945.53f574df@posting.google.com...
> Thanks for your reply Carlos,
>
> I do offer users a proxy class, which does essentially filter out the
> aforementioned methods. The problem is that the end users (developers
> in the case of an Asynchronous System) can use the web service
> directly, allowing me no control over the client. The system will be
> deployed in many different situations. I was hoping that perhaps I
> could exercise some control over what the client sees from the web
> service settings themselves.
>
> Thanks again for responding,
>
> Tracy Fletcher
>
> "Carlos Peix" <cpeix@hotmail.com> wrote in message
news:<#OIxyeUwCHA.1644@TK2MSFTNGP09>...
> > Tracy,
> >
> > If you have a proxy class in your client (and you should), simply
delete
> > those methods from that class...
> >
> > HTH
> > -cp
> >
> > Tracy Fletcher <spambox@fletchercentral.com> wrote in message
> > news:64d36a83.0301171543.9b41a9b@posting.google.com...
> > > I've developed an Enterprise Asynchronous Solution that is accessible
> > > via an ASP.Net WebService. My problem is that the standard
> > > WebReference includes Asynchronous method calls such as BeginWebMethod
> > > and EndWebMethod. Is there any way I can prevent these options from
> > > appearing? I think they will be confusing to my end users.
> > >
> > > Thanks!
> > >
> > > Tracy Fletcher