Thanks for the reply.
I got the problem on every call to a .NET assembly.
It seams the TestStand installation was messed up.
After reinstalling TestStand, it was able to use the .NET classes.
However, the is still another problem using .NET remoting with in TestStand.
I instantiate a .NET class in TestStand send it serialized to the RemotingServer
and trigger a measurement. After a call is returning there is a exception occuring in
TestStand which say that the class returned from the server is not available since
the assembly of the class is not present at TestStand side.
But it is present since the object I have sent has the same type as the received one,
however it is not the same instance.
Is TestStand using another AppDomain or Context to create .NET classes?
What else can this be?
Best Regards
Markus