Migration Help AutoMapper transition #12652

20 Answer(s)

• 

  0

  oguzhanagir created 4 months ago

  Support Team

  Hi @ayoyusuf

  We have documentation available for the transition from AutoMapper to Mapperly; you can review it. Please feel free to contact us if you need any assistance.

  If you specify a more particular part for the transition, we would be happy to assist you. You can share the CustomMapper details if you wish, or contact us regarding a specific issue. If you prefer not to share the CustomMapper details here, you can send an email to [email protected].

  We can continue the Mapperly transition process through this ticket.

  Thank you

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  ayoyusuf created 4 months ago

  Typically upgrades have come with minimal issues in the history of ASP.NET Zero. Mapperly choice is a major breaking change. It is breaking too many old codes.

  Most importantly, it is not doing well with nested objects requiring very long winding codes to get basic nested objects done. This is defeating the purpose of having object Mappings if we have to do such extensive codes, we can as well have custom map functions.

  The main advantage is suppose to be compile time errors? well, got it working only to get strange application behaviours which we later traced to issues of some object properties being null or empty from mapperly maps.

  Mapperly seems great for simple apps, Asp.net zero has been so great, enterprise systems and even fintechs have been built on it, a breaking change such as this is a potential major issue.

  REQUESTS: Please have a quick relook and pending that time provide an easy guide to enable back and use AutoMapper for those that want to keep using the last abp.automapper till then or till when we have time to properly figure out a transition to a workable resolution.

  N.B: We have an AI that can easily do the basic mapping, but this would still hit the brick wall of nested classes. now due to nested issues, its difficult having a prompt that then requires us to provide almost every dto so the AI can see all nested

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  oguzhanagir created 4 months ago

  Support Team

  Hi @ayoyusuf

  If you prefer not to migrate to Mapperly at this stage, you can continue using the Abp.AutoMapper package. It is still supported on our side and remains a viable option for existing projects.

  We understand your concerns regarding the transition. Mapperly introduces a compile time mapping approach, which can be beneficial in terms of performance and type safety, but it may also require more explicit configuration, especially for complex or deeply nested object graphs. This can feel like a regression compared to the more implicit conventions provided by AutoMapper.

  For projects with extensive existing mappings, particularly in enterprise scale solutions, an immediate migration may not be practical. In such cases, continuing with AutoMapper is a reasonable and supported approach until you are ready to refactor incrementally.

  Regarding your request, we can provide guidance on re enabling AutoMapper in newer versions. At a high level, this involves:

  • Installing the Abp.AutoMapper package
  • Replacing Mapperly module dependencies with AutoMapper equivalents
  • Re registering your mapping profiles using the AutoMapper integration

  If needed, we can assist you step by step based on your current version and project structure.

  We also appreciate your feedback about nested mappings and runtime inconsistencies. This kind of input is valuable and will be considered as we continue improving the developer experience.

  Thank you.

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  ayoyusuf created 4 months ago

  Yes, I will highly appreciate a step by step guide to enabling AutoMapper.

  Current Version: 14.0

  My project structure retains the default Asp.Net Zero structure as it makes upgrades easier.

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  oguzhanagir created 4 months ago

  Support Team

  Hi @ayoyusuf

  Sorry for the delay. We've reviewed your project and will share guidance on how to continue using AutoMapper as soon as possible. Thank you.

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  [email protected] created 4 months ago

  I reported the same issue.

  See if this helps. I am still trying to work through it myself.
  https://support.aspnetzero.com/QA/Questions/12647/Migration-Help-to-152

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  oguzhanagir created 4 months ago

  Support Team

  Hi @ayoyusuf

  Sorry for the delay. We've reviewed your project and conducted research on how to upgrade to the latest version with minimal changes to AutoMapper.

  Required technical change:

  <PackageReference Include="Abp.AutoMapper" Version="11.2.0" />
  

  Use this instead of Abp.Mapperly.

  In the Core module:

  using Abp.AutoMapper;
  
  #pragma warning disable CS0618
  [DependsOn(
      typeof(ArchCoreSharedModule),
      typeof(AbpZeroCoreModule),
      typeof(AbpZeroLdapModule),
      typeof(AbpAutoMapperModule),
      typeof(AbpAspNetZeroCoreModule),
      typeof(AbpMailKitModule),
      typeof(AbpZeroCoreOpenIddictModule))]
  #pragma warning restore CS0618
  public class ArchCoreModule : AbpModule
  {
  }
  

  In the Application module, the existing logic should remain as is:

  using Abp.AutoMapper;
  
  public override void PreInitialize()
  {
      Configuration.Authorization.Providers.Add<AppAuthorizationProvider>();
  
      Configuration.Modules.AbpAutoMapper()
          .Configurators.Add(CustomDtoMapper.CreateMappings);
  }
  

  Mappings should also remain inside CustomDtoMapper:

  using AutoMapper;
  
  internal static class CustomDtoMapper
  {
      public static void CreateMappings(IMapperConfigurationExpression configuration)
      {
          configuration.CreateMap<Entity, EntityDto>();
          configuration.CreateMap<CreateOrEditEntityDto, Entity>();
      }
  }
  

  Note: Abp.MapperlyModule and AbpAutoMapperModule should not be used together. Both override the IObjectMapper implementation. If the project will continue using AutoMapper, the Mapperly mapper classes introduced in the newer version should either not be merged or should be converted to their AutoMapper CreateMap equivalents. Existing ObjectMapper.Map<T>() usages will continue to work as-is.

  If there is any conflict on the mapper side, you will need to adjust the implementation to use AutoMapper instead.

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  KieranIrl created 4 months ago

  Hi team ,

  We are working on moving to ASP.NET Zero 15.3 / ABP 11.2.0 / .NET 10.

  AutoMapper 15.0.1 (resolved via Abp.AutoMapper 11.2.0) has a high-severity DoS vulnerability — CVE-2026-32933. Patched in 15.1.3 and 16.1.1.

  Can we safely pin AutoMapper to 15.1.1 or 16.1.1 in our Directory.Packages.props, or is there a planned Abp.AutoMapper update to address this?

  I get you have moved in the direction of Mapperly but the amount of work that will take is beyond the scope we have at the minute. Likewise if there is no support further planned for your wrapper is there documentation available for those of us who decide paying up for automapper is easier than migrating at this time ?

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  oguzhanagir created 3 months ago

  Support Team

  Hi @KieranIrl

  For ASP.NET Zero 15.3 / ASP.NET Boilerplate 11.2.x projects that still use Abp.AutoMapper, the safest short-term workaround is to stay on the AutoMapper 15.x line and pin AutoMapper to a patched 15.x version, preferably 15.1.3 or later.

  We do not recommend forcing AutoMapper to 16.1.1 as a simple transitive override at this point. 16.x is a major AutoMapper upgrade and may also require updating related packages such as AutoMapper.Collection. It should only be used after a full compatibility test, or after we publish/test the corresponding Abp.AutoMapper dependency update.

  So the recommended workaround is:

  <ItemGroup>
    <PackageVersion Include="AutoMapper" Version="15.1.3" />
  </ItemGroup>
  

  If your project uses Central Package Management and this does not affect the transitive dependency, either enable NuGet transitive pinning or add an explicit PackageReference to AutoMapper in the project that uses Abp.AutoMapper. Please verify the final resolved version with: dotnet list package --include-transitive

  Regarding Mapperly: yes, Mapperly is our recommended direction for new generated code and future mapping work, but we understand that migrating an existing application from AutoMapper can be a significant effort. Existing projects are not expected to migrate immediately just to handle this CVE.

  If you continue using AutoMapper 15+, please also note that AutoMapper now requires a license key. Since Abp.AutoMapper configures AutoMapper through ABP module configuration rather than services.AddAutoMapper, you can pass the license key like this:

  public override void PreInitialize()
  {
      Configuration.Modules.AbpAutoMapper().Configurators.Add(cfg =>
      {
          cfg.LicenseKey = "<your AutoMapper license key>";
      });
  }
  

  You can also read the license key from configuration or an environment variable instead of hardcoding it.

  Thank you.

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  KieranIrl created 3 months ago

  Hi,

  Following up on the earlier advice to pin AutoMapper to 15.1.3 and set the licence key via PreInitialize(). We implemented this but there is an error still .,

  Looks like that access to whatever method the abp package is using has been removed or limited ? Can you advise on a fix or solution?

  ENVIRONMENT ABP / ANZ: 11.2.0 / 15.3 | AutoMapper: 15.1.3 | TFM: net10.0

  THE PROBLEM [10:47:09 ERR] Microsoft.Extensions.Hosting.Internal.Host Hosting failed to start System.MethodAccessException: Attempt by method 'Abp.AutoMapper.AbpAutoMapperModule.CreateMappings()' to access method 'AutoMapper.MapperConfiguration..ctor(System.Action1<AutoMapper.IMapperConfigurationExpression>)' failed. at Abp.AutoMapper.AbpAutoMapperModule.CreateMappings() at Abp.AutoMapper.AbpAutoMapperModule.PostInitialize() at Abp.Modules.AbpModuleManager.<>c.<StartModules>b__15_2(AbpModuleInfo module) at System.Collections.Generic.List1.ForEach(Action1 action) at Abp.Modules.AbpModuleManager.StartModules() at Abp.AbpBootstrapper.Initialize() at Abp.AspNetCore.AbpApplicationBuilderExtensions.InitializeAbp(IApplicationBuilder app) at Abp.AspNetCore.AbpApplicationBuilderExtensions.UseAbp(IApplicationBuilder app, Action1 optionsAction) at TCM.Web.Startup.Startup.Configure(IApplicationBuilder app, IWebHostEnvironment env, ILoggerFactory loggerFactory, IHttpContextAccessor accessor) in C:\Code\TCMRepo\aspnet-core\src\TCM.Web.Host\Startup\Startup.cs:line 392 at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span1 copyOfArgs, BindingFlags invokeAttr) at System.Reflection.MethodBaseInvoker.InvokeWithFewArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at Microsoft.AspNetCore.Hosting.ConfigureBuilder.Invoke(Object instance, IApplicationBuilder builder) at Microsoft.AspNetCore.Hosting.GenericWebHostService.StartAsync(CancellationToken cancellationToken) at Microsoft.Extensions.Hosting.Internal.Host.<StartAsync>b__14_1(IHostedService service, CancellationToken token) at Microsoft.Extensions.Hosting.Internal.Host.ForeachService[T](IEnumerable1 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List1 exceptions, Func3 operation) Unhandled exception. System.MethodAccessException: Attempt by method 'Abp.AutoMapper.AbpAutoMapperModule.CreateMappings()' to access method 'AutoMapper.MapperConfiguration..ctor(System.Action1<AutoMapper.IMapperConfigurationExpression>)' failed. at Abp.AutoMapper.AbpAutoMapperModule.CreateMappings() at Abp.AutoMapper.AbpAutoMapperModule.PostInitialize() at Abp.Modules.AbpModuleManager.<>c.<StartModules>b__15_2(AbpModuleInfo module) at System.Collections.Generic.List1.ForEach(Action1 action) at Abp.Modules.AbpModuleManager.StartModules() at Abp.AbpBootstrapper.Initialize() at Abp.AspNetCore.AbpApplicationBuilderExtensions.InitializeAbp(IApplicationBuilder app) at Abp.AspNetCore.AbpApplicationBuilderExtensions.UseAbp(IApplicationBuilder app, Action1 optionsAction) at TCM.Web.Startup.Startup.Configure(IApplicationBuilder app, IWebHostEnvironment env, ILoggerFactory loggerFactory, IHttpContextAccessor accessor) in C:\Code\TCMRepo\aspnet-core\src\TCM.Web.Host\Startup\Startup.cs:line 392 at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span1 copyOfArgs, BindingFlags invokeAttr) at System.Reflection.MethodBaseInvoker.InvokeWithFewArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at Microsoft.AspNetCore.Hosting.ConfigureBuilder.Invoke(Object instance, IApplicationBuilder builder) at Microsoft.AspNetCore.Hosting.GenericWebHostService.StartAsync(CancellationToken cancellationToken) at Microsoft.Extensions.Hosting.Internal.Host.<StartAsync>b__14_1(IHostedService service, CancellationToken token) at Microsoft.Extensions.Hosting.Internal.Host.ForeachService[T](IEnumerable1 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List1 exceptions, Func3 operation) at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken) at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token) at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token) at TCM.Web.Startup.Program.Main(String[] args) in C:\Code\TCMRepo\aspnet-core\src\TCM.Web.Host\Startup\Program.cs:line 27 at TCM.Web.Startup.Program.<Main>(String[] args)

  CURRENT WORKAROUND Reverted to AutoMapper 14.0.0. Not ideal as its carrying a CVE that our sec team would prefer is dealt with .

  Thanks Thomas Murphy

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  KieranIrl created 3 months ago

  Hi,

  Following up on the earlier advice to pin AutoMapper to 15.1.3 and set the licence key via PreInitialize(). We implemented this but there is an error still .,

  Looks like that access to whatever method the abp package is using has been removed or limited ? Can you advise on a fix or solution?

  ENVIRONMENT ABP / ANZ: 11.2.0 / 15.3 | AutoMapper: 15.1.3 | TFM: net10.0

  THE PROBLEM [10:47:09 ERR] Microsoft.Extensions.Hosting.Internal.Host Hosting failed to start System.MethodAccessException: Attempt by method 'Abp.AutoMapper.AbpAutoMapperModule.CreateMappings()' to access method 'AutoMapper.MapperConfiguration..ctor(System.Action1<AutoMapper.IMapperConfigurationExpression>)' failed. at Abp.AutoMapper.AbpAutoMapperModule.CreateMappings() at Abp.AutoMapper.AbpAutoMapperModule.PostInitialize() at Abp.Modules.AbpModuleManager.<>c.<StartModules>b__15_2(AbpModuleInfo module) at System.Collections.Generic.List1.ForEach(Action1 action) at Abp.Modules.AbpModuleManager.StartModules() at Abp.AbpBootstrapper.Initialize() at Abp.AspNetCore.AbpApplicationBuilderExtensions.InitializeAbp(IApplicationBuilder app) at Abp.AspNetCore.AbpApplicationBuilderExtensions.UseAbp(IApplicationBuilder app, Action1 optionsAction) at TCM.Web.Startup.Startup.Configure(IApplicationBuilder app, IWebHostEnvironment env, ILoggerFactory loggerFactory, IHttpContextAccessor accessor) in C:\Code\TCMRepo\aspnet-core\src\TCM.Web.Host\Startup\Startup.cs:line 392 at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span1 copyOfArgs, BindingFlags invokeAttr) at System.Reflection.MethodBaseInvoker.InvokeWithFewArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at Microsoft.AspNetCore.Hosting.ConfigureBuilder.Invoke(Object instance, IApplicationBuilder builder) at Microsoft.AspNetCore.Hosting.GenericWebHostService.StartAsync(CancellationToken cancellationToken) at Microsoft.Extensions.Hosting.Internal.Host.<StartAsync>b__14_1(IHostedService service, CancellationToken token) at Microsoft.Extensions.Hosting.Internal.Host.ForeachService[T](IEnumerable1 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List1 exceptions, Func3 operation) Unhandled exception. System.MethodAccessException: Attempt by method 'Abp.AutoMapper.AbpAutoMapperModule.CreateMappings()' to access method 'AutoMapper.MapperConfiguration..ctor(System.Action1<AutoMapper.IMapperConfigurationExpression>)' failed. at Abp.AutoMapper.AbpAutoMapperModule.CreateMappings() at Abp.AutoMapper.AbpAutoMapperModule.PostInitialize() at Abp.Modules.AbpModuleManager.<>c.<StartModules>b__15_2(AbpModuleInfo module) at System.Collections.Generic.List1.ForEach(Action1 action) at Abp.Modules.AbpModuleManager.StartModules() at Abp.AbpBootstrapper.Initialize() at Abp.AspNetCore.AbpApplicationBuilderExtensions.InitializeAbp(IApplicationBuilder app) at Abp.AspNetCore.AbpApplicationBuilderExtensions.UseAbp(IApplicationBuilder app, Action1 optionsAction) at TCM.Web.Startup.Startup.Configure(IApplicationBuilder app, IWebHostEnvironment env, ILoggerFactory loggerFactory, IHttpContextAccessor accessor) in C:\Code\TCMRepo\aspnet-core\src\TCM.Web.Host\Startup\Startup.cs:line 392 at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span1 copyOfArgs, BindingFlags invokeAttr) at System.Reflection.MethodBaseInvoker.InvokeWithFewArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at Microsoft.AspNetCore.Hosting.ConfigureBuilder.Invoke(Object instance, IApplicationBuilder builder) at Microsoft.AspNetCore.Hosting.GenericWebHostService.StartAsync(CancellationToken cancellationToken) at Microsoft.Extensions.Hosting.Internal.Host.<StartAsync>b__14_1(IHostedService service, CancellationToken token) at Microsoft.Extensions.Hosting.Internal.Host.ForeachService[T](IEnumerable1 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List1 exceptions, Func3 operation) at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken) at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token) at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token) at TCM.Web.Startup.Program.Main(String[] args) in C:\Code\TCMRepo\aspnet-core\src\TCM.Web.Host\Startup\Program.cs:line 27 at TCM.Web.Startup.Program.<Main>(String[] args)

  CURRENT WORKAROUND Reverted to AutoMapper 14.0.0. Not ideal as its carrying a CVE that our sec team would prefer is dealt with .

  Thanks

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  oguzhanagir created 3 months ago

  Support Team

  Hi @KieranIrl

  Thanks for the detailed stack trace. You are right; this is not a license-key configuration issue.

  AutoMapper 15 changed the public MapperConfiguration constructor. The current Abp.AutoMapper package still creates the configuration using the old one-argument constructor, so overriding/pinning AutoMapper to 15.1.3 can cause this runtime MethodAccessException.

  So, with the current Abp.AutoMapper 11.2.0 package, pinning AutoMapper to 15.1.3 is not a safe workaround. Our earlier guidance was incomplete for this case.

  We need to update Abp.AutoMapper itself to use the AutoMapper 15 API, where MapperConfiguration is created with an ILoggerFactory, and test it with the matching AutoMapper.Collection version.

  • keep using the AutoMapper version currently supported by Abp.AutoMapper;
  • if this is urgent, use a locally patched Abp.AutoMapper build that creates MapperConfiguration with the new AutoMapper 15 constructor and validates the compatible AutoMapper.Collection version.

  The AutoMapper license key configuration is still required for AutoMapper 15+, but it does not fix this constructor compatibility issue.

  Thank you.

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  KieranIrl created 2 months ago

  Hi @oguzhanagir

  Any updates on when an update to Abp.Automapper will arrive ?

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  oguzhanagir created 2 months ago

  Support Team

  Hi @KieranIrl

  Thank you for following up, and we apologize for the earlier incomplete guidance.

  We do not plan to release an AutoMapper 15-compatible update for the Abp.AutoMapper package. The package is deprecated and will remain on its currently supported AutoMapper version. ASP.NET Zero now uses Mapperly as its supported object-mapping integration, and AutoMapper's licensing changes in newer versions are also a factor in this direction.

  Please do not override AutoMapper to version 15.x in a project that uses the current Abp.AutoMapper package. As you found, this is incompatible with the package and results in the MethodAccessException at startup.

  If migrating to Mapperly is not currently feasible, maintaining a local fork or a custom AutoMapper integration compatible with your selected AutoMapper version is the available option. In that case, compatibility testing and AutoMapper licensing compliance would be your responsibility.

  We recommend planning an incremental migration to Mapperly for new mappings and moving existing mappings over in stages.

  Thank you for your understanding.

  Best regards

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  ayoyusuf created 2 months ago

  Hi @AspnetZeroSupport Can you at least provide a patch in/with which it's still easy to switch to your last supported Abp.AutoMapper (as we gradually move to Mapperly or decide to Upgrade.) Without errors. The provided guide still throws errors.

  This is such a breaking change, We would appreciate that such level of breaking change should be properly handled with a properly elongated transition option that does not feel like a hack considering you have customers with an enterprise production system reliant on your product which is the primary sales pitch of ASP.NET Zero.

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  oguzhanagir created 2 months ago

  Support Team

  Hi @ayoyusuf

  Thank you for the detailed feedback. We understand your concern, especially given the impact this change may have on enterprise production systems.

  We have started working on this issue and will provide further information along with a proper fix or patch that supports a smoother transition. I will update you as soon as we have a concrete solution available.

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  KieranIrl created one month ago

  [oguzhanagir] said: Hi @ayoyusuf

  Thank you for the detailed feedback. We understand your concern, especially given the impact this change may have on enterprise production systems.

  We have started working on this issue and will provide further information along with a proper fix or patch that supports a smoother transition. I will update you as soon as we have a concrete solution available.

  Hi oguzhanagir

  Any update on this , we like many other customers are not in aposition to move everything to mapperly and are now living with a high cve warning showing up and being flagged ,

  What is the timeline for this fix ?

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  oguzhanagir created one month ago

  Support Team

  Hi @KieranIrl

  We will be publishing a detailed blog post very soon explaining how to switch from Mapperly to AutoMapper. This blog post will show you the steps to make a smooth transition. We will keep you informed here.

  Thank you

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  ayoyusuf created one month ago

  Kndly let us know the actual range of "very soon" so we can also plan versus checking daily for the last 3 weeks. Thanks.

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  oguzhanagir created one month ago

  Support Team

  Hi @ayoyusuf

  Sorry for the inconvenience caused by having to check repeatedly over the last few weeks.

  In the meantime, we’ve published a detailed guide on using AutoMapper after migrating to Mapperly, which may help with the transition:

  https://aspnetzero.com/blog/using-automapper-after-migrating-to-mapperly

  Thanks for your patience and understanding.

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel