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...
