related badly formed path issue for linux I think:

https://support.abp.io/QA/Questions/2209/Bugs--Issues-v5X#answer-9ad254be-2d53-a4ca-0fe9-3a0191e0d611

I update the solution to use Volo.Abp.Identity.Pro.Application 5.0.1 and it now compiles, except for a missing method used by one of the tests: AbpApplicationFactory.CreateAsync

However, I experience the same issue building a docker image with this patch version as I did with version 5.1.2: https://support.abp.io/QA/Questions/2459/Docker-build-failure

Thank you for the tip.

I updated the CLI and SUITE to 5.0.2 and I am unable to build my solution, due to missing framework packages.

C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core>dotnet restore Determining projects to restore... Restored C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\src\Acs.Cts.Portal.DbMigrator\Acs.Cts.Portal.DbMigrator.csproj (in 13.75 sec). Restored C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\src\Acs.Cts.Portal.Web.Public\Acs.Cts.Portal.Web.Public.csproj (in 17.79 sec). C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\src\Acs.Cts.Portal.Application\Acs.Cts.Portal.Application.csproj : warning NU1603: Acs.Cts.Portal.Application depends on Volo.Abp.Account.Pro.Admin.Application (>= 5.0.2) but Volo.Abp.Account.Pro.Admin.Application 5.0.2 was not found. An approximate best match of Volo.Abp.Account.Pro.Admin.Application 5.1.1 was resolved. [C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\Acs.Cts.Portal.sln] C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\src\Acs.Cts.Portal.Application\Acs.Cts.Portal.Application.csproj : error NU1605: Detected package downgrade: Volo.Abp.Identity.Pro.Application from 5.1.1 to 5.0.2. Reference the package directly from the project to select a different version. [C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\Acs.Cts.Portal.sln] C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\src\Acs.Cts.Portal.Application\Acs.Cts.Portal.Application.csproj : error NU1605: Acs.Cts.Portal.Application -> Volo.Abp.Account.Pro.Admin.Application 5.1.1 -> Volo.Abp.Account.Pro.Shared.Application 5.1.1 -> Volo.Abp.Identity.Pro.Application (>= 5.1.1) [C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\Acs.Cts.Portal.sln] C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\src\Acs.Cts.Portal.Application\Acs.Cts.Portal.Application.csproj : error NU1605: Acs.Cts.Portal.Application -> Volo.Abp.Identity.Pro.Application (>= 5.0.2) [C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\Acs.Cts.Portal.sln] Failed to restore C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\src\Acs.Cts.Portal.Application\Acs.Cts.Portal.Application.csproj (in 19.01 sec). C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\test\Acs.Cts.Portal.Application.Tests\Acs.Cts.Portal.Application.Tests.csproj : warning NU1603: Acs.Cts.Portal.Application depends on Volo.Abp.Account.Pro.Admin.Application (>= 5.0.2) but Volo.Abp.Account.Pro.Admin.Application 5.0.2 was not found. An approximate best match of Volo.Abp.Account.Pro.Admin.Application 5.1.1 was resolved. [C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\Acs.Cts.Portal.sln] C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\test\Acs.Cts.Portal.Application.Tests\Acs.Cts.Portal.Application.Tests.csproj : error NU1605: Detected package downgrade: Volo.Abp.Identity.Pro.Application from 5.1.1 to 5.0.2. Reference the package directly from the project to select a different version. [C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\Acs.Cts.Portal.sln] C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\test\Acs.Cts.Portal.Application.Tests\Acs.Cts.Portal.Application.Tests.csproj : error NU1605: Acs.Cts.Portal.Application.Tests -> Acs.Cts.Portal.Application -> Volo.Abp.Account.Pro.Admin.Application 5.1.1 -> Volo.Abp.Account.Pro.Shared.Application 5.1.1 -> Volo.Abp.Identity.Pro.Application (>= 5.1.1) [C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\Acs.Cts.Portal.sln] C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\test\Acs.Cts.Portal.Application.Tests\Acs.Cts.Portal.Application.Tests.csproj : error NU1605: Acs.Cts.Portal.Application.Tests -> Acs.Cts.Portal.Application -> Volo.Abp.Identity.Pro.Application (>= 5.0.2) [C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\Acs.Cts.Portal.sln] Failed to restore C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\test\Acs.Cts.Portal.Application.Tests\Acs.Cts.Portal.Application.Tests.csproj (in 25.11 sec). C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\src\Acs.Cts.Portal.HttpApi.Host\Acs.Cts.Portal.HttpApi.Host.csproj : warning NU1603: Acs.Cts.Portal.Application depends on Volo.Abp.Account.Pro.Admin.Application (>= 5.0.2) but Volo.Abp.Account.Pro.Admin.Application 5.0.2 was not found. An approximate best match of Volo.Abp.Account.Pro.Admin.Application 5.1.1 was resolved. [C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\Acs.Cts.Portal.sln] C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\src\Acs.Cts.Portal.HttpApi.Host\Acs.Cts.Portal.HttpApi.Host.csproj : error NU1605: Detected package downgrade: Volo.Abp.Identity.Pro.Application from 5.1.1 to 5.0.2. Reference the package directly from the project to select a different version. [C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\Acs.Cts.Portal.sln] C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\src\Acs.Cts.Portal.HttpApi.Host\Acs.Cts.Portal.HttpApi.Host.csproj : error NU1605: Acs.Cts.Portal.HttpApi.Host -> Acs.Cts.Portal.Application -> Volo.Abp.Account.Pro.Admin.Application 5.1.1 -> Volo.Abp.Account.Pro.Shared.Application 5.1.1 -> Volo.Abp.Identity.Pro.Application (>= 5.1.1) [C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\Acs.Cts.Portal.sln] C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\src\Acs.Cts.Portal.HttpApi.Host\Acs.Cts.Portal.HttpApi.Host.csproj : error NU1605: Acs.Cts.Portal.HttpApi.Host -> Acs.Cts.Portal.Application -> Volo.Abp.Identity.Pro.Application (>= 5.0.2) [C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\Acs.Cts.Portal.sln] Failed to restore C:\Users\Jamie\Source\Repos\CTS_Portal2\apps\acs-portal\aspnet-core\src\Acs.Cts.Portal.HttpApi.Host\Acs.Cts.Portal.HttpApi.Host.csproj (in 28.23 sec). 12 of 17 projects are up-to-date for restore.

