RoadFlow workflow engine upgrade from 3.0 to .NET Core2.2 encountered some problems and solutions recorded here.
1, DLL project framework selected from 2.2 to 3.0, say nothing of this, no problem. Some changes in the focus of the WEB layer.
2, the ORM package upgrade to the latest data, MYSQL upgrade to 8.0.
3, WEB projects in different Startup.cs route:
2.2：
3.0:
4, SignalR different:
2.2:
3.0 unified routing settings added in:
Output 5,3.0 are using asynchronous, synchronous not enabled by default. Not recommended open, change the code output asynchronously.
6, which is experiencing the biggest pit, looking for a long time to find the cause.
This is not set, setting up an encounter Request.Form [ "keyt"] will error, regardless of content post more cosmopolitan error, and is sporadic, good times and bad. Comment out here just fine.
Error reads as follows:
System.IO.InvalidDataException:“Form key length limit 2147483647 or value length limit 2147483647 exceeded.”
7, the release is set to publish a single document, so much more convenient, simply double-click RoadFlow.Mvc.exe running, comes core3.0 run, no need to install the operating environment.
After the release of the directory are also a lot of refreshing:
Only refers to the presentation or publication procedures are not changed often. Once again turn will stop the update EXE execution. Therefore, it is recommended that production projects compiled in a manner not view the release of this changed view content can be updated in a timely manner.
Compiled in a manner not view the release:
Double-click on the project settings:
And reference the package: Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation