main/cli_ure/readme.txt

9 #  with the License.  You may obtain a copy of the License at
22 Adapting version after a release of an office
25 of the assemblies at the time of the release. Please refer to the document at
27 for more information about versioning of assemblies.
35 Use the Windows Explorer to view the contents of the GAC. Are there any of the following assemblies
50 The "x" and "y" in the names of the policy assemblies are to be replaces by version numbers. At the
51 time of writing the real names are:
59 After deinstalling the offices, there should none of them remain in the GAC. If there are some, the…
60 try to remove them by clicking on them an choose uninstall from the context menu of the mouse.
62 Step 2: Install the office of the last release (respin when using staroffice)
64 Step 3: Determine the versions of the assemblies
66 Use the Windows Explorer to view the contents of the Windows\assembly directory. Locate the assembl…
67 and policy assemblies. See step 1 for the names of those assemblies. Take down the version number a…
74 The first part of the names represent the assemly which they are referring to. So obviously
81 last release. So if a version from version.txt is greater then the one of the respective
86 XYZ_NEW_VERSION : increse the value of the version
96 XYZ_POLICY_VERSION: change the version according to the version of the policy assembly from the
106 of unoil/climaker/version.txt similar to the versions.txt in this module. Then rebuild the module
126 The versions of all assemblies are contained in cli_ure/version/version.txt. This is the place where
129 time of the release. Second, when something was fixed. Then a version should be changed unless
134 minor version of cli_uretypes.dll should be incremented. When building the version directory, a scr…
136 cliureversion.mk contains all the entries of version.txt. The versions have been incremented
137 by the script. The script obtains the information of new types from unotype_statistics.txt
140 The contents of cliureversion.mk is used when building the assemblies in this project. It
145 The contents of version.txt
158 The meaning of these entries is the following:
160 CLI_URETYPES_NEW_VERSION represents the current version of the assembly.
162 CLI_URETYPES_OLD_VERSION represents a range of former versions (which were compatible).
164 cli_uretypes.config XML file which is part of the policy assembly. This is done automatically.
165 The XYZ_OLD_VERSION and XYZ_NEW_VERSION values are used for the binding redirection of
168 CLI_URETYPES_POLICY_VERSION represents the version of the policy file.
170 CLI_URETYPES_POLICY_ASSEMBLY represents the name of the policy file.
190 Because a change of a major is only done if the code has changed incompatibly, we must not
192 The name of the policy file has changed as well so as to refer to the new version. Since
203 Automatic incrementation of the version
206 The automatic incrementation of the version this is done when new published types have been
210 the version parts which have the meaning of a compatible change. Which versions are to be
218 of the different types:
221 Entries ending on _OLD_VERSION: The third number from the left of the second version is incremented.
234 As one can see from the incversions.txt, the versions of the cli_ure.dll and cli_cppuhelper.dll
241 at least the XYZ_NEW_VERSION, XYZ_OLD_VERSION and XYZ_POLICY_VERSION. In case of an incompatible
242 change, that is one of the first two numbers of the version has been changed, the XYZ_POLICY_ASSEMB…
245 When changing a version of an assembly then the versions of the assemblies which depend on it shoul…
246 … changed as well. For example, when changing the version of cli_uretypes.dll, then the versions of
250 If one would not change the versions of the dependent dlls then one would risk that an assembly
252 …i_uretypes.dll with version 1 and a cli_ure.dll with version 1. cli_ure.dll references version 1 of
253 cli_uretypes.dll. Now the version of cli_uretypes.dll changes to version 2 and its policy assembly …
262 rebasing of assemblies