My shop is moving towards re-working the app to be a combination of wpf and web forms. Some functionality will be facing the public via web forms and some will be internal only via wpf. I'm trying to find a common architecture for both sides of the equation. From what I've seen so far wvvm is the best bet for the wpf side, but that doesn't seem to apply as well to web forms.
There is Prism. Prism is designed to help you more easily build modular Windows Presentation Foundation (WPF) and Silverlight client applications. These types of applications typically feature multiple screens, rich, flexible user interaction and data visualization, and role-determined behavior. They are "built to last" and "built for change."
Since you have picked to very different presentation platforms why can't you have two very different architectures? Web Forms and Win Forms or WPF and Silverlight.
Thanks for the replies...
Re "why can't you have two very different architectures? Web Forms and Win Forms or WPF and Silverlight." Microsoft announced awhile back that there would be no new development re WinForms -- so it doesn't make any sense to go that route...
The reason for the common architecture (if possible) if so we don't have 2 different code bases/knowledge bases etc etc...
The app is very much lob (line of business) -- heavy use of grids and data entry forms etc etc...I know when wpf initially came on the sceene there wasn't much in terms of data controls (such as no data grid) but now has controls via Telerik (sp?) and others including Microsoft itself...had been leaning toward webForms for same reason...what's the status re silverlight at this point in time?
Thx