I manually updated the project references from 5.0.0 to 5.0.2, as it appears that the abp update command updates to the latest version, rather than the installed version of the cli and suite, which seems counterintuitive.

Is there a command that can update to a specified version?

Thanks

I was able to create a version 5.0.0 project using the CLI:

abp new MyApp -t app-pro --version 5.0.0 --ui mvc --tiered

Is ABP Suite working as intended or is this a bug?

Thanks

Thanks.

That fixed the problem, but is this a bug and should the script contributor be automatically configured by way of my Web module having a dependency on the ChatWebModule?

Or, is this the typical approach for making the module scripts available in the Web projects?

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:

thank you

@Rrader30

Appreciate for info, was hoping to utilize out of the box too but will have to craft my own as well.

Marketplace for modules would be nice!

Thanks

@Rrader30, we need to do something similar.

I think the File Management module is an incomplete feature without the ability to manage permissions to folders, or at least utilize in a way that provides a root folder as an entry point to the UI, so that the user is restricted to only that folder and its subfolders.

There's an open issue for Resource based authorization integration: https://github.com/abpframework/abp/issues/236

Have you found workable a solution yet that you can share?

Thanks Jamie

Adding a new multi-tenanted entity through ABP Suite has AutoMapperConfigurationException

ABP Framework version: v4.3.0 ( module template) UI type: MVC DB provider: EF Core Identity Server Separated: no

When starting the Unified App from a Module template, after generating a multi-tenanted entity, adding migration and updating SQL database, the application has exception on startup:

An unhandled exception occurred while processing the request.

AutoMapperConfigurationException: Unmapped members were found. Review the types and members below. Add a custom mapping expression, ignore, add a custom resolver, or modify the source/destination type For no matching constructor, add a no-arg ctor, add optional arguments, or map all of the constructor parameters

ResourceClassTypeCreateDto -> ResourceClassType (Destination member list) Acs.ResourceLibrary.ResourceClassTypes.ResourceClassTypeCreateDto -> Acs.ResourceLibrary.ResourceClassTypes.ResourceClassType (Destination member list)

Unmapped properties:

TenantId

ResourceClassTypeUpdateDto -> ResourceClassType (Destination member list) Acs.ResourceLibrary.ResourceClassTypes.ResourceClassTypeUpdateDto -> Acs.ResourceLibrary.ResourceClassTypes.ResourceClassType (Destination member list)

Unmapped properties: TenantId AutoMapper.ConfigurationValidator.AssertConfigurationIsValid(IEnumerable typeMaps)

<br> DependencyResolutionException: An exception was thrown while activating λ:Microsoft.AspNetCore.Identity.ISecurityStampValidator -> Castle.Proxies.AbpSecurityStampValidatorProxy -> Volo.Abp.MultiTenancy.TenantConfigurationProvider -> Volo.Saas.Tenants.TenantStore -> Volo.Abp.ObjectMapping.DefaultObjectMapper1[[Volo.Saas.SaasDomainModule, Volo.Saas.Domain, Version=4.3.0.0, Culture=neutral, PublicKeyToken=null]] -> Volo.Abp.AutoMapper.AutoMapperAutoObjectMappingProvider1[[Volo.Saas.SaasDomainModule, Volo.Saas.Domain, Version=4.3.0.0, Culture=neutral, PublicKeyToken=null]] -> λ:Volo.Abp.AutoMapper.IMapperAccessor -> λ:Volo.Abp.AutoMapper.MapperAccessor. Autofac.Core.Resolving.Middleware.ActivatorErrorHandlingMiddleware.Execute(ResolveRequestContext context, Action next)

<br> Was able to resolve the issue by adding .Ignore(x => x.TenantId) extension on the CreateMap in the src/Project.Application ProjectAutoMapperProfile class:

Is that the correct approach?