I'm creating a Prism 7 WPF/MVVM/Unity desktop application that first displays a Login View and then, when the user enters in the proper credentials and clicks the Login button, closes the Login View and then activates the real ShellView. Because the Login View has been specified to be so radically different from the ShellView (no caption bar, no icons, no menu, not resizable, etc) the LoginView cannot easily be embedded as a hosted UserControl within the ShellView. It looks like it has to be a top level Window with its own WindowStyle (or lack of one in this case).
The only practical way I can think of doing this is to put the Login Window in the App.OnStartup() method and treat it like a modal dialog, effectively staling further processing until the Login is satisfied or killed. This is so counter to how normal Prism navigator happens that I can't help but think I'm missing a better approach. Can someone suggest a practical approach that would do the trick but be more Prism/Unity compliant?
Richard Lewis Haggard