mcrossley wrote:OK, unless you are getting the exception I don't think it was picking up the new file.
I had a quick look this morning, I don't think MX can be made to use an updated DLL without MX being recompiled - because the public key of the assembly will change (or be removed )when I compile it.
I think you are right.
In the first test I've replaced the dll when MX was running. Now I see that is not a stable situation.