FastMember, as glorious as it is and as easy as it makes reflective member access/setting, emits IL at runtime in order to be as efficient as it is. For our purposes of making an AoT-based installer, this doesn't work.
Proposals
The first thing we should do is investigate the process in which variables get updated. If we can handle it by some other means, there's a great chance to get away from reflection entirely. For instance, can we put all variables inside of some "variable soup" mixture and then use source generators to reconstruct them?
Short of any of this - resort to using regular reflection.
Context
FastMember, as glorious as it is and as easy as it makes reflective member access/setting, emits IL at runtime in order to be as efficient as it is. For our purposes of making an AoT-based installer, this doesn't work.
Proposals
The first thing we should do is investigate the process in which variables get updated. If we can handle it by some other means, there's a great chance to get away from reflection entirely. For instance, can we put all variables inside of some "variable soup" mixture and then use source generators to reconstruct them?
Short of any of this - resort to using regular reflection.
Interested Users
Husky Developers