Issue 123065 - sdk dlls not compatible with .Net 4
Summary: sdk dlls not compatible with .Net 4
Alias: None
Product: App Dev
Classification: Unclassified
Component: sdk (show other issues)
Version: 4.0.0
Hardware: PC Windows, all
: P3 Major
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2013-08-19 07:57 UTC by Jens Bornschein
Modified: 2013-08-22 07:32 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description Jens Bornschein 2013-08-19 07:57:47 UTC
The available SDK-dlls for cli to .Net (cli_basetypes, cli_cppuhelper, cli_oootypes, cli_ure, cli_uretypes) are compiled for runtime environment v2.0.50727. That is not compatible to the actual .Net 4 framework. This leads to the fact that the extensions created with this SDK can't be loaded as an internal extension. You have to let them run in their own external process with compatibility mode. So you need to implement some inter-process-communication between your registered UNO-Service and the .Net application handling the requests.

It's not possible to run the OpenOffice process itself in this compatibility mode by changing the appconfig.

The SDK cli dlls have to be compatible with the actual .Net 4 runtime environment.
Comment 1 Oliver-Rainer Wittmann 2013-08-21 10:50:21 UTC
Is this related to bug 122869?
Comment 2 Jens Bornschein 2013-08-21 11:17:41 UTC

The problem is that OpenOffice itself cannot load the sdk dll files under windows. It seems that the OpenOffice Process is running in a .Net 4 environment. In this environment you can't load dlls that are compiled as .Net version 2! So you cannot load the SDK dlls files, when you have created an UNO service that is calling a dll using the sdk dlls for cli.
It is possible to load .Net v2 dlls when you starting your .Net 4 Process in some kind of mixed-mode by config the start application via app.config file to start as "useLegacyV2RuntimeActivationPolicy". But this doesn't have effect on the OpenOffice Process. The OpenOffice Application will not run properly.

The easiest way to handle this is to recompile the dlls for cli-support as .Net 4 dlls. Then the OpenOffice application can now load their SDK-files.

There was a thread repoting this bug befor for the last version of Open office (tryed to find it but no result), liftet to a very high priority - but semms not be done. A solution for this problem is important!
Comment 3 hanya 2013-08-22 07:32:17 UTC
Bug 118355 was reported also about incompatibility to .Net Framework 4.