Interchangeability / re-usability of WPF, Silverlight and Silverlight OOB applications? -
for experienced wpfers out there, how re-usable wpf, silverlight , silverlight oob applications , components? how overlap there?
for example, write 1 application , deploy in 3 aforementioned ways?
ideally, want write little code possible , have flexibility of deploying in range of scenarios, maybe enabling functionality depending on deployment. wpf family of technologies seems starting point casual observer.. really?
the simplified version of answer is:
1. silverlight subset of wpf.
2. silverlight in browser apps , silverlight oob apps running on same framework. deployment difference.
3. oob apps can installed "trusted" apps, , have looser security restraints in browser apps.
porting wpf app silverlight going difficult, wpf app use many features of .net framework not available in smaller subset of framework available silverlight apps. want avoid.
porting silverlight app wpf easier. still challenge there features in silverlight not in wpf (though not many converse). in addition feature delta, actual framework runs silverlight/wpf apps different, during porting run amount of behavioral differences between two.
silverlight , silverlight oob apps running on same framework. possible have exact same app binary run in both places. part, behave identically. differences: in-browser apps can rely on browser features such accessing html dom, invoking javascript, etc. oob app doesn't run in browser doesn't apply. also, if dealing "trusted" oob app, can things prevented security reasons in browser (e.g. com interop).
if want create app runs in 3 places, advice start building app in-browser silverlight app self-contained, i.e. not rely on web page hosting it, , includes necessary resources inside xap package (rather relying on them being next package on web server). porting such app silverlight oob app cinch - pretty check box in visual studio , done. porting wpf significant amount of work, better going other way.
Comments
Post a Comment