Activities of "LinchArnold"

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

hi, any updates?

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

I tried to reproduce it with the latest but couldn't reproduce. We specifically need these
1- your entity.json
2- the following information:

• ABP Framework version:
• UI type: Angular / MVC / Blazor
• DB provider: EF Core / MongoDB
• Tiered (MVC) or Identity Server Separated (Angular):
• Steps to reproduce the issue:

Hi, I am preparing a new Module project and try to reproduce it and share the project to github. But @yekalkan has reproduced the problem.

Hi again @LinchArnold,

Now I reproduced the issue, fixed it internally and added it to next patch release.

For now, i can provide you a simple but dirty workaround if this is urgent for you:

1. Change the name of DbContext interface file (I{Your_Project_Name}DbContext.cs) in your project to something else (example: Random_Name.cs).
2. Generate your entity via suite.
3. Revert the file name.
4. Manually add the new entity to DbContext interface file. (Line to add: DbSet<{Your_Enttiy's_Name}> {Your_Entity's_Name_Plural} { get; set; })

Be sure to rename both MongoDb & EfCore DbContext interfaces before entity generation, but do not take any action for DbContext classes.

Hi, thanks for your reply, I'll take the steps you provide to avoid the exceptions. Best regards.

Hi, is any support here? has someone try to generate page in Module project came across same exception?

Error details:

Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'startIndex')
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'startIndex')
   at System.Globalization.CompareInfo.IndexOf(String source, String value, Int32 startIndex, Int32 count, CompareOptions options)
   at System.String.IndexOf(String value, Int32 startIndex, Int32 count, StringComparison comparisonType)
   at System.String.IndexOf(String value, Int32 startIndex, StringComparison comparisonType)
   at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.EntityGenerateCommand.CvMwA8dFmX(String  , String  , String  )
   at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.EntityGenerateCommand.da8wKZL4Py(String  , String  , Boolean  )
   at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.EntityGenerateCommand.dsxw7tsdx3(String  , String  , Boolean  , DatabaseProvider  )
   at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.EntityGenerateCommand.LM8wSX1JwZ(String  , DatabaseProvider  )
   at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.EntityGenerateCommand.wxHwpn1kEW()
   at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.EntityGenerateCommand.ExecuteAsync(CrudPageCommandOptions options)
   at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.CommandManager.ExecuteAllAsync(CrudPageCommandOptions options)
   at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.CrudPageGenerator.GenerateAsync(EntityModel entity, Solution solution)
   at Volo.Abp.Suite.Controllers.CrudPageGeneratorController.SaveAndGenerateEntityAsync(Guid solutionId, EntityModel entity)
   at lambda_method2227(Closure , Object )
   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.&lt;InvokeNextActionFilterAsync&gt;g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.&lt;InvokeInnerFilterAsync&gt;g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.&lt;InvokeNextExceptionFilterAsync&gt;g__Awaited|26_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)