sorry but this is not supported. you can only generate code in your application or in the module solution itself. you cannot generate code across modules and application.
Each module can define its database table prefix. For example Blog module sets its database table as Blg. This is done in the module. See BloggingDbProperties.cs . If you want to overwrite this prefix you can do it in your Domain Module class as below.
Volo.Blogging.BloggingDbProperties.DbTablePrefix = "Xyz"
For Identity Server module you can set it as below
Volo.Abp.IdentityServer.AbpIdentityServerDbProperties.DbTablePrefix = "Ids";
This behavour is same for other modules as well.
The essential framework modules have Abp prefix. Check out the documentation
https://docs.abp.io/en/abp/latest/Entity-Framework-Core-Migrations#table-prefixes
In your application, your table prefix is App by default. You can change this in the following file:
Acme.BookStore\src\Acme.BookStore.Domain\BookStoreConsts.cs
namespace Acme.BookStore
{
public static class BookStoreConsts
{
public const string DbTablePrefix = "Xyz"; //<----- this is the variable to set your table prefix
public const string DbSchema = null;
}
}
This change requires the re-creation of migrations. To do this; delete your existing migrations in the Migrations folder Acme.BookStore.EntityFrameworkCore.DbMigrations\Migrations\ and then add migrations using add-migration Initial
Publish your Angular application and copy the output to wwwroot of your Host. Then a middleware like this in the Host side
app.Use(async (context, next) =>
{
await next();
if (context.Response.StatusCode == 404 && !Path.HasExtension(context.Request.Path.Value))
{
context.Request.Path = "/index.html";
await next();
}
});
You can use SetSubItemOrder method to set an order in YourProjectMenuContributor.cs class.
private static async Task ConfigureMainMenuAsync(MenuConfigurationContext context)
{
var l = context.GetLocalizer<SAMResource>();
context.Menu.AddItem(new ApplicationMenuItem(
SAMMenus.Home,
l["Menu:Home"],
"/",
icon: "fas fa-home",
order: 1
));
//Administration
var administration = context.Menu.GetAdministration();
administration.Order = 2;
//Administration->Saas
administration.SetSubItemOrder(SaasHostMenus.GroupName, 1);
//Administration->Identity
administration.SetSubItemOrder(IdentityProMenus.GroupName, 2);
//Administration->Language Management
administration.SetSubItemOrder(LanguageManagementMenus.GroupName, 3);
//Administration->Text Template Management
administration.SetSubItemOrder(TextTemplateManagementMenus.GroupName, 4);
//Administration->Audit Logs
administration.SetSubItemOrder(AbpAuditLoggingMenus.GroupName, 5);
//Administration->Settings
administration.SetSubItemOrder(SettingManagementMenus.GroupName, 6);
}
In the microservice structure, we add Application.Contracts packages of all modules to the gateway.
Thus, all permissions can be available and we can get them from the gateway.
For example, In the microservice demo application, the BackendAdminAppGateway.Host project has references
https://github.com/abpframework/abp-samples/blob/master/MicroserviceDemo/gateways/BackendAdminAppGateway.Host/BackendAdminAppGateway.Host.csproj
In this project you can see Application.Contracts of Blogging and ProductManagement module are added.
<PackageReference Include="Volo.Blogging.Application.Contracts" Version="3.2.1" />
<ProjectReference Include="..\..\modules\product\src\ProductManagement.HttpApi\ProductManagement.HttpApi.csproj" />
Also essential references of the other cross-cutting featured projects are added. Eg: PermissionManagement, FeatureManagement, and SettingManagement
<PackageReference Include="Volo.Abp.PermissionManagement.Domain.Identity" Version="3.2.1" />
<PackageReference Include="Volo.Abp.PermissionManagement.Domain.IdentityServer" Version="3.2.1" />
<PackageReference Include="Volo.Abp.PermissionManagement.Application" Version="3.2.1" />
<PackageReference Include="Volo.Abp.PermissionManagement.HttpApi" Version="3.2.1" />
<PackageReference Include="Volo.Abp.PermissionManagement.EntityFrameworkCore" Version="3.2.1" />
So the gateway does not route the permission request but sends its own.
Check out Microservice Demo document.
You can also set up a seperate microservice for only Permission Management but it will be unncessary as it's not a part of the business logic.
hi @JmBdo, there's currently no doc for CI/CD pipelines. But you can follow this official Microsoft document. It can be applied to ABP projects. If you block in any step, feel free to ask.
seems like an Identity Server misconfiguration. check your database table IdentityServerClientRedirectUris
Hi, this was inside the Angular app before but we have moved it to the MVC project because we started to use Authorization Code Flow in v3.1. See the related blog post https://blog.abp.io/abp/ABP-Framework-v3.1-RC-Has-Been-Released
after this change account related features are also moved to MVC side.
for your second question @mehmet can you check it out?