Reply to: Debug XMAX in IEJune 10, 2009 at 8:53 pm
We're sure this used to work and suspect a Windows update may have changed this behavior. We can't get it working with even the simplest test samples that used to work.
MSIE creates a script engine first and instantiates XMAX second. We suspect the MSIE script engine instance is the dominant one and auto-selected for debugging which means the XMAX script engine is being ignored.
That was all done purely in MSIE without using XMetaL Developer.
We'll be running some tests to confirm that is it still possible to launch MSIE from within a debug session from XMetaL Developer in Visual Studio and I will post the results once they are known.