Closed calebboyd closed 10 years ago
I can look into fixing the issue with 3.0.0-alpha2, but I can't retroactively go back and fix the dependency requirements on the explicit install of 3.0.0-alpha. The explicit install thing is broken because of the namespace change; I'm still working through the dependency conflict issue.
OH, I see what happened. It's because we also fixed issue #502. Assembly versions changed.
It looks like I'll need to do some 0.0.1 releases of everything so the assembly versions line up.
After updating all the package versions and requisite dependencies (in a test environment) everything can get added, has the right minimum versions, and I can get a single application with literally every Autofac package in it and no conflicts or warnings show up. I'll publish shortly.
New packages pushed. Taking the update will end up requiring all of the Autofac-related stuff to update so all the assembly versions line up again, but this should be a one-time hit. There really wasn't a way around it since different packages now require a slightly-faster-changing version due to #502.
I just created a new Web API app and added the -alpha3 version of the Autofac Web API OWIN integration from the public NuGet feed and built - no conflicts or errors. I think we're good to go. Let me know if the issue persists.
Adding Autofac.WebApi2.Owin 3.0.0-alpha2 via nuget does not work.
Can be replicated by creating a new C# WebApplication under .NET 4.5.1. and
Install-Package Autofac.WebApi2.Owin -Pre
Also, Installing explicitly 3.0.0-alpha actually pulls in AutoFac.Owin-alpha2. And is thus broken.
Currently I'm just explicitly installing Autofac.Owin-3.0.0-alpha and Autofac.WebApi2.Owin-3.0.0-alpha
probably from this namespace refactor: commit...