c# - What is your strategy on implementation of Visual Inheritance In MVVM? -


I want to write an extension (notification) screen on my framework with MVVM pattern. There will be a basic description view model and this toolbar has toolbars and buttons (save, delete, new button, etc.). And the users of this profile write their / her extension (notice) screen without using the manually added toolbar. The visual model of their expansion (information) screen will be inherited from the description details of the framework. That's why the toolbar is added to its details screen.

Has anyone implemented such a situation in this way or can you give me a pattern or strategy on this issue? Thanks all

I do not use visual heritage. Instead I have the main window with the button toolbar and area where I plug in user controls

For each user control the applicable interface, ViewModels which is the command for the button on the toolbar, I can share buttons to reduce the implementation.

See examples in this MSDN article:


Comments

Popular posts from this blog

Eclipse CDT variable colors in editor -

AJAX doesn't send POST query -

wpf - Custom Message Box Advice -