Do they both do the same thing but in a different way?
Are there some things one will do but not the other?
I am currently using Zone.UmbracoMapper with our umbraco 7.x projects, and I haven't started using umbraco 8.1 yet, just thinking about what we'll need to address.
Hi Murray - no, they aren't the same thing or potential direct replacemetns for each other.
I chose "Umbraco Mapper" for the package name some years back, thinking that it was "kind of like AutoMapper, but for Umbraco data". So taking IPublishedContent items, and mapping via convention and configuration to POCO classes (normally used as view models).
More recently, in core, they've decided to not use AutoMapper internally and instead to develop their own, more focused mapping library, for performance reasons. They've called this "Umbraco Mapper" too. As I understand, you can use this as a developer, as an alternative to AutoMapper, should you want to.
I may consider a new name for the package if it continues to cause confusion down the line.
Should just add I have released an update for the package "Umbraco Mapper" for version 8, so it's still available if you'd like to consider continuing to use it.
Umbraco.Core.Mapping.UmbracoMapper vs Zone.UmbracoMapper.V7.UmbracoMapper
Hi, I'm wondering how this package compares to or overlaps with the new Core.Mapping in Umbraco. https://our.umbraco.com/documentation/Reference/Mapping/
Do they both do the same thing but in a different way? Are there some things one will do but not the other?
I am currently using Zone.UmbracoMapper with our umbraco 7.x projects, and I haven't started using umbraco 8.1 yet, just thinking about what we'll need to address.
Cheers. Murray.
Hi Murray - no, they aren't the same thing or potential direct replacemetns for each other.
I chose "Umbraco Mapper" for the package name some years back, thinking that it was "kind of like AutoMapper, but for Umbraco data". So taking
IPublishedContentitems, and mapping via convention and configuration to POCO classes (normally used as view models).More recently, in core, they've decided to not use AutoMapper internally and instead to develop their own, more focused mapping library, for performance reasons. They've called this "Umbraco Mapper" too. As I understand, you can use this as a developer, as an alternative to AutoMapper, should you want to.
I may consider a new name for the package if it continues to cause confusion down the line.
Andy
Should just add I have released an update for the package "Umbraco Mapper" for version 8, so it's still available if you'd like to consider continuing to use it.
Andy
is working on a reply...