Service hot update

[cysharp]

Service hot update

[neuecc]

Thank you! and very interesting.

Maybe, it is related to Grpc.Core.Server.
I can only think of the following way.
server.Kill -> new Server(MagicOnionServiceDefinition) -> server.Start

[parkycai]

Kill the server will cause a disconnection to the client. Or will the client automatically restore the connect, even the stream connection won't notice the disconnection (logic level)?
Anyway, I guess I have to dive into Grpc Server to find out a way to replace logic assemble during runtime. Thanks!

[parkycai]

Hi, I took some time this weekend and dig out the approach. I used some reflections so no need to modify the grpc source.

Note:

1. Assemblies can be loaded from raw binary dll files, so it can be overwritten in runtime.
2. Remember to clean up old assemblies after the update.

[aidapsibr]

@parkycai Problem you will run into is unloading assemblies is only supported through unloading entire AppDomains. It is a Framework only feature (not core) and very complicated.

[parkycai]

@psibernetic agreed. By "clean up old assemblies" I means dispose any resources used by the assemblies. So this is a comprimise, that I don't need to make any inter-appdomain communication but only waste acceptable amount of memory.