Hi, I've been working on a web portal using ASP.NET Core 3.1 and I keep running into weird errors between Identity and EF Core. I've gone through several complete rebuilds and tons of errors and problems. when I build little web apps or separate Identity and EF Core then everything works just dandy. But when I try to bring them all together in a rather large production web app all of a sudden weird bugs crop up.
I've read that the Identity and EF Core teams work separately and sometimes there are problems between their releases...So I am wondering:
Is ASP.NET Core 3.1 not yet ready for prime time for building web apps?
Is there anyone here that is actually using it successfully in a production environment?
And if so, are there some tricks/suggestions for doing so?
Or should I use Core 2.2? Is that stable enough for production apps?
I know that this is a general question without going specifically into the bugs I've encountered. The bugs are many and variable and the code is too large to summarize here. If no one answers this then that will be my answer. If some people do answer but cannot confirm that they are using it in production then that will be my answer as well. And if some people tell me that I should not be using it right now that will be my answer as well.
In the other case, if people tell me that this is a known problem then perhaps they will be able to point out a workaround. Else I will have to abandon Identity and EF Core and build my own implementations directly. I've been thinking that I should have done this from the beginning, perhaps using Dapper instead of EF Core.
Thanks,
- Grant
I've read that the Identity and EF Core teams work separately and sometimes there are problems between their releases...So I am wondering:
Is ASP.NET Core 3.1 not yet ready for prime time for building web apps?
Is there anyone here that is actually using it successfully in a production environment?
And if so, are there some tricks/suggestions for doing so?
Or should I use Core 2.2? Is that stable enough for production apps?
I know that this is a general question without going specifically into the bugs I've encountered. The bugs are many and variable and the code is too large to summarize here. If no one answers this then that will be my answer. If some people do answer but cannot confirm that they are using it in production then that will be my answer as well. And if some people tell me that I should not be using it right now that will be my answer as well.
In the other case, if people tell me that this is a known problem then perhaps they will be able to point out a workaround. Else I will have to abandon Identity and EF Core and build my own implementations directly. I've been thinking that I should have done this from the beginning, perhaps using Dapper instead of EF Core.
Thanks,
- Grant