Steps to reproduce: 1) Install LibreOffice_5.4.7.2_Win_x86.msi 2) Install LibreOffice_5.4.7.2_Win_x86_sdk.msi 3) Create a VisualStudio 2015 Project: 3.1) Append the delivered example from the SDK Installation "SpreadsheetDocHelper.cs" 3.2) Project configuration = x86 3.3) Add useLegacyV2RuntimeActivationPolicy="true" to app.config 3.4) Reference the folowing libraries: LibreOffice_5.4.7.2_Win_x86_sdk\cli\cli_basetypes.dll LibreOffice_5.4.7.2_Win_x86_sdk\cli\cli_cppuhelper.dll LibreOffice_5.4.7.2_Win_x86_sdk\cli\cli_oootypes.dll LibreOffice_5.4.7.2_Win_x86_sdk\cli\cli_ure.dll LibreOffice_5.4.7.2_Win_x86_sdk\cli\cli_uretypes.dll 3.5) Adding code to add @"c:\Program Files (x86)\LibreOffice 5\program" to "PATH" 3.6) Adding code to add @"c:\Program Files (x86)\LibreOffice 5\program" to "UNO_PATH" 3.7) compile succefully 3.8) Unregister cli-Dlls from GAC using GACBrowser to force the application to use the CLI-dlls from the location of the executable. 3.9) Run: Exception occured on the line m_xContext = uno.util.Bootstrap.bootstrap(); cppu.bootstrap(Reference<com::sun::star::uno::XComponentContext>* ) uno.util.Bootstrap.bootstrap()\r\n bei SpreadsheetDocHelper.connect(String[] args) 3.10) Here is the complete output: \v4.0_4.0.0.0_de_b77a5c561934e089\mscorlib.resources.dll'. Module was built without symbols. The thread 0x1678 has exited with code 0 (0x0). The thread 0x1f34 has exited with code 0 (0x0). The thread 0x2944 has exited with code 0 (0x0). 'libreOfficeSdkTest.vshost.exe' (CLR v4.0.30319: libreOfficeSdkTest.vshost.exe): Loaded 'C:\ddtest\libreOfficeSdkTest\libreOfficeSdkTest\bin\x86\Debug\libreOfficeSdkTest.exe'. Symbols loaded. 'libreOfficeSdkTest.vshost.exe' (CLR v4.0.30319: libreOfficeSdkTest.vshost.exe): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll'. Cannot find or open the PDB file. 'libreOfficeSdkTest.vshost.exe' (CLR v4.0.30319: libreOfficeSdkTest.vshost.exe): Loaded 'C:\ddtest\libreOfficeSdkTest\libreOfficeSdkTest\bin\x86\Debug\cli_uretypes.dll'. Module was built without symbols. 'libreOfficeSdkTest.vshost.exe' (CLR v4.0.30319: libreOfficeSdkTest.vshost.exe): Loaded 'C:\ddtest\libreOfficeSdkTest\libreOfficeSdkTest\bin\x86\Debug\cli_oootypes.dll'. Module was built without symbols. 'libreOfficeSdkTest.vshost.exe' (CLR v4.0.30319: libreOfficeSdkTest.vshost.exe): Loaded 'C:\ddtest\libreOfficeSdkTest\libreOfficeSdkTest\bin\x86\Debug\cli_cppuhelper.dll'. Cannot find or open the PDB file. 'libreOfficeSdkTest.vshost.exe' (CLR v4.0.30319: libreOfficeSdkTest.vshost.exe): Loaded 'C:\ddtest\libreOfficeSdkTest\libreOfficeSdkTest\bin\x86\Debug\cli_basetypes.dll'. Module was built without symbols. Exception thrown: 'System.Runtime.InteropServices.SEHException' in cli_cppuhelper.dll Additional information: Eine externe Komponente hat eine Ausnahme ausgelöst. Exception thrown: 'System.Runtime.InteropServices.SEHException' in libreOfficeSdkTest.exe Additional information: Eine externe Komponente hat eine Ausnahme ausgelöst. The thread 0x1d88 has exited with code 0 (0x0). The thread 0x2e4 has exited with code 0 (0x0). The program '[12584] libreOfficeSdkTest.vshost.exe: Program Trace' has exited with code 0 (0x0). The program '[12584] libreOfficeSdkTest.vshost.exe' has exited with code 0 (0x0).
Well - from the first glance, this looks normal. When you start your app, it needs to bind to a LibreOffice installation; and it looks the bootstrap information in the same place where the cli dlls are located. The dlls in the SDK are meant to provide the necessary development environment, not to be used directly (since they are not related to any LibreOffice installation).
Thanks Mike. What would be the correct way to run this example successfully? The setting used in the provided example is the same used in our software for starting and LibreOffice for years. But once the SDk-Dlls are upgraded to 5.4.7.2, we get the bootstrap error. When we downgrade to 4.x every thing is O.K.
A new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Paco De Lucia, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Paco De Lucia, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp