Hi,
Is there any error log?
The administration and identity are the basis of microservices, If you remove them, the microservice template will not work.
You can configure the AbpJsonOptions
https://docs.abp.io/en/abp/latest/JSON#abpjsonoptions
services.Configure<AbpJsonOptions>(options =>
{
options.OutputDateTimeFormat = "yyyy-MM-dd";
});
We follow ABP modular practice (Instead of Application Template, we develop Module Template), so what is the correct place to put the above Custom Filter, IN Module.EntityFrameworkCore or my Tiered Application.EntityFrameworkCore?
You can add a custom filter both in Module.EntityFrameworkCore and Application.EntityFrameworkCore
Also, how can I make sure that when I am creating a Module and Tiered Application via ABP SUITE, it is Host-only and does not have Tenant or Edition?
https://docs.abp.io/en/abp/latest/Multi-Tenancy#abpmultitenancyoptions-enable-disable-multi-tenancy
Multi-Tenancy is disabled in the ABP Framework by default. However, it is enabled by default when you create a new solution using the startup template. MultiTenancyConsts class in the solution has a constant to control it in a single place.
By default does the ABP suite include Tenant Management & Edition Management in the application?
Yes, it's
Hi,
"RemoteServices" :{
"TestIntegrationService": {
"BaseUrl": "https://localhost:44302/", // The internal URL for the service(Internal private network),
"UseCurrentAccessToken": "false"
}
}
Format datetime for all API responses
can you elaborate
Hi,
Could you please share the ABP version, Suite version, and the steps to reproduce? I will check it. thanks.
This is my test code:
public class QaPermissionDefinitionProvider : PermissionDefinitionProvider
{
public override void Define(IPermissionDefinitionContext context)
{
var test = context.AddGroup("TestGroup");
test.AddPermission("TestPermission", new FixedLocalizableString("TestPermission")).AddChild("TestChildPermission", new FixedLocalizableString("TestChildPermission"));
}
private static LocalizableString L(string name)
{
return LocalizableString.Create<QaResource>(name);
}
}
And you can open the Swagger page to test the API:
Looks like the client packages are already restored.
Can you see them in the wwwroot folder?
If you can share a reproducible project with me I will check it and help you solve the problem quickly. My email is shiwei.liang@volosoft.com