Gabriel,
A URI is a "UNIVERSAL" resource identifier, meaning it contains all the information needed to locate a resource in your application. In the .NET world, that includes the assembly in which a type resides. If I have loosely coupled modules, then I need to know which module contains a given type before I can navigate to it.
What astounds me is that this is baked into WPF and Silverlight navigation. Why would you make your framework less functional than the one it's supposed to be replacing?
Don
A URI is a "UNIVERSAL" resource identifier, meaning it contains all the information needed to locate a resource in your application. In the .NET world, that includes the assembly in which a type resides. If I have loosely coupled modules, then I need to know which module contains a given type before I can navigate to it.
What astounds me is that this is baked into WPF and Silverlight navigation. Why would you make your framework less functional than the one it's supposed to be replacing?
Don