Home/ Questions/Q 3212930
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T14:53:21+00:00

In our product, we use MVVM model first approach and it works nicely but

  • 0

In our product, we use MVVM model first approach and it works nicely but with one caveat. When view becomes complex it takes time to create it from the data template. If the view is shown and hidden frequently, it becomes slightly irritating. If using view first, it would be easy enough to cache a view if needed – but when using DataTemplate and model first, we do not have much control of view creation.
Anybody solved this problem already without switching to the view first method?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    with viewmodel first approach i think you have no chance to “cache” the view. so you may consider to use view first and a viewmodel locator for the heavyweight datatemplates workflows. here is a solution when using datatemplates with lists.

    but maybe there is any solution with overriding the wpf datatemplate mechanism?

    edit: what if you create just a “markerview” for your viewmodel, so wpf datatemplate can find it. and then within this marker view you create/rehydrate the real view? something like an view service locator?

    • 0