Aug 20, 2014 at 5:47 AM
Edited Aug 20, 2014 at 5:48 AM
After spending more than a few hours on this subject, I think I have it sorted out.
Appearently there is a (big) difference in the way C# and VB treat subfolders and namespaces. Why do I find that nowhere in any documentation?
I think it would be very helpful for all those VB programmers out there to point this out more explicitly (and explain how to get over it) in the documentation.
In general what I found out is this:
When putting views in a subfolder like the framework expects, they need to be explicitly made part of the namespace Views as well. That is not done automatically as it seems to be done in C#. Moreover, in the XAML that reference to the namespace must be made
in the class header.
MainPage.xaml.vb has to be within the namespace Views like so:
''' A basic page that provides characteristics common to most applications.
Public NotInheritable Class MainPage
Public Sub New()
And in the XAML header the namespace has to be added like so:
I hope this will help some other VB programmers to be able to adopt Prism.