Bug 67404 - CLI bridge is not working. A lot of namespaces are missing.
Summary: CLI bridge is not working. A lot of namespaces are missing.
Status: RESOLVED DUPLICATE of bug 67725
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: sdk (show other bugs)
Version:
(earliest affected)
4.1.0.4 release
Hardware: x86 (IA32) Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-27 16:04 UTC by serg
Modified: 2015-06-18 12:02 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description serg 2013-07-27 16:04:04 UTC
My VB.NET program, involving CLI, worked with lbo 3.6.6.
With 4.1.0 it says "Could not load type'unoidl.com.sun.star.frame.XDesktop' from assembly cli_oootypes".

I looked, by means of Visual Studio, at the content of cli_oootypes and found out that it is virtually empty. All unoidl.com.sun.star namespaces are gone.

I forcibly rewrote cli_oootypes.dll in the system by that from lbo 4.0.b2 (it just happend that I had it) and all namespaces reappeared and my program appeared to be working again.
Comment 1 kpreisert 2013-09-04 09:19:17 UTC
Same here. My application currently only works if I deliver an older version of cli_oootypes.dll with it. The current version installed in the GAC is missing most of the namespaces and types.
Comment 2 serg 2013-12-20 22:38:43 UTC
This bug is the same as https://bugs.freedesktop.org/show_bug.cgi?id=67725 and it is fixed.
Comment 3 QA Administrators 2015-04-19 03:22:15 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

   *Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later)
   https://www.libreoffice.org/download/

   *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
 
   *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

   *Update the version field
   *Reply via email (please reply directly on the bug tracker)
   *Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 

1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug 
3. Leave a comment with your results. 
4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 
4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
Comment 4 Buovjaga 2015-06-18 12:02:29 UTC
Dupe per comment 2

*** This bug has been marked as a duplicate of bug 67725 ***