I'm looking at Side-by-Side assemblies and isolated application solution in Microsoft Windows.

Documentation says:

> 
> A private assembly is an assembly that
>  is deployed with an application and is
>  available for the exclusive use of
>  that application.
> 
> 
> 

and

> 
> Private assemblies must be designed to
>  work side-by-side with other versions
>  of the assembly on the system.
> 
> 
> 

However, the deployment process for private assembly is just copying assebly into application's folder (or subfolder with assembly's name). Thus, application can not use more than one version of private assembly. Because if you put another version of private assembly - it'll overwrite old version.

Can someone explain this to me?

If this is indeed so - then what are advantages of such assemblies over usual DLLs with redirection? They seems pretty the same to me and manifest seems not even be used here.