Unity.Abstractions 4.1.3 not compatible with Unity.Container 5.10.0

[mjeanrichard]

Unity.Abstractions 4.1.3 not compatible with Unity.Container 5.10.0

[mjeanrichard]

I just managed to write a test. It seems to have something to do with the SingletonLifetimeManager.

namespace UnitTestProject1
{
  public interface ITest
  {
  }

  public class Test : ITest
  {
  }

  public class Test2 : ITest
  {
    private readonly IEnumerable<IInner> _tests;

    public Test2(IEnumerable<IInner> tests)
    {
      _tests = tests;
    }
  }

  public interface IInner
  {
  }

  public class Inner : IInner
  {
  }

  [TestClass]
  public class UnitTest1
  {
    [TestMethod]
    public void TestMethod1()
    {
      UnityContainer container = new UnityContainer();

      container.RegisterType<ITest, Test>(nameof(Test), new TransientLifetimeManager());
      container.RegisterType<ITest, Test2>(nameof(Test2), new TransientLifetimeManager());

      container.RegisterType<IInner, Inner>(nameof(Inner), new SingletonLifetimeManager());

      IEnumerable<ITest> enumerable = container.Resolve<IEnumerable<ITest>>();

      Assert.AreEqual(2, enumerable.Count());
    }
  }
}

[ENikS]

Unity.Container 5.10.0 works with Unity.Abstractions 4.1.1.

Unity.Abstractions 4.1.3 requires Unity.Container 5.10.3

If you decided to upgrade the container, why not upgrade Abstractions as well? Perhaps use composite Unity package to get matching set?

Feel free to reopen if issue persists with matching packages

[mjeanrichard]

The Issue happend in the following constellation:

Project A (a Nuget Package) references:

• Unity.AspNet.WebApi 5.10.0

Project B references:

• Unity.Abstractions 4.1.3 (because it needs this directly)
• the Package created in Project A (and therefore gets the reference to Unity.AspNet.WebApi 5.10.0)

With Project B you get the described Error, because nuget will fullfill the dependency on Unity.Container from Unity.AspNet.WebApi with Version 5.10.0).

To me it was just a bit confusing, that there is a breaking change from one Patch Version to the next. But everthing is solved by explicitly referencing the right packages.