1
Vote

Private method reflection at deserialization

description

Hi

We have the following problem with at deserialization time.

We have task framework (plugin system) and a client server application. We need to send the tasks to the client in order to edit them. All tasks implements an ITask interface that client knows and we display them through a property grid.

The main problem, is that, when we deserialize in client side, Newtonsoft goes through all private methods by reflection and some tasks may fail, because they have some dependencies in the parameters that are not in client side. Therefore we have to transfer also dependency assemblies to the client.

I don´t believe this is a good approach as I would never expect that a serializer "analyze" all my private methods. Is not only a dependency problem, but also probably a performance issue. What do you think?

Thanks.

comments