I downloaded prism5.exe from Microsoft and expanded it which left a variety of quick start projects. I simply opened the 'stock' BasicMVVMQuickstart_Desktop solution.
At first I received a 'couldn't find name in the namespace error' (on the same line as noted below, BTW), but after closing and reopening Visual Studio per one stack overflow post, I am now receiving this error:
Your views must implement IView
This is the XAML code and the line with the error:
I have referenced other stack overflow questions but still cannot resolve this.
One post suggested upgrading to Prism 6. I performed the only upgrade available in NuGet which updated Microsoft.Practices.Prism.Mvvvm to v 1.1.1.0.
I don't see Prism.Core anywhere in my project, so I'm guessing that's something about Visual Studio and packages that I don't quite understand. Anyway, I uninstalled Prism.Core 4.0 and then Installed Prism.Core 6.2, but since I don't see Prism.Core anywhere in Visual Studio I don't know if anything was changed.
So in addition to trying to understand how to remedy the error above, I'd also like to understand how I use Prism 6 instead of Prism 5. It's a little confusing to me.
You are using an older version of Prism. I would (highly) recommend starting over with the latest bits from the Prism team. You can get that from the link below. There are plenty of samples to choose from, too. The documentation is up to date, which is always nice. This will be much easier than trying to upgrade the code you downloaded from Microsoft. There are plenty of breaking changes between that version and the latest.
You can get Prism from NuGet, too. Get one of the packages that have the IOC container already included, like Unity (Prism.Unity), or MEF (Prism.Mef). Just getting the Core package will leave much to be desired.
The packages with an IOC contain include all the dependencies (Prism.Core, Prism.Wpf, etc.) needed to get started. I am assuming you are doing a WFP application. I use the Unity version, and I would recommend that over the MEF version, because I found MEF to be interesting to troubleshoot. Go with what you like, though.
Good luck!