I am using Nhibernate from about 3 years.Currently Microsoft published Asp.net Identity 2 sample using EntityFramework.But I can't customize Asp.net Identity sample with Nhibernate 4.For this reason i can't get any data by userid.So Which one i should use for my project Nhibernate or Entity Framework 6
I ran across this today. Looks like NHibernate has published a ASP.NET Identity Provider here.
You can also pull down the NuGet package here.
Related
We are looking to migrate our existing application to ASP.NET Core 2.2 , with the reference on the same I am facing some challenges
In the existing system we are using membership but in ASP.NET Core, it is identity; in identity, the default connection is Entity Framework. Can we switch to use ADO.NET connectivity, because we need to migrate the existing data? We are not looking to have Entity Framework in this project.
Please help and suggest
I'm working on porting an ASP.NET MVC application to an ASP.NET Core MVC hosted in .NET Core.
I was excited to see that EF 6.3 can host on .NET Core, since it looks like the EF -> EF Core migration is something that I'd at like to defer (possibly indefinitely).
Looking at Microsoft.AspNet.Identity.* nuget packages, it appears that they don't have dependencies on a particular .NET framework (full or Core) just on Entity Framework 6.1 or greater.
Other than the purist idea that I should just move everything over to core while I'm in the code, is there any reason I can't have an ASP.NET Core MVC application that uses EF 6.3 and Microsoft.AspNet.Identity rather than EF Core and Microsoft.AspNetCore.Identity?
After some experimentation:
It looks like I was wrong and Microsoft.AspNet.Identity.Owin has a dependency on the full .NET framework. So I will revise the question:
Can I use Microsoft.AspNetCore.Identity with Entity Framework 6.3? My key goal here is to avoid biting off the EF -> EF Core migration while getting the rest of my codebase moved to .NET Core.
I'm decided to migrate from .Net classic web api project to .Net core project. Many developers say to me for migration you don't have any concern about code changes, because .net core support package for Ninject, but I don't see any operational example. Please tell me exactly could I use my old api controller from .net classic project in .net core project using Ninject?
ASP.NET core comes with completly new web framework. Regarding your existing controllers from classic web api framework, you can do the following:
rewrite them to fit the new framework
or use Microsoft.AspNetCore.Mvc.WebApiCompatShim, so you can reuse them
Here is the article describing this topic:
https://learn.microsoft.com/en-us/aspnet/core/migration/webapi?view=aspnetcore-2.2
What you don't have to rewrite are dependencies that can be ported to .nestandard. This is also the case of Ninject, because it already supports .nestandard, so if you've already written any Ninject modules you can use them. But the integration with the ASP.NET core looks different, beacause the framework is different. As already commented this link shows the integration:
How to integrate Ninject into ASP.NET Core 2.0 Web applications?
What do I need to do to add Entity Framework for Oracle with ASP .NET 5? I'm going against an Oracle database version 10.2.5.
You will need Oracle Data Provider for .NET (ODP.NET). Please find it in the link below.
http://www.oracle.com/technetwork/topics/dotnet/index-085163.html
I have a ASP.NET MVC 2 project which I could open in VS 2012. But for that project I want to add asp.net identity 2.0. Is ASP.NET mvc 5 mandatory for asp.net identity? As far as I understood can't we separate the UI part from the user store/authentication methods hence there wont be any dependency on mvc 5. If there is any steps which I could follow for using asp.net mvc 2 with identity, please provide advice or the link to read further or any other advice about migration steps.Thanks
Is ASP.NET mvc 5 mandatory for asp.net identity?
No, you do not need ASP.Net MVC5 for ASP.NET Identity 2.0.
However, ASP.NET Identity 2.0 requires .Net 4.5.
please provide advice or the link to read further or any other advice
about migration steps
Here is the Migrating an Existing Website from SQL Membership to ASP.NET Identity Version 1.
Note: Identity V1 is a little bit different from Identity V2, but not much.