-
Notifications
You must be signed in to change notification settings - Fork 17
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
NuGet package depends on legacy AspNetWebApi.Core package #2
Comments
Hi Matt, thanks for the heads up. This is fixed and updated in NuGet: https://nuget.org/packages/Elmah.Contrib.WebApi/1.0.2.0 |
Thanks! |
Looks like the code was changed in the csproj file but that the .nuspec file wasn't updated with the changed dependencies. Should I create a new issue for tracking that? Should now depend on Microsoft.AspNet.WebApi.Core instead of AspNetWebApi.Core. https://github.com/rdingwall/elmah-contrib-webapi/blob/master/build/Elmah.Contrib.WebApi.nuspec |
Hi @mattscully sorry this was an oversight on my part. 1.0.4.0 should be fixed now properly: https://nuget.org/packages/Elmah.Contrib.WebApi/1.0.4.0 |
That did it; thanks! |
With the final release of Web API, the AspNetWebApi.Core package is no longer being used. Could you please update your NuGet dependencies to use the current 'Microsoft.AspNet.WebApi.Client' and/or 'Microsoft.AspNet.WebApi.Core' packages?
You can see this recommendation here:
http://nuget.org/packages/AspNetWebApi.Core
Thanks!
The text was updated successfully, but these errors were encountered: