Uli,
What is the type of the target object? Doublecheck that it does indeed
implement the target interface.
It's possible that in your build process some assemblies get overriden
and the one that ends up in the output folder is no the one the type was
built against.
Also doublecheck if you don't have any differences between .NET profile
(client vs full) between your projects.
K
On 21/12/2011 11:09 PM, [email protected] wrote:
I'm developing a client-server application and want to use the castle
dynamic proxy for wrapping remote objects. In my dynamic proxy wrapper
I want to handle remoting-exceptions. For creating the wrapper I use
the method "CreateInterfaceProxyWithTarget".
The whole thing works fine when I run client and server on 2 different
machines and also when I start client and server from the same build
folder where also the Dll is located, which defines my interface (The
interface for which I create a dynamic proxy). The Dll is called
'common.dll'.
When I build my client and my server project to 2 different folders,
my Dll ('common.dll') which defines the interface will be copied to
both folders. When I start server and client from these different
build-folders I get a System.ArgumentException with the message
"target does not implement Interface".
I really don't know, what I'm doing wrong.
Cincerely,
Uli
--
You received this message because you are subscribed to the Google Groups "Castle
Project Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-users?hl=en.
