On the server the deployed version, GetAllSettings method of the HostSettingsAppService throw below exception, but on the development environment it works fine, could give me some guide how to identify the problem?
System.FormatException: Invalid length for a Base-64 char array or string.
at System.Convert.FromBase64_Decode(Char* startInputPtr, Int32 inputLength, Byte* startDestPtr, Int32 destLength)
at System.Convert.FromBase64CharPtr(Char* inputPtr, Int32 inputLength)
at System.Convert.FromBase64String(String s)
at Abp.Runtime.Security.SimpleStringCipher.Decrypt(String cipherText, String passPhrase)
at Viewtance.MES.Configuration.Host.HostSettingsAppService.d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Viewtance.MES.Configuration.Host.HostSettingsAppService.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Abp.Threading.InternalAsyncHelper.d__5`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Abp.Threading.InternalAsyncHelper.d__3`1.MoveNext()
In MPA, on the same server when request a page it will spend more than 200ms to wait the server get response, if request the API (which also requested in the page via AJAX) directly it only needs spend more or less 60ms.
request a page needs to wait more than 200ms will let people feel the page is slowly.
Is there a way to optimize the page loading performance?
It seems the audit logs not delete the records with a interval period automatically, this is a bad design.
I am running a test application with multi background workers to insert record per second to database, after several days the audit log table with supper larger data, it caused the audit log page failed to query.
It needs to be deleted with an interval period using background worker.
ABP 2.1.1 released, when I update the package via nuget to 2.1.1, the project cannot run as there are lots of break changes, is there a plan to release v4.1 with abp 2.1.1, because we want use ABP 2.1.1 in our project.
In my application, there will be large data be queried, sometimes it will timeout to connect database, where I can set timeout for EF core?
I tried add below property in EF Core constructor but it seems it doesn't work, and when using EF migration update database, it will failed because this change.
public MyDbContext(DbContextOptions<MyDbContext> options)
: base(options)
{
this.Database.SetCommandTimeout(180);
}
Can I set it in connection string? Hope you can give me some guides.
Explicit Loading support was introduced in EF Core 1.1.0. With below API
using (var context = new BloggingContext())
{
var blog = context.Blogs
.Single(b => b.BlogId == 1);
context.Entry(blog)
.Collection(b => b.Posts)
.Load();
context.Entry(blog)
.Reference(b => b.Owner)
.Load();
}
As it is using DbContext, is there a way that could use them in IRepository?
In version 4.0.0, in the admin area, if select the language dropdown list, then it always stay on "English" option, if you selected other language, the side bar always display English language resources, but the page could display according selected language resources.
ABP could Building Dynamic Web API Controllers and the namespace of the API could be customized in module initialize, but it seems this cannot be implemented in asp.net core integration, in asp.net core only below configuration available
Configuration.Modules.AbpAspNetCore().CreateControllersForAppServices(typeof(MyApplicationModule).Assembly, moduleName: 'app', useConventionalHttpVerbs: true)
This really not convenient, as I have lots of same name application service in different namespace in the application module.
Could you also make the Dynamic Web API controllers feature available for asp.net core?
As EF Core replaced EF 6.x, migration records also restart, does Zero 4.0 still support upgrade from previous versions? such as Zero 3.4
Can I use multi DbContext (in fact, it is multi database instance) and multi tenancy per database in the same time? Is that will create multi database instance for each tenant?