Blazor Hot Reload Strategy

[dazinator]

Blazor relies on the runtime ability to dynamically update the IL of an assembly in order to achieve its "Hot Reload" capability.

However this means it's also subject to the limitations of what the runtime can support in terms of its IL modifications.

Yet, the runtime also support unloadable assemblies via Assembly Load Contexts.

I am curious to know why Blazor wouldn't make use of unloadable ALC's to achieve its Reload mechanism. For example instead of dynamically updating an assembly in place via the runtime provided method; Load the modified assembly into a new ALC and drop references to the previous one, allowing it and it's assemblies to be disposed.

This would be how I would typically do dynamic updates for in process plugin assemblies for example in a backend process.

Can anyone comment perhaps on whether this approach was considered and why perhaps it wasn't pursued?