Activities of "alper"

it returns 10 records as default. but you should be writing into the typeahead component. do you get any console errors. and what's your suite version?

let's keep it open until it gets solved

we couldn't reproduce the Angular code generation problem.

There's no ABP module for ticket management. This website is also implemented with the ABP Commercial platform. But it's not for sale!

hi 5.2.0 is preview version. we have removed 5.2.0 from stable releases. so close all Visual Studios, remove your ABP Suite v5.2.0 and clear your nuget cache...

1. removing abp suite : abp suite remove
2. clear nuget cache: dotnet nuget locals all --clear
3. install abp suite : abp suite install

this case is not directly related to ABP Framework. ABP Framework uses Entity Framework Core as the database provider. Do you get the same problem with a vanilla .NET console application?

for now, you can generate with Suite and make the necessary modifications. On the other hand, I created an issue to support these modules for the new versions. (issue: 9022)

this is different that's mentioned in https://support.abp.io/QA/Questions/17 .we already support module templates. but Administration, Identity and Saas modules are not identical to the ABP new module template that's why ABP Suite cannot properly generate on these modules.

I Created a new project (Abp : 5.1.1) (angular) (not separated identity ) (SQL Server) And added a new module (abp add-module CustomModule --new --add-to-solution-file) Then when I added a simple AppService and related Controller,
When I run the project I get this error:

Autofac.Core.DependencyResolutionException: 'An exception was thrown while activating Volo.Abp.IdentityServer.Grants.PersistedGrantStore -> Volo.Abp.ObjectMapping.DefaultObjectMapper1[[Volo.Abp.IdentityServer.AbpIdentityServerDomainModule, Volo.Abp.IdentityServer.Domain, Version=5.1.1.0, Culture=neutral, PublicKeyToken=null]] -> Volo.Abp.AutoMapper.AutoMapperAutoObjectMappingProvider1[[Volo.Abp.IdentityServer.AbpIdentityServerDomainModule, Volo.Abp.IdentityServer.Domain, Version=5.1.1.0, Culture=neutral, PublicKeyToken=null]] -> λ:Volo.Abp.AutoMapper.IMapperAccessor -> λ:Volo.Abp.AutoMapper.MapperAccessor.'

5.1.1 had a problem adding a module. upgrade to 5.1.2...

@aldercove

ABP Version 5.1.1

• MVC with public website and tiered identity server
• EF Core
• Steps needed to reproduce the problem:

1. Create a new MVC solution with abp suite
2. Run migrations
3. Run the app

The profile picture does not seem to be working properly. It shows properly on the account page, but not in the web or public web applications. Doesn't make a difference if changing to Avatar/Gravatar or uploaded file, still shows:

Error in the browser on get of the picture:

With an Id that corresponds with the Admin user Id:

created an internal issue to repro and fix. moved to https://support.abp.io/QA/Questions/2444/Issues-with-Adding-New-Custom-Module-to-New-Project-5XX-Issue (issue: 8961)