Library load issue about protobuf.services HOT 3 OPEN

The types are loaded when the proto channel is first initialized in case of server and for the first requests in case of clients. In both the latter instances it is done as the library finds all the related types for the data contracts in question, these types are then used to build a tree which is cached for sending to the client (only the server does this operation, in case of clients, it requests the server for the output of this search). As the lib now does not know in which libraries it is supposed to be looking for child types of the orginal data contract, it looks everywhere.

I meant to refactor this and find a more efficient method (and now I have the motivation), in the meantime if you are seeing an error it is because there is some assembly which is referenced in your host project (server side) which cannot be found, you should locate that reference and remove it from the project. The latter although is an issue in the server side host project, but since it does not impact normal workings of any other WCF channel, it should not impact the proto channel as well and I will fix the same hopefully by this weekend.

from protobuf.services.

Thanks for a really quick response. That's a great news. Using your library is very convenient vs the plain protobuf-net, so you may expect some other input from my side shortly.

from protobuf.services.

hmmm... went looking further into this.... short of exposing the exclusion list as a configuration, there is no way for shortening it, the code maps the types and its children in order to make it possible for protoBuf to work across servers and clients.

This loading of assemblies only results in slowing the first request to the server and for the client, its first request to the server, this should not be an issue.

There is a scenario where if a referenced assembly does not exist in the bin folder (or GAC) the server errors out, but since this should be fixed at the server anyway and will never be an issue for clients, I'm gonna ignore this for now instead of adding more configurations, let me know what you think.

from protobuf.services.