OK,thanks!
I used the ：https://community.abp.io/articles/using-elsa-workflow-with-the-abp-framework-773siqi9 I guess replace ElsaContext with AbpDbContext
Please give me some advice,thanks!
I found the problem； The custom defined module is not upgraded to 4.4.0。
There is too little exception information ：）
There is no change！
run *.HttpApi.Host:
There is no process associated with this object
rollback to 4.3.3 ,all going well.
run *.DbMigrator：
System.NullReferenceException HResult=0x80004003 Message=Object reference not set to an instance of an object. Source=Volo.Abp.Core StackTrace: at Volo.Abp.AbpApplicationWithInternalServiceProvider.Dispose()
My code is canceled, stack no message. stack = null.
1、 use abp update cli 4.3.3 Upgrade to 4.4.0 2、 do not change the solution structure 3、 *.DbMigrator and *.HttpApi.Host project runtime exception: Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object. code position: application.Initialize() ，not stack message.
Whether there is an upgrade tutorial?
I misread it. That's it。 thank you liangshiwei laotie!!!
Results still the same, login button cannot be clicked;
hi, abp team
If you're creating a bug/problem report, please include followings:
runtime: centos&docker nginx(static html)
I packaged the angluar project on my local Windows system and deployed it as a static file on nginx on my centos server; pack cli : yarn build:prod
There is no exception on the page, but the login button cannot be clicked;
My doubts： 1.Whether the angluar project must be on linux to build? 2.Is there a Dockerfile scheme for reference?
