Hello PankajGoswami,
As far as I can see on the code you provided everything seems to be on the right track.
Please verify that:
• The RequestNavigate call is being performed. Assuming you are using a command, the issue might be related to an incorrect binding.
• The StartUpScreenViewModel class is instantiated before the RequestNavigate() call occurs. Otherwise, the view won’t be registered in the container.
Notice that the mainRegion should be a SingleActiveRegion (use a ContentControl), which only display one view at the same time.
Is there a reason why you are performing the views registrations into the container from the view model, instead of doing it when the module is initialized?
If the above does not help, please send a small repro sample (or code that provides more context) so I can troubleshoot the cause for the issue.
As far as I can see on the code you provided everything seems to be on the right track.
Please verify that:
• The RequestNavigate call is being performed. Assuming you are using a command, the issue might be related to an incorrect binding.
• The StartUpScreenViewModel class is instantiated before the RequestNavigate() call occurs. Otherwise, the view won’t be registered in the container.
Notice that the mainRegion should be a SingleActiveRegion (use a ContentControl), which only display one view at the same time.
Is there a reason why you are performing the views registrations into the container from the view model, instead of doing it when the module is initialized?
If the above does not help, please send a small repro sample (or code that provides more context) so I can troubleshoot the cause for the issue.