1 - Introduction
In my previous post, I said that Acropolis provide out of the box 2 kinds of Navigation Model : "SinglePartNavigation" and "MultiPartNavigationManager".
In conclusion of my previous post, I have shortly described the limitations of these 2 Navigation Model in fact that the Navigation between Components is hard coded on the application Design. Therefore, it enforces dependencies between Components.
That's why, building its own engine of Navigation is more convenient. This means that it is required to understand Acropolis Components Life Cycle during an Acropolis Application execution.
See the complete article on NetFxFactory