606393 - Install ISimple dll as a shared dll

Status: RESOLVED WONTFIX

(Core :: Disability Access APIs, defect)

Description

[Makoto Kato [:m_kato]]

I installed SeaMonkey after Firefox, AccessibleMarshal.dll via COM uses SeaMonkey version.  Because CLSID is same.

So we should change CLSID each products (Firefox, Thunderbird and SeaMonkey).

Comment 1

[James Teh [:Jamie]]

As far as I understand it, this is not an option. The registry maps from interface IIDs to the proxy stub CLSID so that COM knows which proxy to use for each interface. Even if you have two proxy dlls with different CLSIDs, the second will overwrite the interface to proxy mapping so that the second will still get used for the ISimpleDom* interfaces. Having different CLSIDs just means your first proxy dll won't be associated with any interfaces once the second is registered. The only way this would be useful is if you had different ISimpleDom* interfaces for each application (ISimpleDomNodeFirefox, ISimpleDomNodeThunderbird, etc.), which is obviously not practical.

The solution here is to install the dll as a shared dll in %systemroot%\system32, changing the version number if new interfaces get added. Installing it as a shared dll ensures that it doesn't get removed while an application that needs it is still installed. The version number ensures that a later version of the dll overrides an earlier version.

Comment 2

[Masatoshi Kimura [:emk]]

Why the case is inverted?

Comment 3

[James Teh [:Jamie]]

ISimpleDOM is effectively deprecated for new usage. Any existing usage is either in-process (JAWS) or manages its own cross-process proxy registration (NVDA). Thus, I don't think we ever need to do this.