I have not tried it any other way. What I'm looking for is some advice. How
does the .Net runtime load assemblies? Does it put everything into memory?
If so, I would expect that it does matter how much stuff you embed into an
assembly and we would not want to do so.

If it does not and it's smarter about just pulling out what it needs, but
keeping the entire assembly out of memory, then it would certainly be easier
to maintain by keeping the data in there.

I can certainly run some performance and profiling tests, but I'm just
shocked that no one seems to know anything about best practices in this area
( or this is just being ignored because no one really has an opinion ) and
I'm not finding anything anywhere. In general, I like to back up my own
testing with a general consensus and best practice that is out there. I'm
just not finding it for this topic. I changed the subject on this post, so
maybe that will help

Regards,

Andrew Elmhorst