Fpr 1.8.0.32006

.NET Framework 4.5 This package targets .NET Framework 4.5. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package Fpr --version 1.8.0.32006                

                    
                

            
NuGet\Install-Package Fpr -Version 1.8.0.32006
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="Fpr" Version="1.8.0.32006" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add Fpr --version 1.8.0.32006                

                    
                

            
#r "nuget: Fpr, 1.8.0.32006"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install Fpr as a Cake Addin
#addin nuget:?package=Fpr&version=1.8.0.32006

// Install Fpr as a Cake Tool
#tool nuget:?package=Fpr&version=1.8.0.32006

A fast, fun and stimulating object to object mapper.  Kind of like AutoMapper, just simpler and way, way faster.

Product Compatible and additional computed target framework versions.
.NET Framework net45 is compatible.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.11.0 4,118 2/27/2015
1.10.4.39547 2,233 10/24/2014
1.10.3.31415 5,536 8/5/2014
1.10.2.14052 1,504 8/1/2014
1.10.1.26853 1,525 7/31/2014
1.10.0.20033 1,499 7/31/2014
1.9.1.39105 1,503 7/31/2014
1.9.0.27688 1,455 7/30/2014
1.8.0.32006 1,517 7/27/2014
1.7.6.16097 1,518 7/25/2014
1.7.5.12964 1,507 7/25/2014
1.7.4.35837 1,537 7/25/2014
1.7.3.30157 1,588 7/24/2014
1.7.0.22841 1,464 7/24/2014
1.6.0.25724 1,513 7/18/2014
1.5.0.16504 1,507 7/16/2014
1.4.0.16689 1,501 7/14/2014
1.3.2.30767 1,601 7/10/2014
1.3.1.27518 1,480 7/10/2014
1.2.1.22053 1,487 7/9/2014
1.1.9.30100 1,521 7/5/2014
1.1.8.37589 1,514 6/5/2014

Added support for custom type resolvers and custom value resolvers.  Also obsoleted IgnoreMember and MapFrom in favor of the more terse Ignore and Map.

Custom Type Resolvers

In some cases, you may want to have complete control over how an object is mapped. In this case, you can register a custom type resolver. It's important to note that when using a custom type resolver, that all other mapping associated with the type is ignored. So all mapping must take place within the resolver. The custom type resolver must implement the ITypeResolver interface and register it using MapWith().

//Example using MapWith resolver generic call.
TypeAdapterConfig<TSource, TDestination>.NewConfig()
           .MapWith<TCustomTypeResolver>();

//Example using MapWith resolver factory function
TypeAdapterConfig<TSource, TDestination>.NewConfig()
           .MapWith(() => new TCustomTypeResolver());

//Example using MapWith resolver instance
TypeAdapterConfig<TSource, TDestination>.NewConfig()
           .MapWith(customResolverInstance);
Custom Value Resolvers

In some cases, you may want to encapsulate a value conversion into a separate class. In this case, you can use a custom value resolver by registering it using Resolve(). The value resolver must implement the IValueResolver interface.

//Example using MapWith resolver generic call.
TypeAdapterConfig<TSource, TDestination>.NewConfig()
           .Resolve<TCustomValueResolver, string>(dest => dest.Name);

//Example using value resolver factory function
TypeAdapterConfig<TSource, TDestination>.NewConfig()
           .Resolve(dest => dest.Name, () => new TCustomValueResolver());

//Example using value resolver instance
TypeAdapterConfig<TSource, TDestination>.NewConfig()
           .Resolve(dest => dest.Name, customValueResolver);