I’d started a discussion about a problem with a SWF file not loading an XML data file when rendered in a .NET WebBrowser control (see here)
Further investigation has revealed that if the XML data file is loaded using Action Script 2 (via XML.load()), it works. But if the SWF file in question uses Action Script 3 (via URLLoader.load(), I think), the data file is NOT loaded, UNLESS the XML file is in the same folder as the HTML file.
If either SWF file is loaded using Internet Explorer 9, then everything works OK.
Are there any know issues (which would be apparently well-hidden from Internet search engines, because we’ve been beating on those) regarding the performance of SWF + Action Script 3 + .NET WebBrowser?
It’s just so weird that there are ways to coerce the AS3 solution to work by moving files (not really an option for what we want to do), and that Internet Explorer 9 has no trouble, but the WebBrowser control (which everyone SAYS “is just a wrapper for IE”) does NOT work the same way.
Any help appreciated.
I’ll add a wrap-up to the sordid saga…
Through discussions with Microsoft and Adobe, we determined that this was indeed an issue with the Flash ActiveX control being used in a WebBrowser control. Adobe describes this as an “unsupported use case” and that’s the end of the story. There’s not going to be a “fix”. I was able to replicate the issue with the ActiveX WebBrowser control as well, so it’s not a .NET thing exclusively. And, as mentioned, the version of ActionScript in use also contributes to success or failure.
What did get done in the long run was to dynamically adjust a
<base>tag in the overall HTML document during the loading, and pointing the reference to the folder that held the SWF and XML files. Seems kludgy, but it works.