Mixing
AutoMapper 8.0 missing GetPropertyMaps
up vote
0
down vote
favorite
Prior to AutoMapper 8.0, I used this code to find a property mapping by string, example: entity model has property named "currency_id" and DTO has property named "currency". I have defined bi-directional mapping in AutoMapper, and I used this code to find source/target property relat
public static string GetDestinationPropertyFor<TSrc, TDst>(IMapper IMapper, string sourceProperty)
{
var mapper = AutoMapper.IMapper.ConfigurationProvider;
// TSrc = source generic type
// TDst = destination generic type
var map = mapper.FindTypeMapFor<TSrc, TDst>();
var propertyMap = map.GetPropertyMaps()
.FirstOrDefault(pm =>
pm.SourceMember.Name == sourceProperty
);
return propertyMap.DestinationProperty.Name;
}
In AutoMapper Profile:
this.CreateMap<EntityModels.contact, DTO.contact>()
.ForMember(m => m.currency, src => src.MapFrom(f => f.currency_id))
;
this.CreateMap<DTO.contact, EntityModels.contact>()
.ForMember(m => m.currency_id, src => src.MapFrom(f => f.currency))
;
When I called my method like this:
var _dboField = GetDestinationPropertyFor<DTO.contact, EntityModels.contact>(this.mapper, "currency");
Console.WriteLine(_dboField);
// output should be "currency_id"
After upgrading to AutoMapper 8.0 I got this error at build:
'TypeMap' does not contain a definition for 'GetPropertyMaps' and no accessible extension method 'GetPropertyMaps' accepting a first argument of type 'TypeMap' could be found (are you missing a using directive or an assembly reference?)
What are replacements for GetPropertyMaps in AutoMapper 8.0?
Thanks!
.net-core automapper
asked 3 hours ago
Luke1988
14119
add a comment |
up vote
0
down vote
favorite
Prior to AutoMapper 8.0, I used this code to find a property mapping by string, example: entity model has property named "currency_id" and DTO has property named "currency". I have defined bi-directional mapping in AutoMapper, and I used this code to find source/target property relat
public static string GetDestinationPropertyFor<TSrc, TDst>(IMapper IMapper, string sourceProperty)
{
var mapper = AutoMapper.IMapper.ConfigurationProvider;
// TSrc = source generic type
// TDst = destination generic type
var map = mapper.FindTypeMapFor<TSrc, TDst>();
var propertyMap = map.GetPropertyMaps()
.FirstOrDefault(pm =>
pm.SourceMember.Name == sourceProperty
);
return propertyMap.DestinationProperty.Name;
}
In AutoMapper Profile:
this.CreateMap<EntityModels.contact, DTO.contact>()
.ForMember(m => m.currency, src => src.MapFrom(f => f.currency_id))
;
this.CreateMap<DTO.contact, EntityModels.contact>()
.ForMember(m => m.currency_id, src => src.MapFrom(f => f.currency))
;
When I called my method like this:
var _dboField = GetDestinationPropertyFor<DTO.contact, EntityModels.contact>(this.mapper, "currency");
Console.WriteLine(_dboField);
// output should be "currency_id"
After upgrading to AutoMapper 8.0 I got this error at build:
'TypeMap' does not contain a definition for 'GetPropertyMaps' and no accessible extension method 'GetPropertyMaps' accepting a first argument of type 'TypeMap' could be found (are you missing a using directive or an assembly reference?)
What are replacements for GetPropertyMaps in AutoMapper 8.0?
Thanks!
.net-core automapper
asked 3 hours ago
Luke1988
14119
But why do you need that destination property? Maybe there is a better way to do what you want.
– Lucian Bargaoanu
1 hour ago
This is a workaround for OData bugs. API accepts arguments like property names from DTO but has to 'reflect' it to Entity model. For example: $orderby=currency should build Expression like .OrderBy(o => o.currency_id). I have this already done, what is the problem is missing feature in AutoMapper
– Luke1988
1 hour ago
That is done by mapping expressions. What you're doing is a hack. MemberMaps is what you want. But really, that code is not how you solve the problem.
– Lucian Bargaoanu
1 hour ago
Thanks. Could you give me a direction? What should I be looking for?
– Luke1988
40 mins ago
github.com/AutoMapper/AutoMapper.Extensions.ExpressionMapping
– Lucian Bargaoanu
35 mins ago
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Prior to AutoMapper 8.0, I used this code to find a property mapping by string, example: entity model has property named "currency_id" and DTO has property named "currency". I have defined bi-directional mapping in AutoMapper, and I used this code to find source/target property relat
public static string GetDestinationPropertyFor<TSrc, TDst>(IMapper IMapper, string sourceProperty)
{
var mapper = AutoMapper.IMapper.ConfigurationProvider;
// TSrc = source generic type
// TDst = destination generic type
var map = mapper.FindTypeMapFor<TSrc, TDst>();
var propertyMap = map.GetPropertyMaps()
.FirstOrDefault(pm =>
pm.SourceMember.Name == sourceProperty
);
return propertyMap.DestinationProperty.Name;
}
In AutoMapper Profile:
this.CreateMap<EntityModels.contact, DTO.contact>()
.ForMember(m => m.currency, src => src.MapFrom(f => f.currency_id))
;
this.CreateMap<DTO.contact, EntityModels.contact>()
.ForMember(m => m.currency_id, src => src.MapFrom(f => f.currency))
;
When I called my method like this:
var _dboField = GetDestinationPropertyFor<DTO.contact, EntityModels.contact>(this.mapper, "currency");
Console.WriteLine(_dboField);
// output should be "currency_id"
After upgrading to AutoMapper 8.0 I got this error at build:
'TypeMap' does not contain a definition for 'GetPropertyMaps' and no accessible extension method 'GetPropertyMaps' accepting a first argument of type 'TypeMap' could be found (are you missing a using directive or an assembly reference?)
What are replacements for GetPropertyMaps in AutoMapper 8.0?
Thanks!
.net-core automapper
asked 3 hours ago
Luke1988
14119
Prior to AutoMapper 8.0, I used this code to find a property mapping by string, example: entity model has property named "currency_id" and DTO has property named "currency". I have defined bi-directional mapping in AutoMapper, and I used this code to find source/target property relat
public static string GetDestinationPropertyFor<TSrc, TDst>(IMapper IMapper, string sourceProperty)
{
var mapper = AutoMapper.IMapper.ConfigurationProvider;
// TSrc = source generic type
// TDst = destination generic type
var map = mapper.FindTypeMapFor<TSrc, TDst>();
var propertyMap = map.GetPropertyMaps()
.FirstOrDefault(pm =>
pm.SourceMember.Name == sourceProperty
);
return propertyMap.DestinationProperty.Name;
}
In AutoMapper Profile:
this.CreateMap<EntityModels.contact, DTO.contact>()
.ForMember(m => m.currency, src => src.MapFrom(f => f.currency_id))
;
this.CreateMap<DTO.contact, EntityModels.contact>()
.ForMember(m => m.currency_id, src => src.MapFrom(f => f.currency))
;
When I called my method like this:
var _dboField = GetDestinationPropertyFor<DTO.contact, EntityModels.contact>(this.mapper, "currency");
Console.WriteLine(_dboField);
// output should be "currency_id"
After upgrading to AutoMapper 8.0 I got this error at build:
'TypeMap' does not contain a definition for 'GetPropertyMaps' and no accessible extension method 'GetPropertyMaps' accepting a first argument of type 'TypeMap' could be found (are you missing a using directive or an assembly reference?)
What are replacements for GetPropertyMaps in AutoMapper 8.0?
Thanks!
.net-core automapper
.net-core automapper
asked 3 hours ago
Luke1988
14119
asked 3 hours ago
Luke1988
14119
asked 3 hours ago
Luke1988
14119
asked 3 hours ago
Luke1988
14119
asked 3 hours ago
Luke1988
14119
14119
But why do you need that destination property? Maybe there is a better way to do what you want.
– Lucian Bargaoanu
1 hour ago
This is a workaround for OData bugs. API accepts arguments like property names from DTO but has to 'reflect' it to Entity model. For example: $orderby=currency should build Expression like .OrderBy(o => o.currency_id). I have this already done, what is the problem is missing feature in AutoMapper
– Luke1988
1 hour ago
That is done by mapping expressions. What you're doing is a hack. MemberMaps is what you want. But really, that code is not how you solve the problem.
– Lucian Bargaoanu
1 hour ago
Thanks. Could you give me a direction? What should I be looking for?
– Luke1988
40 mins ago
github.com/AutoMapper/AutoMapper.Extensions.ExpressionMapping
– Lucian Bargaoanu
35 mins ago
add a comment |
But why do you need that destination property? Maybe there is a better way to do what you want.
– Lucian Bargaoanu
1 hour ago
This is a workaround for OData bugs. API accepts arguments like property names from DTO but has to 'reflect' it to Entity model. For example: $orderby=currency should build Expression like .OrderBy(o => o.currency_id). I have this already done, what is the problem is missing feature in AutoMapper
– Luke1988
1 hour ago
That is done by mapping expressions. What you're doing is a hack. MemberMaps is what you want. But really, that code is not how you solve the problem.
– Lucian Bargaoanu
1 hour ago
Thanks. Could you give me a direction? What should I be looking for?
– Luke1988
40 mins ago
github.com/AutoMapper/AutoMapper.Extensions.ExpressionMapping
– Lucian Bargaoanu
35 mins ago
But why do you need that destination property? Maybe there is a better way to do what you want.
– Lucian Bargaoanu
1 hour ago
But why do you need that destination property? Maybe there is a better way to do what you want.
– Lucian Bargaoanu
1 hour ago
This is a workaround for OData bugs. API accepts arguments like property names from DTO but has to 'reflect' it to Entity model. For example: $orderby=currency should build Expression like .OrderBy(o => o.currency_id). I have this already done, what is the problem is missing feature in AutoMapper
– Luke1988
1 hour ago
This is a workaround for OData bugs. API accepts arguments like property names from DTO but has to 'reflect' it to Entity model. For example: $orderby=currency should build Expression like .OrderBy(o => o.currency_id). I have this already done, what is the problem is missing feature in AutoMapper
– Luke1988
1 hour ago
That is done by mapping expressions. What you're doing is a hack. MemberMaps is what you want. But really, that code is not how you solve the problem.
– Lucian Bargaoanu
1 hour ago
That is done by mapping expressions. What you're doing is a hack. MemberMaps is what you want. But really, that code is not how you solve the problem.
– Lucian Bargaoanu
1 hour ago
Thanks. Could you give me a direction? What should I be looking for?
– Luke1988
40 mins ago
Thanks. Could you give me a direction? What should I be looking for?
– Luke1988
40 mins ago
github.com/AutoMapper/AutoMapper.Extensions.ExpressionMapping
– Lucian Bargaoanu
35 mins ago
github.com/AutoMapper/AutoMapper.Extensions.ExpressionMapping
– Lucian Bargaoanu
35 mins ago
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371494%2fautomapper-8-0-missing-getpropertymaps%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
But why do you need that destination property? Maybe there is a better way to do what you want.
– Lucian Bargaoanu
1 hour ago
This is a workaround for OData bugs. API accepts arguments like property names from DTO but has to 'reflect' it to Entity model. For example: $orderby=currency should build Expression like .OrderBy(o => o.currency_id). I have this already done, what is the problem is missing feature in AutoMapper
– Luke1988
1 hour ago
That is done by mapping expressions. What you're doing is a hack. MemberMaps is what you want. But really, that code is not how you solve the problem.
– Lucian Bargaoanu
1 hour ago
Thanks. Could you give me a direction? What should I be looking for?
– Luke1988
40 mins ago
github.com/AutoMapper/AutoMapper.Extensions.ExpressionMapping
– Lucian Bargaoanu
35 mins ago