Hi all,

I am new with llblgen pro, I am trying to build a client-server application using remoting in .net. The example in the download area describes a very simple scenario, where there is only one class with only one method, and the interface used in client-server communication is hand written (very simple). Now, a real scenario is a little bit more complex, I need to expose all business classes with all base methods and the methods I defined in 'EntityClasses' in 'two class scenario' template (I am using a single database). I made some experiments with Northwind database, I tried to generate a type library needed to write the client with 'SoapSuds.exe' from Northwind.dll, built from visual studio 2003 with these parameters:

Soapsuds.exe -ia:Northwind -gc

(from the \bin directory of the Northwind project generated by llblgen pro)

the message i receive from soapsuds is the following: ''Error: Object reference not set to an instance of an object."

note that on the \bin directory there's also a copy of the SD.LLBLGen.Pro.ORMSupportClasses.NET11 library referenced from northwind project and soapsuds works well with other dll projects not generated by llblgen pro.

Is this the wrong way to get the server interface I need client side?

Thanks a lot.

I've never heard of soapsuds, is that a tool part of the .NET SDK ? (so I can have a look at what it does and what it expects)

soapsuds is a .NET Framework utility that does 2 things basically: It creates XML schemas describing services exposed in a common language runtime assembly. It creates runtime assemblies to access services described by XML schemas. A schema definition can be a local file or it can be dynamically downloaded from the Internet.

You can read more about it here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/html/cpgrfSoapsudsUtilitySoapSudsexe.asp

In a nutshell, I beleive that Pier is trying to use soapsuds to generate a wireframe assembly that can be referenced by the client.

Piere, what you should probably do, is define an interface for your remotable methods. Then have your server objcts implement these interfaces. In the methods that you implement, execute your implemenation for performing the CRUD access. Also note, that if you place the interfaces in a stand alone assembly, you can have your server solution and client solution reference the stand alone assembly.

Does this make sense?