Activities of "LinchArnold"

Hi, support team, it has been 5 days, any information?

If you're creating a bug/problem report, please include followings:

• ABP Framework version: v6.0.0
• UI type: Angular
• DB provider: Not Related
• Tiered (MVC) or Identity Server Separated (Angular): ABP Module Template
• Exception message and stack trace:
• Steps to reproduce the issue:"

Hi. ABP teams: I have a problem with the command abp generate-proxy -t ng after upgrade to abp 6.0. Before version 6.0, for instance I create a module template that is AbpModule5, I use abp generate-proxy -t ng -m abpModule5 -a AbpModule5 --target AbpModule5 to generate proxies for angular library: AbpModule5. It worked as expect.

But for version 6.0, for instance I create a module template that is AbpModule6, I use abp generate-proxy -t ng -m abpModule6 -a AbpModule6 --target AbpModule6 to generate proxies for angular library: AbpModule6.

It Prompts: Please enter target Angular project to place the generated code. (default: workspace "defaultProject"), so I input the abpModule6,

After that, it shows [Proxy Config Not Found] There is no JSON file at "projects/abp-module6/abpModule6/src/proxy/generate-proxy.json". (The actual path for generate-proxy.json is projects/abp-module6/src/lib/proxy/generate-proxy.json)

So I cannot generate proxies for angular library properly in ABP 6.0.

As the suite tool generate Angular Library in projects/project-name/src/lib/, no matter what target project for The Please enter target Angular project to place the generated code. (default: workspace "defaultProject"), the Proxy Config projects/abp-module6/{target project}/src/proxy/generate-proxy.json will never found.

By the way, if I use the CLI abp generate-proxy -t ng for angular library by mistakes, would you provide a correct way for use this command.

our test team tested this issue and couldn't reproduce it. they just send feedback that it takes a long time to generate the UI otherwise it works. make sure your ABP Suite and your ABP project are the same version. Also, test it with the new 5.3.0 project to understand it works with the brand new template.

Thanks, I tried again, really wired, it worked, the exception's gone.

thanks we are checking the issue and let you know once we finish

hi, any updates?

After upgrade suite to 5.3.0, it cannot generate angular page in module project. It gives follow exceptions

[INF] Angular Schematics command failed.
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module '---------angular\.suite\schematics\run-schematics.mjs'
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

If you're creating a bug/problem report, please include followings:

• ABP Framework version: v5.3.0
• UI type: Angular
• DB provider: Not related
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• Steps to reproduce the issue:"

Hi @LinchArnold

We've investigated and verified the issue. In the module-pro template, sample/test projects are not the real applications, they're just for testing your custom module. If your module is dependent on the account module or you develop something related to the account module, you have to add the account module reference to your project. By doing it, you'll see the account permissions and that setting tab in your application.

If your module doesn't depend on the account module but you still want to see the account in that test project, you can apply the following steps:

1. Add Volo.Abp.Account.Pro.Admin.Application.Contracts to the IdentityServer project.
2. Add dependson attribute in IdentityServer module file.

   typeof(AbpAccountAdminApplicationContractsModule) 
   

3. Clear Redis keys (If it runs on docker, you can remove the volume and re-run again)
4. Re-run application. (Make sure IdentityServer is built after adding reference.)

Then you can see account permissions and the account tab on the settings page.

Hi, @enisn: Thanks for your reply. yes, my module depends on the account-pro module. When I start to develop my module on old version, in 5.1.1, I remeber the account tabs is show up there, and when I upgrade abp to 5.2.0, it's gone. but now I am not sure if I was wrong memory. Anyway, your detailed reply solved this.

Thanks so much.

We have tried this issue with Angular like following step and no problem was found.

For Angular Version 5.1.3 and Angular Version 5.2.0;

1. Create your project by choosing which version to use with the command below.

For v5.1.3 :

• abp new ProjectName -u angular --separate-identity-server -t app-pro --version 5.1.3

For v5.2.0 :

• abp new ProjectName -u angular --separate-identity-server -t app-pro --version 5.2.0

2. Run following command on ProjectName.DbMigrator folder at Terminal.

• dotnet run

3. Run following commads on ProjectName.IdentityServer folder at Terminal.

• abp install-libs
• dotnet run

4. Run following commads on ProjectName.HttpApi.Host folder at Terminal.

• dotnet run

5. Run following commad on angular folder at Terminal.

• yarn start

When we check Account module is served under IdentityServer in Angular Version 5.1.3 and Angular Version 5.2.0.

Angular Version 5.1.3 Settings : Permission : Angular Version 5.2.0 Settings : Permission :

I had tried the project template, it does not have this problem. It's the module template has this problem. I had described it in my post: 1.

2.

As the commands you provide is the -t app-pro, it should be the project template, not the module template, would you give a try for module template?

In separate IdentityServer solutions, the Account module is served under IdentityServer. Nevertheless, the permissions should be available in the angular application.

I will create an internal issue about this problem.

Thank you, I have refunded your credit.

Thank you.

This is not just happen in new module template of 5.2.0, when I upgrade my module from 5.1.3 to 5.2.0, the account tabs is also disappear.

Is it separate identity server or not?

The module template is seperate identity server