I have an extensive desktop application -- 30+ assemblies, uses the WPF Toolkit (datagrid), data triggers in xaml, etc. So now the customer would like to consider a web version. I have a model-view-controller architecture...So I was thinking it should not
be a big deal...But then I tried with Silverlight -- and perhaps I am missing something.
I have tried the (too-good-to-be-true) solution of adding a post-build step to run SLASM that uses ildasm and massages version numbers of mscorlib, etc. I am wondering where I might find a comprehensive list of unsupported attributes because I am guessing
that they are fairly extensive and that would be why I cannot get it to run.
So I tried creating a Silverlight Class Library and added one small xaml control as a link to the project. Ok -- That is when I learned that ControlTemplate.Triggers, Dynamic Resource, SnapsToDevicePixels, TargetName in a Setter -- all of these do not exist
So, am I missing something? How does one take a complex existing WPF desktop application and make it a web app without rewriting the UI? I have a ton of data triggers all written in xaml. I have gotten my stuff to run in a WPFWebBrowser application
-- but would much prefer Silverlight...
Any advice would be very welcome!