Firstly, sorry I didn't mean to cross post, my first post should have been
here,
Secondly:
I have a derived class that serializes nicely when run in a dot net client
(v1.1).
However when run from a COM client the serializer constructor produces a
FileNotFound exception when trying to locate the base class' assembly.
The binding log shows that the serializer probes all the COM clients folders
etc but
The serialiser seems to ignore the obvious codebase of the base class as the
source of the assembly.
If I manually copy the base class assembly to every COM client's directory
then it works however this doesn't seem very practical.
I could compare the base class' codebase to the CallingAssembly's codebase
and copy it prior to calling the Serializer's constructor, but surely this
seems very messy to have to do this.
Is this something that the serializer can or should be able to do on its
own, can anyone suggest a better solution.
Thanks
--
Simon Lampen
In search of enlightenment
