Activities of "abpVAndy"

• ABP Framework version: v4.4.0
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• Steps to reproduce the issue:"

I use suite to create module template. I try to create many products for testing. Some products(module template) could create angular code. Some products cannot. "aaaaa" could create angular part code. but "Pu.MoonStore" cannot. pls check below info. But both could create mvc part code.

Where could it be wrong for using the suite to create module template? Thx

I also try to update suite, it also same issue. I follow this link to update and test. https://support.abp.io/QA/Questions/414/ABP-Suite-install-problem https://support.abp.io/QA/Questions/1681/ABP-Suite-CRUD-Page-generator-is-not-working-in-latest-version-44

My goal: We want to create module template as library. And also the module angular Ui will be as library into application.

Below is created by suite in abp\suite\appsettings.json. I just copy the two products information:

Please check below .abp\suite\appsettings.json, for two example products. "Name": "aaaaa", and "Name": "Pu.MoonStore",

I try to change abp\suite\appsettings.json for "Pu.MoonStore" to follow the "aaaaa", it still does not work. { "Id": "bbe1a3b5-b065-4fec-8c15-5e25c9096d25", "Name": "Pu.MoonStore", "UiFramework": 2, "AngularSolutionRootPath": "E:\_dev\shop\Pu.MoonStore\angular", "UiFrameworkName": "Mvc", },

=================================================================

