Assembly dependency version issues 2.1.0.0 vs 2.1.1.0 about abstractions HOT 7 CLOSED

I am working on few things before I can release Abstractions.2.1.2 and the rest of packages depending on it. Would you like to help to speed it up? I would be happy to accept a pull request...

from abstractions.

If you are using individual packages such as MVC or ASP I would recommend not to mix them with Unity composite package. Use all individual packages Unity.Abstactions, Unity.Container, and etc. This way you would guarantee they all depend on the same thing.

from abstractions.

Sorry, wasn't intended as a rant.

from abstractions.

I was kind of joking. Did you resolve the issue?

from abstractions.

I had installed Unity.Containter in one project and Unity.Abstractions in another. All using the latest Nuget packages. The issue was that Unity.Container depended on a newer versions of Unity.Abstractions which wasn't available on Nuget.

I dropped back to an earlier 0.0.1 point release and the dependency versions all match up. It just looked like there was a missing Nuget package for Unity.Abstractions 2.1.1.0 to go along side the latest Unity.Container package.

from abstractions.

I deployed 2.1.1 Sorry for the confusion.
2.1.1 has a small fix for one issue and I thought Container still references 2.1.0

from abstractions.

That's super! Now, running the latest NuGet package versions and my build is now working. Thanks.

from abstractions.