> I tried putting them together on the Server and with same > results. I have book "Remoting with C# and .Net" that states > that each object should have it's on <service> tag and the > same with the client and <client> tag. I do not know if this > is correct or not.....
I haven't heard about this recommendation so far. [1] for example says about the <activated> entry that "Zero or more of these elements can be placed under the <service> or <client> tags." But on the other hand, it also says that "Zero or more elements are allowed" for <service> and <client> within one <application>. Which somehow translates to: it doesn't matter too much ;-) Unfortunately, this brings us back to square one. Ok ... I just re-read your initial post. As you say that the "other classes run locally on your client", the only cause can be that the name in the config file does not match the real class's names. The format for these type="" attributes is "namespace.classname, assemblyname". If all these classes are in the same assembly (I'd believe ImageGrabber.dll according to your description), then these entries should be (on client and server): type="ImageGrabber.ImageGrabber, ImageGrabber" type="ImageGrabber.ITest, ImageGrabber" type="ImageGrabber.IGrabber, ImageGrabber" i.e. the "assemblyname" part after the comma should be the same for all classes. -Ingo [1] http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotne t/html/remotingconfig.asp thinktecture http://www.thinktecture.com In-depth support and consulting for software architects and developers =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
