Unity (Composite) Package Structure

[MohsenAra]

Create Composite Package

Some Package Like NServiceBus.Unity Depend on Unity.Container on Our Project Framework Depend On Unity when run Update package unity.container.dll some time reference to unity.Container folder and some time to unity container

I think this is can be better : Unity Composite Package must be Empty Package and has Dependency to Unity.Abstraction And Unity.Container

[ENikS]

I used to be against the idea, but it looks like people see benefit in it. Could you explain why do you think it is better?

[MohsenAra]

because now Unity.Container assembly can referenced from two package Unity OR Unity.Container Unity.Abstract assembly too can referenced from two package Unity OR Unity.Abstract

Some Some Library Like NServiceBus Referenced To Unity.Container Package So two package be installed same time because of dependency, and assembly reference to two package is randomly maybe package one or two

[ENikS]

I've added it to the plan