c# - Loading managed assemblies in a unit test project seems to slow Visual Studio 2010 down -

i loading multiple managed assemblies in unit test. assemblies within solution , not third party, not matters. notice visual studio tends increase memory consumption after running tests few times (usually 10) , slows down overall in terms of build times , responsiveness. behavior not surface if particular unit tests not run.

the loaded assemblies used retrieve embedded types , create instances of enum types there no chance of code within assembly causing trouble. tried [reflectiononlyload] naturally not allow creation of type instances.

apparently there no way explicitly unload assemblies once loaded unless entire app domain unloaded.

my question is, unit test projects run under vs process , if so, these loaded assemblies pile up? assume unit test context clean after itself.

"the loaded assemblies used retrieve embedded types , create instances of"

could self modifying code issue

if asm runs in non bounded part of cache rewrites, , has massive hit on speed of execution no logical reason onlooker

with asm must keep dynamic data , instruction data locked apart

read/write dynamic data should stored outside block of memory containing code

http://www.bbcbasic.co.uk/bbcwin/manual/bbcwina.html#cache

the hit huge, 10 times slower

basically asm program should be:

allocate 2048k

[dynamic data]

allocate 4096k

[code]

for flavour of assembly

if can't it, learn how, difference night , day