New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autofac.Owin Nuget dependencies broken #508

Closed
calebboyd opened this Issue Mar 27, 2014 · 4 comments

Comments

Projects
None yet
2 participants
@calebboyd

calebboyd commented Mar 27, 2014

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...

@tillig tillig self-assigned this Mar 27, 2014

@tillig tillig added bug labels Mar 27, 2014

@tillig

This comment has been minimized.

Show comment
Hide comment
@tillig

tillig Mar 27, 2014

Contributor

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.

Contributor

tillig commented Mar 27, 2014

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.

@tillig

This comment has been minimized.

Show comment
Hide comment
@tillig

tillig Mar 27, 2014

Contributor

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.

Contributor

tillig commented Mar 27, 2014

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.

tillig added a commit that referenced this issue Mar 27, 2014

Incremented everything by 0.0.1
In prep for release of updated packages that use slightly-faster
changing assembly versions. Caused a minor issue (#508) with previous
fix when not all packages were released but version dependency
requirements were updated.
@tillig

This comment has been minimized.

Show comment
Hide comment
@tillig

tillig Mar 27, 2014

Contributor

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.

Contributor

tillig commented Mar 27, 2014

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.

@tillig

This comment has been minimized.

Show comment
Hide comment
@tillig

tillig Mar 27, 2014

Contributor

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.

Contributor

tillig commented Mar 27, 2014

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.

@tillig tillig closed this Mar 27, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment