Automapper will remove static API.

[maliming]

It'll break some folks, but I'm tired of supporting an API that no one should use anymore.

• Version 8.1.1 - Obsolete Mapper.Initialize Obsolete Mapper.Initialize LuckyPennySoftware/AutoMapper#3082
• Version 9.0 - Removing static API Removing static API LuckyPennySoftware/AutoMapper#3136

see: LuckyPennySoftware/AutoMapper#3135

[hikalkan]

I am happy for it, but this is a big breaking change for us since .MapTo extension methods are using it.
However, we can emulate it (by defining a static mapper instance) and mark these methods as obsolete.

We will work on this once AutoMapper releases 9.0.

[sebitsi]

@hikalkan What about ProjectTo ?

Should we start using/replacing static extensions

srcInstance.ProjectTo<DestType>()

with

IMapper.ProjectTo<DestType>(srcInstance)

or

srcInstance.ProjectTo<DestType>(config)
?

[maliming]

About ProjectTo<> please refer to
https://github.com/AutoMapper/AutoMapper.Extensions.Microsoft.DependencyInjection#projectto-usage

[iyhammad]

@hikalkan So what's the correct integration way with Abp.AutoMapper now ? Is it safe to use IObjectMapper ? and what about the list mapping ?

[hikalkan]

Using IObjectMapper was always safe and the suggested way. It also supports the list mapping. Actually it is a wrapper to automapper and supports everything it supports.

[andmattia]

Hi

so can you explain with example how change we must made to refact the code from myEntity.MapTo() wtih new AutoMapper?

[maliming]

@andmattia
Instead of using static MapTo extension methods, you should use the IObjectMapper provided by abp to map objects.

Static methods can't use dependency injection and are also unfriendly to unit tests.

[andmattia]

I try to inject via private readonly IObjectMapper but ABP say that is not registered

[maliming]

Please share your code.

In addition, ObjectMapper has been injected by default in multiple base class services.
For example,

aspnetboilerplate/src/Abp.AspNetCore/AspNetCore/Mvc/Controllers/AbpController.cs

Line 62 in e0ded5d

public IObjectMapper ObjectMapper { get; set; }

[easyfast]

在AppServiceBase里这么做：
`
public TenantManager TenantManager { get; set; }

    public UserManager UserManager { get; set; }

    protected IConfigurationProvider AutoMapperConfigurationProvider { get; set; }

    protected EasyFastAppServiceBase()
    {
        LocalizationSourceName = EasyFastConsts.LocalizationSourceName;
        var mapper = IocManager.Instance.Resolve<IMapper>();
        AutoMapperConfigurationProvider = mapper.ConfigurationProvider;
    }

`

实际代码中这么做：

`
public async Task<PagedResultDto> GetPagedList(GetPagedListInput input)
{
var query= _userTypeRepository.GetAll();
var total = await query.CountAsync();
var items = await query
.Skip((input.PageIndex - 1) * input.PageSize).Take(input.PageSize)
.ProjectTo(AutoMapperConfigurationProvider).ToListAsync();
return new PagedResultDto { TotalCount = total, Items = items };

    }

`

测试时会报错：

EasyFast.Tests.UserType.UserTypeAppService_Tests.CreateOrUpdate_ShouldBeOk_Test
源: UserTypeAppService_Tests.cs 行: 35
持续时间: 1 ms

消息:
Castle.MicroKernel.ComponentActivator.ComponentActivatorException : ComponentActivator: could not proxy EasyFast.Application.UserType.UserTypeAppService
---- System.Reflection.TargetInvocationException : Exception has been thrown by the target of an invocation.
-------- Castle.MicroKernel.ComponentNotFoundException : No component for supporting the service AutoMapper.IMapper was found
堆栈跟踪:
在 DefaultComponentActivator.CreateInstance(CreationContext context, ConstructorCandidate constructor, Object[] arguments)
在 DefaultComponentActivator.InternalCreate(CreationContext context)
在 AbstractComponentActivator.Create(CreationContext context, Burden burden)
在 AbstractLifestyleManager.CreateInstance(CreationContext context, Boolean trackedExternally)
在 AbstractLifestyleManager.Resolve(CreationContext context, IReleasePolicy releasePolicy)
在 DefaultHandler.ResolveCore(CreationContext context, Boolean requiresDecommission, Boolean instanceRequired, Burden& burden)
在 DefaultHandler.Resolve(CreationContext context, Boolean instanceRequired)
在 DefaultKernel.ResolveComponent(IHandler handler, Type service, Arguments additionalArguments, IReleasePolicy policy, Boolean ignoreParentContext)
在 IKernelInternal.Resolve(Type service, Arguments arguments, IReleasePolicy policy, Boolean ignoreParentContext)
在 DefaultKernel.Resolve(Type service, Arguments arguments)
在 WindsorContainer.ResolveT
在 UserTypeAppService_Tests.ctor() 在 UserTypeAppService_Tests.cs 行: 19
在 ----- Inner Stack Trace -----
在 RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)
在 RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
在 RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
在 ProxyGenerator.CreateClassProxyInstance(Type proxyType, List1 proxyArguments, Type classToProxy, Object[] constructorArguments) 在 DefaultProxyFactory.Create(IKernel kernel, Object target, ComponentModel model, CreationContext context, Object[] constructorArguments) 在 DefaultComponentActivator.CreateInstance(CreationContext context, ConstructorCandidate constructor, Object[] arguments) 在 ----- Inner Stack Trace ----- 在 IKernelInternal.Resolve(Type service, Arguments arguments, IReleasePolicy policy, Boolean ignoreParentContext) 在 DefaultKernel.Resolve(Type service, Arguments arguments) 在 WindsorContainer.Resolve[T]() 在 EasyFastAppServiceBase.ctor() 在 EasyFastAppServiceBase.cs 行: 30 在 UserTypeAppService.ctor(IRepository2 userTypeRepository) 在 UserTypeAppService.cs 行: 19

除了在具体的service中用构造器注入以外。 最佳的做法是什么？