Updating to ASP.NET Core 3.1 #5737
Replies: 35 comments
|
(Now we know what you did over Chrismas... :-)) Good to see you back in full action :-) Wish you a great, successful 2020. With kind regards, John |
|
Great news, |
|
great!has adminLTE also upgraded to 3? |
|
Great job! Thank you very much @volkanceylan ! |
|
Thank you @volkanceylan for your hard work and progress on Serenity - my favourite framework! I followed this guide on my project and I'm getting a warning and error about Razor. Maybe this is just something that I've done? It mentions removing the My environment before upgrade:
Has anyone else migrated and/or run into this issue? Thank you, |
|
Thank you for update. Kindly request you to please prepare and share Migration tutorial of Serenity MVC to .NET core version. Thanks. |
|
@edwardch need your CSPROJ file references section |
|
Here we go <ItemGroup>
<PackageReference Include="Azure.Storage.Blobs" Version="12.1.0" />
<PackageReference Include="CsvHelper" Version="12.2.3" />
<PackageReference Include="DocumentFormat.OpenXml" Version="2.9.1" />
<PackageReference Include="Hangfire.AspNetCore" Version="1.7.8" />
<PackageReference Include="HangFire.Core" Version="1.7.8" />
<PackageReference Include="HangFire.SqlServer" Version="1.7.8" />
<PackageReference Include="MailKit" Version="2.4.1" />
<PackageReference Include="Mapster" Version="4.1.1" />
<PackageReference Include="Microsoft.TypeScript.MSBuild" Version="3.7.4" />
<PackageReference Include="Microsoft.VisualStudio.Azure.Containers.Tools.Targets" Version="1.9.10" />
<PackageReference Include="Serenity.FluentMigrator.Runner" Version="1.6.904" />
<PackageReference Include="Serenity.Pro.Scripts" Version="3.9.10" />
<PackageReference Include="Spire.XLS" Version="9.12.20" />
<PackageReference Include="StackExchange.Exceptional.AspNetCore" Version="2.1.0" />
<PackageReference Include="Microsoft.Data.Sqlite" Version="3.1.0" />
<PackageReference Include="Telerik.Reporting" Version="13.0.19.222" />
<PackageReference Include="Telerik.Reporting.OpenXmlRendering" Version="13.0.19.222" />
<PackageReference Include="Telerik.Reporting.Services.AspNetCore" Version="13.0.19.222" />
<PackageReference Include="EPPlus" Version="4.5.3.2" />
<PackageReference Include="FastMember" Version="1.5.0" />
<PackageReference Include="Serenity.Web" Version="3.12.0" Condition="!Exists('..\..\Serenity\Serenity.Core\Serenity.Core.csproj')" />
<PackageReference Include="Serenity.Web.Assets" Version="3.9.2" />
<PackageReference Include="Serenity.Scripts" Version="3.12.0" />
<PackageReference Include="Microsoft.AspNetCore.Mvc.NewtonsoftJson" Version="3.1.0" />
<PackageReference Include="Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation" Version="3.1.0" />
</ItemGroup> |
Hi @edwardch , found that you are using telerik reporting.. Can you please help me on implementation of telerik reporting on serenity project. skype Id: mustafalotiya@gmail.com Regards, |
|
@mustafalotiya I have this working in .NET MVC, and working 95% in .NET Core. The catch in .NET Core is that the reports are not finding my named connection string. Reports that do not use a connection string do work though. I got paid-for support from Volkan to help me set this up initially for the .NET MVC version, and I plan on fixing that connection string issue first before creating a tutorial on how to do that. I will post an issue to announce when the tutorial is complete. |
As of now my all developments in Serenity MVC framework and looking for good reporting tool. it would be great help. |
|
@edwardch I had a similar problem but it only showed up after I tried to publish the app, so in my case it was related to my publish setup. |
|
@RouteTech I haven't got any publish profiles, but I'm interested to know what you had different in your publish profile to what was on your local/dev environment? |
|
@edwardch Telerik.Reporting.Services.AspNetCore 13.0.19.222 probably has reference to ASP.NET Core 2.0, as the package is private i can't check deps |
|
Ah that makes sense, thank you for that feedback. I'm happy with the solution and looking forward to getting my upgrades into production! |
|
Thanks for the upgrade guide. Worked great, except the build task "CompileTSC" keeps giving the following error message when building: The build task in project file looks like this: on investigation looks like "tsc.exe" is not part of 3.7.4 Typescript SDK anymore. Any suggestions for fixing? |
|
@she-ll-b-rite you should first follow other upgrade guides: |
|
hi, i'm trying serenity for the first time. it's probably a newbie mistake... but any help would be great |
My bad. Thanks 👍 |
To anyone that has the same problem, I resolved this by adding an empty object {} inside secrets.json |
|
Does anyone know if dotnet sergen servertypings should be still inside building process? I guess I am missing it somehow. Thanks! |
Nvm, I replaced the wrong build tag inside web.csproj. |
|
@vitorsilva Hi |
|
so how do I run Sergen now ? |
I have the same problem as @vitorsilva. VS2019 - Serene - ASP.NET Core 2.2 -> 3.1. |
|
@zhiwenchong for me, this was caused by the fact, that no all the files were installed. |
|
Nice job! |
|
Hi, I just updated from 2.2 to 3.1. Sadly I hade a problem with the IF COREFX and IF !COREFX Parts. I don't know why and what this is doing, but now (for now) its workling. Any ideas? |
|
Thank you sooo much for taking the time to write this up, it was effortless to move across! |

Uh oh!
There was an error while loading. Please reload this page.
Starting with 3.12 Serenity supports ASP.NET Core 3.1, and this is an upgrade guide for those who use .NET Core version and wish to upgrade to .NET Core 3.1.
Important Warnings:
Steps to Upgrade to ASP.NET Core 3.1:
with:
with:
with:
And replace this line:
with:
and remove the first ItemGroup closing tag, and ItemGroup opening tag with Condition so that it looks like this (we are just merging item groups and removing the unused condition):
Eventually your ItemGroup should look similar to this (for Serene):
so that it looks like this:
with this (insert dotnet tool restore line):
to this:
with:
with:
Edit Initialization/DataMigrations.cs, SergenEdpoint.cs, and EmailHelper.cs. Replace IHostingEnvironment with IWebHostEnvironment (there should be five or so).
Rebuild the solution and make sure there are no errors.
It was a long upgrade guide but unfortunately there are too many changes in ASP.NET Core and .NET Core themselves. You may look at following guides to see how complex it is (particulary the first one):
https://docs.microsoft.com/en-us/aspnet/core/migration/22-to-30?view=aspnetcore-3.1&tabs=visual-studio
https://docs.microsoft.com/en-us/aspnet/core/migration/30-to-31?view=aspnetcore-3.1&tabs=visual-studio
All reactions