{ "Id": "f4c7e0ec-834c-41fb-b4fc-de796a37bda2", "Name": "aaaaa", "UiFramework": 2, "ProjectNameWithCompanyName": "aaaaa", "OnlyProjectName": "aaaaa", "Path": "E:\_dev\aaaaa\aaaaa.sln", "RootProjectDirectory": "E:\_dev\aaaaa", "SrcFolderDirectory": "E:\_dev\aaaaa\src", "TestFolderDirectory": "E:\_dev\aaaaa\test", "WebProjectDirectory": "E:\_dev\aaaaa\src\aaaaa.Web", "DomainProjectDirectory": "E:\_dev\aaaaa\src\aaaaa.Domain", "DomainSharedProjectDirectory": "E:\_dev\aaaaa\src\aaaaa.Domain.Shared", "ApplicationProjectDirectory": "E:\_dev\aaaaa\src\aaaaa.Application", "ApplicationContractsProjectDirectory": "E:\_dev\aaaaa\src\aaaaa.Application.Contracts", "EntityFrameworkCoreProjectDirectory": "E:\_dev\aaaaa\src\aaaaa.EntityFrameworkCore", "MongoDbProjectDirectory": "E:\_dev\aaaaa\src\aaaaa.MongoDB", "EntityFrameworkCoreDbMigrationsProjectDirectory": "E:\_dev\aaaaa\src\aaaaa.EntityFrameworkCore", "MongoDbTestsProjectDirectory": "E:\_dev\aaaaa\test\aaaaa.MongoDB.Tests", "EntityFrameworkCoreTestsProjectDirectory": "E:\_dev\aaaaa\test\aaaaa.EntityFrameworkCore.Tests", "AppliactionTestsProjectDirectory": "E:\_dev\aaaaa\test\aaaaa.Application.Tests", "TestBaseProjectDirectory": "E:\_dev\aaaaa\test\aaaaa.TestBase", "MigratorProjectDirectory": null, "MigratorCsprojFileName": "aaaaa.DbMigrator.csproj", "AngularSolutionRootPath": "E:\_dev\aaaaa\angular", "DefaultNamespace": "aaaaa", "DefaultNamespaceAsCamelCase": "aaaaa", "MigrationsMigrationsDbContext": "aaaaaMigrationsDbContext", "TenantMigrationsMigrationsDbContext": "aaaaaTenantMigrationsDbContext", "DbContextFilePath": "E:\_dev\aaaaa\src\aaaaa.EntityFrameworkCore\EntityFrameworkCore\aaaaaDbContext.cs", "DbContextModelCreatingExtensionsFilePath": "E:\_dev\aaaaa\src\aaaaa.EntityFrameworkCore\EntityFrameworkCore\aaaaaDbContextModelCreatingExtensions.cs", "HttpApiHostProjectDirectory": null, "HttpApiProjectDirectory": "E:\_dev\aaaaa\src\aaaaa.HttpApi", "BlazorProjectDirectory": "E:\_dev\aaaaa\src\aaaaa.Blazor", "StartupProjectDirectory": "E:\_dev\aaaaa\src\aaaaa.Web", "StartupProjectName": "aaaaa.Blazor", "DatabaseProvider": 1, "DatabaseProviderName": "EntityFrameworkCore", "UiFrameworkName": "Mvc", "ApplicationContractsExists": true, "MigratorProjectExists": false, "UpdateDatabaseMethod": 1, "IsTieredArchitecture": false, "ActiveDate": "2021-08-11T12:14:07.7430085-05:00", "ProjectTemplateType": 2, "AbpVersion": "4.4.0" }

 {
  "Id": "bbe1a3b5-b065-4fec-8c15-5e25c9096d25",
  "Name": "Pu.MoonStore",
  "UiFramework": 3,
  "ProjectNameWithCompanyName": "Pu.MoonStore",
  "OnlyProjectName": "MoonStore",
  "Path": "E:\\_dev\\shop\\Pu.MoonStore\\Pu.MoonStore.sln",
  "RootProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore",
  "SrcFolderDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\src",
  "TestFolderDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\test",
  "WebProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\src\\Pu.MoonStore.Web",
  "DomainProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\src\\Pu.MoonStore.Domain",
  "DomainSharedProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\src\\Pu.MoonStore.Domain.Shared",
  "ApplicationProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\src\\Pu.MoonStore.Application",
  "ApplicationContractsProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\src\\Pu.MoonStore.Application.Contracts",
  "EntityFrameworkCoreProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\src\\Pu.MoonStore.EntityFrameworkCore",
  "MongoDbProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\src\\Pu.MoonStore.MongoDB",
  "EntityFrameworkCoreDbMigrationsProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\src\\Pu.MoonStore.EntityFrameworkCore",
  "MongoDbTestsProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\test\\Pu.MoonStore.MongoDB.Tests",
  "EntityFrameworkCoreTestsProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\test\\Pu.MoonStore.EntityFrameworkCore.Tests",
  "AppliactionTestsProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\test\\Pu.MoonStore.Application.Tests",
  "TestBaseProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\test\\Pu.MoonStore.TestBase",
  "MigratorProjectDirectory": null,
  "MigratorCsprojFileName": "Pu.MoonStore.DbMigrator.csproj",
  "AngularSolutionRootPath": null,
  "DefaultNamespace": "Pu.MoonStore",
  "DefaultNamespaceAsCamelCase": "pu.moonStore",
  "MigrationsMigrationsDbContext": "MoonStoreMigrationsDbContext",
  "TenantMigrationsMigrationsDbContext": "MoonStoreTenantMigrationsDbContext",
  "DbContextFilePath": "E:\\_dev\\shop\\Pu.MoonStore\\src\\Pu.MoonStore.EntityFrameworkCore\\EntityFrameworkCore\\IMoonStoreDbContext.cs",
  "DbContextModelCreatingExtensionsFilePath": "E:\\_dev\\shop\\Pu.MoonStore\\src\\Pu.MoonStore.EntityFrameworkCore\\EntityFrameworkCore\\MoonStoreDbContextModelCreatingExtensions.cs",
  "HttpApiHostProjectDirectory": null,
  "HttpApiProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\src\\Pu.MoonStore.HttpApi",
  "BlazorProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\src\\Pu.MoonStore.Blazor",
  "StartupProjectDirectory": "E:\\_dev\\shop\\Pu.MoonStore\\src\\Pu.MoonStore.Web",
  "StartupProjectName": "Pu.MoonStore.Blazor",
  "DatabaseProvider": 1,
  "DatabaseProviderName": "EntityFrameworkCore",
  "UiFrameworkName": "Angular",
  "ApplicationContractsExists": true,
  "MigratorProjectExists": false,
  "UpdateDatabaseMethod": 1,
  "IsTieredArchitecture": false,
  "ActiveDate": "2021-08-11T12:17:48.3212256-05:00",
  "ProjectTemplateType": 2,
  "AbpVersion": "4.4.0"
},

