ASP.NET Core 2.0 Supported?

pacal / NPoco_Identity_Provider

Identity provider replacement for the default asp.net Entity Framework based provider

MIT License

4 stars 5 forks source link

ASP.NET Core 2.0 Supported? #1

Open bradbamford opened 7 years ago

bradbamford commented 7 years ago

Does this provider work with ASP.NET Core Identity in a Core 2.0 project?

pacal commented 7 years ago

Currently it does not, rather I have not tested it any .Net Core releases. Ill use this issue to track testing of it. Thank you for showing interest in the project, I will try to take a look at it over the US Thanksgiving Holidays as time permits.

bradbamford commented 7 years ago

That sounds great; the only documentation I could find was migrating from Core 1x to Core 2.

Edit: Okay, found a great Dapper example, shouldn't be too different from NPoco.

I look forward to your findings.

pacal commented 6 years ago

As it stands currently it will NOT work due to the a few things

Being compiled against .net 4.52 (the nuget rather)
Using the Microsoft.AspNet.Identify.Core (which is targeted towards .net Framework) namespace and its interfaces VS Microsoft.AspNetCore.XXXX (which is the newer cross platform net core)

This is based on a an Asp.net Core 2 website using individual accounts. As stated above the namespace, interfaces etc have changed up a bit from the original .net Identity I'm looking at what it would take to port it over to Core 2

pacal commented 6 years ago

Just and Update. I haven't forgot about this request, "Real life" work etc keeping me busy along with all the holiday baggage. My goal is to port it over to Net Core 2 and replace it in the net core 2 webapp template using NPoco if possible. I am looking at the Schema of the new providers as well as the interfaces provided.

HARDYLARDY commented 6 years ago

Just wondering if have you managed to look into this? Would be good to see what you have achieved so far.

pacal commented 6 years ago

Sorry all. My current work schedule is pretty hectic as I am coding etc almost everyday at work. I have been chipping away slowly.. But this it will not be a branch but a separate repo. So much has changed between the two. I don't have an ETA sorry, but It is essentially a rewrite.

HARDYLARDY commented 6 years ago

Completely understand. I have instead used my own code, slim down version but works a treat.