some assemblies are mapped twice.....

Hi,

I have noticed using the ProcXP (VMMap) that some ASP.NET applications (.NET 4)
load (maps?) some assemblies twice or more.

I use VS 2010 (W7 x64), with the AnyCPU option and tested in 2008 R2 x64 server....the apps are both complied with release/debug options, the result it's the same.

This "problem" can be build with any "blank" (read default) ASP.NET application.

here some examples:

ProcXP images

Could anyone let me know why the assembly are mapped twice (or more), there is a reason ???

PS

if you need, I can provide the blank/default application sample :).

Thx