Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cascade windows opening & MVVMLight requirement

See original GitHub issue

Hello @FantasticFiasco, Can I use your Framework for opening Windows one from another? Like: InitialWindow -> MainWindow -> SomeDialog. If so I would be grateful for some tip how to do that. I would also like to ask about registering in SimpleIoc I do not use any framework for MVVM. Is the MVVMLight required for your framework to work?

Issue Analytics

State:
Created 6 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

FantasticFiascocommented, Jul 27, 2017

Hi Niko0pl, welcome to MVVM Dialogs!

Can I use your Framework for opening Windows one from another? Like: InitialWindow -> MainWindow -> SomeDialog.

Yes, there should be nothing special about opening a second window compared to opening the first window. Please take a look at the demos, there you will find examples on how to open windows.

I would also like to ask about registering in SimpleIoc I do not use any framework for MVVM. Is the MVVMLight required for your framework to work?

No, MVVM Dialogs does not require MVVMLight or any other MVVM framework, it can stand on its own.

0reactions

FantasticFiascocommented, Jul 28, 2017

MVVM Dialogs is opinionated when it comes to view models, but for a good reason. The change detection mechanism in WPF is most performant when the view models implement INotifyPropertyChanged.

One could argue that the error message displayed could be better, but then again I don’t often get questions regarding this particular error.