Official WinForms support about prism

[brianlagunas]

Actually, there is a similar library available for WinForms called CAB (Composite UI Application Block). There is also the Smart Client Software Factory for WinForms. Unfortunately, Prism will not be supporting WinForms. The nature of Prism and it's features are tailored around the XAML platform, and do not fit well with the WinForms platform.

Thanks for the suggestion.

[mika76]

I know, but both of those project were abandoned by Microsoft years ago.

[brianlagunas]

Yeah, the same would have happened to Prism if we didn't take ownership of it. Unfortunately though, WinForms is not on our roadmap.

[briannoyes]

But also because we are an open source project, we would also encourage people to create value-add forks of our code base. Back when we first release Prism 1, we had compositewpfcontrib on codeplex for those kinds of additions, and I was the one who ported the code to support modularity and CompositePresentationEvents for Windows Forms because I was still doing plenty of Windows Forms work then to see the value in doing so.

I'm there are others who would benefit from a current Prism fork making the features that make sense and are possible in Windows Forms available there, but as Brian Lagunas said, we have to draw some bounds for our roadmap based on our team and resources, and I'm afraid Windows Forms is a little too legacy to be on that roadmap.

[Mike-E-angelo]

FWIW, I am really glad you guys took ownership of this, and shocked(!) to hear that they were considering abandoning this project. Also, it does look like Windows Forms is still part of the .NET roadmap going forward, surprisingly. But I am in agreement that it should prioritized as far as Prism goes and best relegated to external forks/contribs.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.