Isolated vs in-process changes

[ksgopal4]

Hi Folks,

This is not an issue, but reaching out to see if you can help understand how the out-of-process has so much less code and much less infrastructure compared to the listeners/message-pump classes in in-process. How does the magic work?

Thanks
Gopal

[ksgopal4]

Whilst the documentation for custom bindings for isolated functions is very inadequate, I think this article from a some time ago, has thrown some light on working of the custom bindings.

https://blog.maartenballiauw.be/post/2021/06/01/custom-bindings-with-azure-functions-dotnet-isolated-worker.html

Basically the custom binding has two parts. The older webjob.* assembly works in-process (functions host) and newer functions.worker.* works in the out-of-process (dotnet worker). The newer style assembly contains very little code (mainly attribute classes) and doesnt replace the older style assembly, but works with it.