I am looking for a strategy to implement a new WPF 4.0 application with the MVVM pattern that reuses various VB6 user controls. I'd like to have both WPF and VB6 controls share the same view model.
Are there any known strategies for this?
I am looking for a strategy to implement a new WPF 4.0 application with the MVVM pattern that reuses various VB6 user controls. I'd like to have both WPF and VB6 controls share the same view model.
Are there any known strategies for this?
You can host an ActiveX control in WPF, as this walkthrough shows. That is your first issue. Assuming the VB6 bits are set up as an ActiveX control, you have most of the game conquered.
Using the same view model (UI data?) in the control should not be a major undertaking, depending on how the control is written. You have to be able to direct the view model to the control, which means there is some exposed method or property.
So, I see two potential obstacles:
Unless you are absolutely forced to use the VB6 control, however, I would consider using a more modern UI element.