Ambiguous reference problem (Microsoft.AspNet.Identity & Microsoft.AspNet.Identity.Core)

I am creating a one-page AngularJS application using the latest community VS2015 and ASP.NET 5 etc.

The problem I'm currently experiencing when trying to implement authentication is that I need to use these two namespaces:

Microsoft.AspNet.Identity //Version 3.0.0-beta4 Microsoft.AspNet.Identity.Owin //Version 2.2.1 

but since Microsoft.AspNet.Identity.Owin has a dependency on

 Microsoft.AspNet.Identity.Core 

I keep getting ambiguous reference problems, for example for the UserManager, which exists in both Microsoft.AspNet.Identity and Microsoft.AspNet.Identity.Core.

Has anyone else done this before? Is this a version incompatibility problem or is it just not a complete implementation of Owin ASP.NET 5?

+3
asp.net-core asp.net-identity
Jul 29 '15 at 12:12
source share
1 answer

The Microsoft.AspNet.Identity.Owin package is part of ASP.NET Identity 2, not the latest version that comes with ASP.NET 5. Attempting to link to it will load ASP.NET Identity 2 and cause a strange error that you encounter.

Just a Microsoft.AspNet.Identity link and it should work.

+7
Jul 29 '15 at 13:01
source share



All Articles