The reaseon for the problem was, that the DLL resided on client side in
the app directory,
what shouldn't happen. In that case the server searched for an unknown
reason in the GAC.
But If I have installed the DLL into the GAC of the server, other
classes are 'not serialized', but
have to be serialized.
So it might be that Windows seems to do serialization, if a remote DLL
is located on client
side and I explicitly create an enterprise service object.
After removing the client side DLL, that haven't to be there, also the
serverside doesn't has a
look for that DLL in the GAC.
A question: Why could the object instantiated for the first, say, three
functions, but then
not anymore ?
Lothar
Prabakar Samiyappan schrieb:
[quoted text, click to view] > The reason for your problem is you have a depended dll for the existing d=
ll
> which you use in your application.
>
> The reason for working in the local is the dll is present in the private =
or
> shared assembly of that machine. Check whether all the dependencies are
> present .
>
>
> "lothar.behrens@lollisoft.de" wrote:
>
> > Hi,
> >
> > I have a serviced component, that exposes a class I am able to use some
> >
> > methods from.
> > But one of the methods in my application flow then throws this
> > exception:
> >
> >
> > System.IO.FileNotFoundException: Die Datei oder Assembly Voil,
> > Version=3D1.0.0.0, Culture=3Dneutral, PublicKeyToken=3D0f47ce5265036a51=
oder
> > eine Abh=E4ngigkeit davon wurde nicht gefunden. Das System kann die
> > angegebene Datei nicht finden.
> >
> >
> > If I run the classes in local mode on my development system, all works
> > fine.
> >
> > If I test the component via a vbs script, the function can be called.
> >
> > I have updated the assemblies, that must be in the GAC. I have
> > recreated the proxy classes.
> >
> >
> > The software runs with .NET 2.0.
> >=20
> >=20
> > Any help ?=20
> >=20
> >=20
> > Thanks, Lothar
> >=20
> >
