Hi,

Suite finds the location of the code class via RegEx expressions. And some of them are precisely fine-tuned to inject the code to the right place. If I see your DbContext.cs file I can understand the reason.

@Nicolas my bad! it will come with v4.4

What would you do if you have a plain ASP.NET Core application?

4.3 file management module.

file upload api works on local host after deploying to server it won't work. redirects to home page. all other apis works well.

on the UI I can upload files well

have you tested this ?

there must be 2 identical enum value. you can remove the enum property and add again. or you can edit the entity.json file which is located in your .suite\entities folder.

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?

@AlderCove that's right.

I created a new entity with the latest Suite (4.3.1 not published yet) and it also ignores TenantId

I have an error with abp 4.3.0 and the Tiered MVC Version I think we got that error before, but could not find a issue here at that page.

Steps to reproduce:

1. Generate a new MVC/EF Version with Tiered Option enabled
2. Generate a Item a property with Abp Suite
3. Start Web Application and access that Item Page

You receive that error:

(Also an bug or feature : The AddItem Menu Entry in MenuContributor is in a different place at ConfigureUserMenuAsync instead ConfigureMainMenuAsync)

I did check the index.js from that Item. There seams to be an error at the controller at line 3:

var inventoryItemService = window.tierTest.controllers.inventoryItems.inventoryItems;

instead of :
var inventoryItemService = window.tierTest.controllers.inventoryItems.inventoryItem;

I couldn't fix, because it seams that are more errors somewhere..

It works well if i generate a new ap without the Tired Option.

Do you got an workaround ?

@hakan while we fix this issue there's a workaround. open the templates page in Suite. and find index.js.txt make the following change entity-name-plural-camelcase => entity-name-camelcase

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

Problem : wrong generate localization

@arifharsono that issue will be fixed in 4.3.1

I've upgraded our solution from ABP 3.3.2 to 4.3.0.

Everything was more or less smoothly, but now I discovered a problem: some new ABP tables are missing from migration scripts! How come? What am I supposed to do now?

Please have a look at the migration classes autogenerated for 3.3.2 and 4.3.0. https://1drv.ms/u/s!AhWdpZddvifTtizt4xjre044i7B8?e=0xuBUs

Here is the list of ABP-prefixed tables created from test solution (autogenerated in ABP Suite) using DbMigrator project in local MS SQL server DB - all the tables are at place:

Here is the list of tables in our ORACLE DB created using standard update-database command and DbMigrator afterwards to seed data - make a note some tables are missing (for instance, AbpBlobContainers, AbpTextTemplateContents). How it's possible?? How to easily find out what is missing and add it?

@Alexander there are missing tables because you might not have these modules: AbpBlobContainers, AbpTextTemplateContents If you create a new project these modules come by default that's why you see the difference in migration. You need to add these modules manually (if you require them)

ABP Framework version: v4.3.0
UI type: Angular
DB provider: EF Core
Tiered (MVC) or Identity Server Separated (Angular): Yes
Steps to reproduce the issue:
I just get source from ABP suite and build. It has this error

@edelivery couldn't understand what you get? is that a module?

Hi alper
I just created new solution from abp suite
Template type: application template

so I understand this; you create a new Angular + EF Core + Separated Identity Server proejct.
And it throws exception out of the box. Right?

yes, that's right

I created a new 4.3.0 project with the following CLI command

abp new Angular.EfCoreSeperate05113159 -t app-pro -u angular -m none --separate-identity-server --database-provider ef -csf 

Migrated db with DBMigrator. Run IdentityServer project first, then HttpApi.Host project then, Angular ...

And I don't see any console errors:

Ensure that you are running the latest ABP CLI

Nicolas each module has its own translation. in your case some of the module translations are missing. Can you create a new latest project to see if it's the same in a new project?