Hi @ismcagdas
ok thaks for your answer. So we can plan to move in first step to AspNetZero Core using AngularJS and in second step we can plan to move AngularJS to Angurlar
Hi,
about Q1 this but can be use to move from ZERO .Net to ZERO .NetCore obvisuly with some difference because in this way we can move in to step:
Q1: from .NET Framework to .NET Core Q2: so at the moment the only way is move to ZERO Core. But the modularity of ABP.IO is very good option...
Hi @ismcagdas
Thanks for the clarification, so we will receive it when you will release it.
Regards
Hi @ismcagdas
all information is enough to solve my issue so I close the ticket.
thank for you support
Hi @ismcagdas
is not my problem. The issue is related to OraganizationUnit is defined on base class of AbpZeroCommonDbContext and I cann't override on second DbContext, for that reason when I use OrganizationUnit Entity on Linq the Linq engine say that already exist an object mappet to dbtable. This problem not happen for user because I can create a TUser (user1 and user2) without issue.
So if we move to virtual OraganizationUnit I can override it on derived class and prevent this.
Is it correct?
I found another issue releted to this topic AutoMapper and CustomDto
We found a solution but I'm not sure is the correct way. Add this line off code at the end of first CustomDtoMapper. We add only at the first becasue if you use it on more module Automapper give an exception that say "Mapper already initialize"
// Add for AutoMap 8.x
Mapper.Initialize((MapperConfigurationExpression) mapper);
No unfortunatly no.
At the moment all Call made via AutoMapper.Map(input,Output) give the same error
Ok
So you confirm that starting from now I need to disable the module into web.confing and it's not necessay any more?