Woefully Behind in Upgrades on this project #3954
-
|
hello all, I recently took over the dev manager role on a call center based app for an insurance company and I see they are using AutoMapper 4.x on a .net 4.5.2 app. I realize I need to get this beast to .net core eventually, but was hoping for an interim approach. I'm trying to cherry pick a version of Automapper I can successfully run in .net 4.8. The highest explicit support I see it 4.6.1, which really is no better than 4.5.2. Any help or advice of a direction without refactoring the app to .net core? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
Are you trying to upgrade AutoMapper? If so I'd just go one version at a time, there are upgrade guides for each major version (that had major breaking changes). The .NET 4.6.1 vs. .NET 4.8 support is irrelevant, it runs just fine. That's just the minimum version we support, it also supports everything above that. |
Beta Was this translation helpful? Give feedback.
-
|
I really have no choice other than to leap from 4.x to 10.x. Thanks for clarification on the dependency. |
Beta Was this translation helpful? Give feedback.
-
Well GOOD LUCK SIR |
Beta Was this translation helpful? Give feedback.
-
|
I appreciate the speedy reply and the challenge ahead |
Beta Was this translation helpful? Give feedback.
Are you trying to upgrade AutoMapper? If so I'd just go one version at a time, there are upgrade guides for each major version (that had major breaking changes).
The .NET 4.6.1 vs. .NET 4.8 support is irrelevant, it runs just fine. That's just the minimum version we support, it also supports everything above that.