Alistair Leslie-Hughes leslie_alistair@hotmail.com writes:
Since msxml2/4/6 all point to msxml3, having to install native msxml3 will cause all the rest to fail. As an example, mdac28 requires msxml3 to be installed (msxml3 has an incomplete IXMLParser implementation, so native has to be used). I would change msxml4/6 as well, so that installing any of the native msxml DLL wouldn't affect the others.
We could just use my previous patch, which would also resolve the issue of registry entry. That scenario is
- Clean prefix.
- Install native msxml3
- Force update of bottle (e.g. wine update)
The msxml2.DOMDocument registry entry is now incorrect.
That's a corner case that I don't think justifies duplicating such a large dll 4 times. It should be easy to avoid by using native for the other ones too. And of course fixing builtin would be even better...