Ok, this may be a stupid question but do I need to generate public/private
key pair for each assembly in a single solution?

I am thinking about delay-signing and that'd mean the "signer" must maintain
the key pair for every single assembly separately.  Is this how it's
supposed to be done?

Also, this is kind of on a side note.  I've read somewhere that having a
single combined assembly is better than many smaller separate assemblies -
assuming all assemblies involved are always updated at the same time -, is
this true?  I can understand why from file access point of view(single file
= less frequent fs access, many files = more frequent fs access but then
that single file may be huge).  If employing the combined assembly strategy,
do I need to genereate netmodules for each contained assemblies instead or,
is there a way to combine already generated assemblies into one?

Thanks much in advance.
Jiho