ABP Framework version: v4.4.0 UI type: Angular DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): yes Exception message and stack trace: Steps to reproduce the issue:"

Two bugs: ---> suite to create module template

1, The bool property in the UI(Angular), if not select the bool property in UI, it could not be saved, see below image

2, The import path is error in UI, see below image import { ProductService } from '../../../proxy/controllers/products/product.service';

============================================================ Please check this link: https://support.abp.io/QA/Questions/1181/Extend-tenant-property-failed-for-enum-property

4.2 version already has this error:

The angular ui seems check bool as integer. (New Buttton only) (Edit works) I created root entity with the bool property. But the UI "new button" will check bool validation(int).

image.png image.png

================================ ABP Framework version: v4.3.2 UI type: Angular DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): yes Exception message and stack trace: Steps to reproduce the issue:

Hi Maliming,

Yes, works now.

It seems the default migration files no these tables:

Execude one more time "add-migration" after suite create module template, in Identityserver.host it will create these pay related tables.

thx

ABP Framework version: v4.4.0 UI type: Angular DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): yes Exception message and stack trace: Steps to reproduce the issue:"

1. create new module template
2. angular ui and api all run
3. login from angular ui
4. the identitymanagement is ok for any menu
5. when click the "Editions" it show the error
6. and tenant "new" also show this error

I did not add any other modules. It just create from abp suite, and run.

The Edition "New" works, I could see the data from database. But edition getlist not work.

Hi Mehmet,

Thanks, Yes, it works now for NG Zorro.

Another question: How about the angular UI metronic component? (like abpzero ui)

Can we use metronic directly like ng zorro in our Angular UI product?

thx

Ng Zorro has tree view and tree select. https://ng.ant.design/components/tree-select/en

But I am not sure it could be used directly into Abp Angular UI created by suite or not?

Thanks.

I will consider your advice.

• ABP Framework version: v4.3.3
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• Steps to reproduce the issue:"

I need to use "Cascader" and "multiple select" component in our product, angular UI. I want to use Cascader and select of NG-ZORRO. I try to add them into pages (create by suite), it does not work.

1, I try to add them directly into pages create by suite, it does not work. 2, So I try to only use NG-ZORRO component into blank page, it still not work.

More Questions 1, How about PrimeNG Component, Can we use PrimeNG Component into pages created by suite directly? 2, Do you have any other solutions for "Cascader" and "multiple select" component in Angular UI?

Thanks,

I follow your method to test it. 1, add builder.ConfigureCategoryCenter in the ProductCenterDbContext 2, add-migration --> create new migration file 3, remove these category tables from this migration file (these tablse are already in db) 4, update-database --> it works

Another question: It is about the "AutoMapperProfile". Can we use category automapperprofile directly in the productcetner module?

Now I want to use CategoryCenterApplicationAutoMapperProfile in productcenter module. I have to copy the info of CategoryCenterApplicationAutoMapperProfile into productcenter module.

Without copy, it dose not work.

Thx

Thanks for your reply. Yes, we use one database. We already have tried it. It will not create that issue, but we dev module one by one. The categorycenter already finished and create tables in db. So, if we call builder.ConfigureCategoryCenter, it will create category tables one more time. and update-database will not pass for the tables already in db.

1, if we use your method, to call builder.ConfigureCategoryCenter in productcernterdbcontext, do we need to delete the duplicate tables from Migration file? Is this common method to deal with this Scenario?

2, I used suite to create navigation property. I konw xxxWithNavigationProperties class was used as the bridge class of relationship of 1:M. So for M:M relastionship, is it possible we could use like xxxWithNavigationProperties class to make M:M bridge?

3, Could you give me some ideas or examples for the M:M in microservices. You know, M:M is very common in Microservice, like shippmentcenter with ordercenter. order also is M:M with shippment. and Order with payment some Scenario also need M:M.

Thanks,