Somehow the subjects on this page are not hyperlinks, only the first item is. This makes it hard to read the documentation which is there.

@Gerhard

Can you post this question on the mailing list, or on Stack Overflow? It's a good question, I just want to make sure that the answer can be found by others easily.

What's about lazy loading? If I use a ORM handling database traffic (like OpenAccess from Telerik) I have full support for lazy loading. Now I want to map such an object to a new object, which is build up to handle GUI-tasks. Do I loose the lazy loading option? Whats about the situation, my original object contains a very long list of something, which is put on screen very seldom? Now it's very simple by using the original object, but GUI and DB centric tasks get mixed up.
With Automapper or some tool like this, I will be able to seperate GUI and DB concerns, which is a good practice, but I really won't loose lazy loading. This would be a huge performance and memory usage drawback!!

Thanks for helping out and clearify that here.

Any plans complete this documentation page? Or am I looking in the wrong place? Maybe provide a demo app like to blog app in the video that demonstartes the more advanced features like custom mapping.

@tommck You can use the Mapper.Map(source, dest) overload that takes in the destination object.

Are there plans to handle bi-directional mapping? I was contemplating using this for mapping/flattening some data from a service and then sending the data back. There doesn't seem to be a way to auto-update the original objects

Here are two topics I'd like to see discussed in the documentation:

1. What is the difference between constructing, converting, formatting, resolving, and "mapping from"? The differences between some of these are quite subtle, and it can be difficult to determine which one to choose.
2. What is the difference between Ignore() and UseDestinationValue()?