Therefore I don't know how to handle this. I've done some research on Silverlight Assembly loading and I believe that only one version of a given assembly can be loaded at a time. Plugins and the host are all meant to be independent but with this problem in mind, I realise that a given plugin could work for a while, and then I update a reference of the host app, or add a new plugin, causing another plugin to break. That is a problem that is extremely likely to happen. host app references the version 1.0 of the reactive extensions dll and plugin C refernces the version 2.0 of the same dll. I don't think that Silverlight 5.x even works with this version of the Extended Kernel, but I could be wrong here. plugin A references the version 1.0 of the silverlight toolkit dll and plugin B references the version 2.0 of the same dll. I'm wondering if it is possible to either use a older version of ntdll.dll or investigate parts of the ntdll.dll file to determine what caused Silverlight to not work anymore either. It's not perfect, but it brings IE6+ up to nearly Chrome's level of HTML5 support for selected sites/pages/apps, without sacrificing IE6 compatibility on pages that don't target it. Now the problem arises when different plugins and/or the host app reference different versions of the same assembly. Another thing to consider, regarding older versions of IE and relying on plugins like Flash/Silverlight, is the Chrome Frame plugin. Plug ins can be created by third parties. There is a silverlight host app, and the app can download plugins on the fly to add functionality.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |