In our case we'll have to use a code generator. But before compilation I make some adjustments for easier handling at runtime within the service. The built assembly is then published. So all applications who need it can load it into its own assembly or better in an own assembly load context.

Yeah it's, there is one problem though, my colleagues haven't worked with reflection so much.

I created a singleton service which takes care of the heavy lifting to handle all dynamic model classes and jack into the assembly resolver. To ensure that we only load one class to prevent casting problems. Hopefully my colleagues will learn something.

To prove my point I built a small application which uses json schema as a base for describing the model. I use the schema to create a model class on-the-fly which I compiled into a dll-file. I can then load the newly created file. This way I can easily validate and cast it to a strongly typed model.

Did I mention that all networks can be accessed via ethernet and wifi. It took about three weeks to set it all up.

And one network for guests secured the same way as family devices but also bandwidth limitation. And last, but not least a company segment with extremely strict policy which only permits vpn traffic to a certain address and only registered devices can use this network.