NOTE: a related question from ~ 2 years ago just confirmed that SL3 cannot do this.
Since Silverlight 5 (AFAICT) still does not have editing and continuation support (even for an external browser, again AFAICT), I wanted to ask if anyone knows what made it so difficult for Silverlight to work? I would be happy if it were even limited to a specific scenario (e.g. IE10 on Win7 +, only 32-bit Silverlight 5), because at least I could develop against it much faster / more productively, and then have other platforms for testing / checking when it worked fine in one scenario.
I wondered which scenarios would be closest, but would work on editing and continuation. The only thing that jumps at me is to create a WPF application that lives in the same solution (possibly using Prism 4, since it aims to minimize the necessary changes between WPF and Silverlight application) and develop them “together” having the ability to use EnC for a WPF application, and then, hopefully, only a minor development in Silverlight will be required.
These are a lot more problems than I would like to get through, and I wonder what else might work. For example, .NET 4 can load / use Silverlight 4 assemblies, and WPF can host (IIRC) Silverlight, so I can create a WPF shell that actually runs my real Silverlight application (just hosted in a WPF, .NET 4 CLR application).
Nevertheless, such efforts shoot in the dark (at best), but at least in some understanding of what is happening with the current Silverlight CLR / runtime / environment, which makes it difficult to use EnC in the first place. Knowing that we hope will help in solving more efficient (less complex) workarounds, at least theoretically. :)
NOTE. The answers, which only work in certain situations (as indicated above, e.g. IE10 + Win8 + SL5), are still wonderful - I would rather use this function for a while than never! :)