zoukankan      html  css  js  c++  java
  • 列表和数组

    AutoMapper only requires configuration of element types, not of any array or list type that might be used. For example, we might have a simple source and destination type:

        public class Source
        {
        	public int Value { get; set; }
        }
        
        public class Destination
        {
        	public int Value { get; set; }
        }
    

    All the basic generic collection types are supported:

        Mapper.Initialize(cfg => cfg.CreateMap<Source, Destination>());
        
        var sources = new[]
        	{
        		new Source { Value = 5 },
        		new Source { Value = 6 },
        		new Source { Value = 7 }
        	};
        
        IEnumerable<Destination> ienumerableDest = Mapper.Map<Source[], IEnumerable<Destination>>(sources);
        ICollection<Destination> icollectionDest = Mapper.Map<Source[], ICollection<Destination>>(sources);
        IList<Destination> ilistDest = Mapper.Map<Source[], IList<Destination>>(sources);
        List<Destination> listDest = Mapper.Map<Source[], List<Destination>>(sources);
        Destination[] arrayDest = Mapper.Map<Source[], Destination[]>(sources);
    

    To be specific, the source collection types supported include:

    • IEnumerable
    • IEnumerable<T>
    • ICollection
    • ICollection<T>
    • IList
    • IList<T>
    • List<T>
    • Arrays

    For the non-generic enumerable types, only unmapped, assignable types are supported, as AutoMapper will be unable to "guess" what types you're trying to map. As shown in the example above, it's not necessary to explicitly configure list types, only their member types.

    Polymorphic element types in collections

    Many times, we might have a hierarchy of types in both our source and destination types. AutoMapper supports polymorphic arrays and collections, such that derived source/destination types are used if found.

        public class ParentSource
        {
        	public int Value1 { get; set; }
        }
        
        public class ChildSource : ParentSource
        {
        	public int Value2 { get; set; }
        }
        
        public class ParentDestination
        {
        	public int Value1 { get; set; }
        }
        
        public class ChildDestination : ParentDestination
        {
        	public int Value2 { get; set; }
        }
    

    AutoMapper still requires explicit configuration for child mappings, as AutoMapper cannot "guess" which specific child destination mapping to use. Here is an example of the above types:

        Mapper.Initialize(c=> {
            c.CreateMap<ParentSource, ParentDestination>()
        	     .Include<ChildSource, ChildDestination>();
            c.CreateMap<ChildSource, ChildDestination>();
        });
        var sources = new[]
        	{
        		new ParentSource(),
        		new ChildSource(),
        		new ParentSource()
        	};
        
        var destinations = Mapper.Map<ParentSource[], ParentDestination[]>(sources);
        
        destinations[0].ShouldBeInstanceOf<ParentDestination>();
        destinations[1].ShouldBeInstanceOf<ChildDestination>();
        destinations[2].ShouldBeInstanceOf<ParentDestination>();
    
  • 相关阅读:
    hdu 2594 Simpsons’ Hidden Talents
    hdu 1358 Period
    hdu 3746 Cyclic Nacklace
    理解KMP算法
    ural 1039 Anniversary Party
    ural 1018 Binary Apple Tree
    RowDataBound事件
    aspxGridview 根据单元格值得不同,设置单元格字体的颜色(设置和读取值)
    Asp.Net中GridView加入鼠标滑过的高亮效果和单击行颜色改变
    GridView的行颜色高亮显示(包括满足条件的行)
  • 原文地址:https://www.cnblogs.com/Leman/p/5774348.html
Copyright © 2011-2022 走看看