I have developed a windows application in .net 3.5. While runing the application many times i encounter "out of memory" exception, since my application loads alot of assemblies. However when i observed the process (of the application) in VMMap (http://technet.microsoft.com/en-us/sysinternals/dd535533) i found CLR maps assemblies into the virtual address space twice, which occupies most of the virtual space.
Can anyone please help me out in understanding that why CLR maps the assemblies twice and cosumes important virtual address?
Moreover if there is any workaround available?
I am using Visual studio 2008 (.net framework 3.5).