This post is fine.
ASP<span></span>.NET Zero already specifies .AllowAnyHeader()
. How to reproduce this?
It's a header problem, not an origin problem.
No significant impact on performance. Linq queries are compiled and cached by EF Core.
if i dont use the async then the await operators thorws a error.
So don't use await
. Use the sync methods or check out AsyncHelper.RunSync
.
I changed my code to send the email after the using block. Nowit works fine. But is that a good way to do a task outside the using statement?
It is good to not disable filters unnecessarily.
Don't do async void
.
Nest a list in another model.
You are on ABP 1.0.0?
Show code of your worker class.
Did you run yarn
to update abp-web-resources
npm package?
Simply override CreateFilterExpression for IMayHaveTenant
and/or IMustHaveTenant
in your DbContext.
Change ((IMayHaveTenant)e).TenantId == CurrentTenantId
to (((IMayHaveTenant)e).TenantId == CurrentTenantId || (((IMayHaveTenant)e).TenantId == 0)
.