title: How to share the most code between a WPF and an ASP.NET MVC application?
body: <p>What architecture and patterns can I use to share the most model and logic code between a WPF and an ASP.NET MVC application?</p>
  
  <p>I am trying to achieve a bit more here than just separating my data entities from the two presentation projects. There is a lot more in common e.g. UI logic on what gets displayed under what conditions, when is something required, etc. that I would like to keep in the shared code.</p>
  
  <p><strong>ADDED:</strong> I am just beginning to really like the concept of view models independent of my entity model driving my presentation. While some of the annotations used in these are located in assemblies specific to MVC, none of the metadata provided is actually web specific. I would very much like to explore using my MVC view models as data sources for binding to WPF views. Any suggestions on this front will be most appreciated.</p>