Hi Mike, Thanks for your reply.
The syntax I used at the command line for soapsuds is: soapsuds -url:http://localhost:1095/ServiceClass?WSDL -oa:Server.dll The directory structure for the server console app is: My Documents\Visual Studio Projects\Remoting2\bin\Debug ...and the client directory is: Visual Studio Projects\Remoting2Client\bin\Debug The soapsuds generated DLL is in: My Documents\Visual Studio Projects\Remoting2Client The exception text is: "Cannot load type soap:ServiceClass, http://schemas.microsoft.com/clr/nsassem/Server/Remoting2%2C%20Version%3D1.0 .1137.27545%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Dnull. at System.Runtime.Remoting.Messaging.MethodCall.ResolveMethod(Boolean bThrowIfNotResolved) at System.Runtime.Remoting.Messaging.MethodCall.ResolveMethod() at System.Runtime.Remoting.Messaging.MethodCall..ctor(IMessage msg, Boolean needAccessCheck) at System.Runtime.Remoting.Messaging.MethodCall..ctor(IMessage msg) at System.Runtime.Remoting.Proxies.RemotingProxy.InternalInvokeAsync(IMessageSi nk ar, Message reqMsg, Boolean useDispatchMessage, Int32 callType) at System.Runtime.Remoting.Proxies.RemotingProxy.InternalInvoke(IMethodCallMess age reqMcmMsg, Boolean useDispatchMessage, Int32 callType) at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(IMessage reqMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at MyDelegate.BeginInvoke(AsyncCallback callback, Object object) at TheClient.Run() in c:\documents and settings\zb5897\my documents\visual studio projects\remoting2client\theclient.cs:line 45" Thanks again for your help! Sean -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Woodring (DevelopMentor) Sent: Wednesday, February 12, 2003 10:08 AM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Asynch Remoting Call Fails I cannot reproduce your failure using either the 1.0 runtime & tools nor the 1.1 runtime and tools. Your code builds & runs fine with no errors on either platform. You didn't specify how you used soapsuds, so I tried both ways (using -ia:<serverAssemblyname> as well as -url:<wsdlQueryToRunningServer>). Can you post the following: - the soapsuds command line you're using - a description of the directory structure where the two exes and soapsuds-generated dll reside when you run your apps - the full text of the exception that you're seeing -Mike DevelopMentor http://staff.develop.com/woodring > -----Original Message----- > From: Moderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED]] On Behalf Of Sean Chase > Sent: Tuesday, February 11, 2003 4:35 PM > To: [EMAIL PROTECTED] > Subject: [ADVANCED-DOTNET] Asynch Remoting Call Fails > > > I'm trying to get an asynch remoting call to work and I think I'm > missing something simple. I have two console apps: 1 client and the > other hosting > the server object. When I try to do the BeginInvoke: > > IAsyncResult ar = d.BeginInvoke(cb, null); > > I get a runtime error "Cannot load type soap:ServiceClass" followed by > some cryptic text. Do I need to use TCP for this, or can I use > HTTP? Also, the > reference for the client code was made using the soapsuds.exe > utility. Any > thoughts? > > Thanks, > > Sean > > PS> I included the code below in case someone is up to check it out...
