Problem description: When LibreOffice is installed past to OpenOffice an application using the OOo CLI bridge won't work anymore. LibreOffice puts the CLI bridge assemblies (cli_types.dll, etc.) into the .NET GAC (Global Assembly Cache) as OOo does. Steps to reproduce: 1. Install OOo 2.4.0. 2. Create an application that interacts with OOo 2.4.0 using the CLI bridge. 3. Install LibreOffice 4.0.0.1. Current behavior: Interaction of custom application and OOo 2.4.0 does not work anymore. Error: Die Datei oder Assembly "cli_basetypes.dll" oder eine Abhängigkeit davon wurde nicht gefunden. Die gefundene Manifestdefinition der Assembly stimmt nicht mit dem Assemblyverweis überein. (Ausnahme von HRESULT: 0x80131040) (appropriate "cli_basetypes.dll" cannot be found, probably because LibreOffice has overwritten OOo CLI bridge assemblies) Expected behavior: Running OOo and LibreOffice in parallel should be possible. LibreOffice should use different (TCP/IP, Named Pipe) ports and/or a different namespaces for CLI bridge assemblies. Operating System: Windows 7 Version: 4.0.0.1 rc
I did increase the importance of this bug because of the release notes; this is definitely an undesirable interaction between LibreOffice and OpenOffice.org: > If you notice undesirable interactions between LibreOffice and > OpenOffice.org, please report this as a bug.
This is a known issue but after talking to one of the core devs...it may be closed as WONTFIX. I'm going to get a little more input but that's where it's leaning right now
@ Michael - more .net issues, you mind taking a look at this one? One developer so far has said won't fix but just wanted to confirmation.
This looks like it may be related to bug#58275. In general in that bug - disabling .Net wherever the platform is in a confused state at install time seems like a -much- better option than hindering users from installing without XYZ version of .Net installed too: our dependency on that is -profoundly- optional. Andras - any more to add ?
It is a conflict between OOo (AOO) and LibreOffice, they fight for a single resource on Windows, like they fight for file associations. It affects very few users, those who have both OOo and LibreOffice installed and use .NET to automate the suite. I don't know who said WONTFIX (Tor?, Noel?), but the fix would not be as easy as in case of bug#58275. Reporter suggested that LibreOffice should use different (TCP/IP, Named Pipe) ports and/or a different namespaces for CLI bridge assemblies.
Markus said in his opinion this is known and is very unlikely to get fixed. I could be misquoting but that's what I remember
trying to get this out of UNCONFIRMED status - any word on what is the appropriate status?
So - lets mark it wontfix for now - in the absence of any well tested patch to adapt / rename all integration points: pipe names etc. for all languages on all platforms that is consistent and works well I can't see this getting fixed. It is surely no great hardship to only have one suite on your machine ? :-) I'd be more interested in fixing any other bugs you have that inhibit using LibreOffice for 100% of use-cases. Thanks.