oh well. indeed than that'S a problem.

although if you are using frequently the same dll's then this can be a
feature: they wouldn't be loaded for a second or third time, there will
be a cached, already loaded version that can be used.

if you still want to unload your assemblies you can open a new appdomain,
load the assembly there and then close that appdomain. that would remove
the assembly from memory.

or you just stick to identifying the version of your assemblies manually
without loading them.

or another possibility: you could use the unmanaged metadata api to
localize these infos in the assemblies without loading them. but then you
would have lotsa unmanaged code with lots of interop calls. that'S hard
to code and also quite a performance loss because every managed<->
unmanaged call has to be marshaled.