Difference between revisions of "Uno/CLI/Problems when using OOo built with VS 2005"

Latest revision as of 02:34, 29 December 2008

Because Microsoft Visual Studio 2005 uses the .NET Framework 2.0, an office built with it (in particular the CLI-UNO bridge and the assemblies belonging to this language binding) requires also a .NET Framework 2.0.

CLI client programs which were build for an office which used .NET Framwork 1.1 (that is, VS 2003), may not work out-of-the-box with an office that requires version 2 even if this version is installed. In particular, the .NET runtime cannot locate the policy assemblies and the assemblies themselves. The reason is probably that the version 2 uses a different GAC. However, this problem can be solved by providing a configuration file for the client program and specifying that version 2 is to be used. Assuming that the program is called runtests.exe then there must be a config file runtests.exe.config with at least these entries:

<?xml version="1.0"?>
<configuration>
  <startup>
    <supportedRuntime version="v2.0.50727" />
  </startup>
</configuration>

If you use another version of the runtime then the version string must be adapted accordingly.