Activities of "dkaczor"

• ABP Framework version: v4.4.0
• UI type: Angular
• DB provider: EF Core

I created an EF Core + Angular application. Then, I added custom module using command abp add-module MyOwnModule --new --add-to-solution-file. It created backend projects in aspnet-core/modules folder and angular project in angular/projects folder. I followed this article and added lazy loading of this new module in my main app-routing.module.ts:

    {
        path: 'my-own-module',
        loadChildren: () =>
            import('MyOwnModule/projects/my-own-module').then(m => m.MyOwnModuleModule.forLazy()),
    },

Then, Imported the ConfigModule in my app.module.ts

    MyOwnModuleConfigModule.forRoot(),

At last, I added route in my route.provider.ts

      {
        path: '/my-own-module',
        name: 'My Own Module'
      }

Now the problem is that when I navigate to /my-new-module path, no component is loaded, the menu and header stay but there is no content. I also can't see any error in console. Did I miss any part of configuration or is there a bug in generated code?

• ABP Framework version: v4.4.0-rc2
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): Microservice architecture

I created a microservice template solution via ABP Suite, then I added a microservice based on this guide. In this new microservice I have an app service and I wanted the controllers to be generated automatically, so I followed this guide. The controllers are visible in swagger UI in my new microservice direct address only, they are not available in any of the gateways. If I create controllers manually, everything works fine. Do I have to take any additional steps to make the auto controllers visible or do gateways utilise only manually created controllers?