MVVM Solution structure

MVVM Solution structure

I'd like to understand the best practice for structuring an MVVM solution.
Currently I've created a separate project for my View and my ViewModel. My
View project references my ViewModel project. So far so good. When it
comes to implementing navigation my ViewModel classes need access to the
RootFrame in order to navigate around, but the RootFrame resides in
App.xaml which is in the View project. So I have a circular dependency
issue here.
Is there a recommended structure I should be using? I could just lump this
all into one big project but in order to decouple the View and ViewModel I
feel like having separate projects is a better approach.