Can You Really Use ASP.NET Core 3.1 to Build Production Web Pages/Apps?
-
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
-
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
.NET Core 2.2 reached "end of life" back in December: .NET Core 2.2 will reach End of Life on December 23, 2019 | .NET Blog[^] .NET Core official support policy[^] The 2.x "long-term support" version is 2.1, which will be supported until August 2021. The other LTS version is 3.1, which will be supported until December 2021. I've got a small custom CMS template which we use for creating basic sites for some of our customers, and for our own websites. It started life in 2.1, and the latest version is in 3.0; I haven't encountered any significant issues. It's using the
Microsoft.AspNetCore.Identity.EntityFrameworkCorepackage, matching the version of the package to the version of .NET Core in the project.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
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 started with V2.0, and made it to V2.2 and still using it. I have no issues with V2.2 at all, everything works together and it's durable/reliable. I thought about moving up to V3+, but wanted to finish my project on a stable platform first before moving up. But I don't use Identity and EF Core anymore, threw that out the window when I figured out that it's too complex to keep up with. It was more trouble than it was worth so I just went with Google SignIn with OAuth2 that I wrote on the side. I ended up writing code to support GMail and Signin part of the Google suite which was available as a NuGet package with little documentation.
If it ain't broke don't fix it Discover my world at jkirkerx.com
-
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 started with V2.0, and made it to V2.2 and still using it. I have no issues with V2.2 at all, everything works together and it's durable/reliable. I thought about moving up to V3+, but wanted to finish my project on a stable platform first before moving up. But I don't use Identity and EF Core anymore, threw that out the window when I figured out that it's too complex to keep up with. It was more trouble than it was worth so I just went with Google SignIn with OAuth2 that I wrote on the side. I ended up writing code to support GMail and Signin part of the Google suite which was available as a NuGet package with little documentation.
If it ain't broke don't fix it Discover my world at jkirkerx.com
-
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
On a current project which is a large system that consists of multiple microservices, we use .net core 3.1 since Richard Deeming correctly mentioned that it has long term support by Microsoft unlike .net core 3.0. It worth mentioning though that we don't use Identity and rely on your in house authorization mechanism. There are no problems with EF Core though.
