Implementing .NET 1.1 style asynchronous web services with .NET 2

[org]

Hi,

I'm developing a web service with should be used by an .NET CF2 client and
an .NET 2.0 Windows client.
I've tried to put all the connection logic into one class, which could be
used in common from the mobile and the windows client. But this didn't work:
The new .NET framework supports asynchronous web services with the
"MethodnameCompleted+=new MethodNameEventHandler pattern, but the "old
style" .NET 1 pattern used in the compact framework works with BeginInvoke
and delegates. Is there a way to create (in VS2005) the "old-style" proxy
class to access the web service that offers this BeginInvoke methods?

best regards
Johannes

[Mork]

Johannes,

I'm not sure I understand your question/problem. The asynchronous
patterns of BeginOperation/EndOperation vs.
Operation/OperationCompleted are concurrent programming patterns in
..NET that allow your other threads to continue to do work while one
thread waits on the (synchronous) response from the Web service.

This doesn't affect the message exchange pattern exposed by the Web
service which is still synchronous request/response in both versions.
The XML sent/received will be about the same from .NET 1.1 proxy or
..NET 2.0 proxy using the synchronous methods or asynchronous methods.

HTH,
~Mork
org wrote:

Hi,

I'm developing a web service with should be used by an .NET CF2 client and
an .NET 2.0 Windows client.
I've tried to put all the connection logic into one class, which could be
used in common from the mobile and the windows client. But this didn't work:
The new .NET framework supports asynchronous web services with the
"MethodnameCompleted+=new MethodNameEventHandler pattern, but the "old
style" .NET 1 pattern used in the compact framework works with BeginInvoke
and delegates. Is there a way to create (in VS2005) the "old-style" proxy
class to access the web service that offers this BeginInvoke methods?

best regards
Johannes